Search the Community

Showing results for tags 'log file'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Resilio Sync
    • Sync General Discussion
    • Sync Troubleshooting
    • Sync for NAS (Network Attached Storage)
    • Sync Stories
    • Developers
    • Feature Requests

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 4 results

  1. I would post these two problems separately, but I think they are related. Some background: I've been using sync for months now and love it. One of the directories I've started syncing recently is my photos folders: 450GB in 66,000+ files between a Windows 7 64-bit machine and my Linux server at home. Problem 1. I noticed that the sync was taking a long time and that the speed was really slow. That's when I noticed that the 300MB sync of current files was creating a lot of .!sync files and not finishing the sync on them. I tried moving the files in question out of the folder, allowing the
  2. A long set of similarly named files (~500) are not synced across 2 peers. The corresponding line of the log file is the following: [2014-10-19 13:28:15] SF[3AE5]: Torrent \\?\F:\.......\....._A1_seg_007.mat status:137 error:<NULL> meta:1 conns:0 io:0 What is the meaning of "status:137 error:<NULL> meta:1 conns:0 io:0"?
  3. In my application support folder on Mountain Lion 10.8.5 I had a bit torrent folder of 5.9GB! It turned out that in the folder there was log file of that size. When I double clicked it, it opened the console and showed an endless list of messages. So I deleted the folder and it had no effect on bit torrent sync. Perhaps the size can be limited and automatically trigger a delete operation with an update?
  4. Hi. I'm running Bittorrent Sync 1.1.82 on Windows 7 64 bits. I was trying to enable Debug Logging to try and figure out why synchronization is so slow and I've realized that no debug or log files are being created. Initially I couldn't figure out where the debug file was supposed to be created at. After searching these forums I found that the file name is "debug.txt" and it should be in the same directory as "sync.log". Well, after doing a full drive search, neither of these files is anywhere to be found! Am I missing something here or aren't these files being generated at all? Thanks.