Search the Community
Showing results for tags 'log file'.
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 .!sync files to get deleted, and then trying again, but no luck. I tried stopping and restarting sync on both machines. I tried combinations in various orders of all of the above. No joy. I noticed that my Linux version was still the previous stable version (1.1.82 or whatever), so I upgraded to the most recent 1.2.82. Didn't help. Eventually, I solved the problem by removing the photos folder on both machines and allowing them to reindex. As of yesterday, the problem has reoccurred. I don't want to spend half a day re-indexing the folders every time this happens. All other folders sync with no problems. Problem 2. While investigating the first problem, I inspected the log files on each machine. There were a fair number of errors on the Linux side. I turned on debug logging on the Linux machine. Shortly after that, I noticed that my sync.log file was getting huge. So I removed that switch from the init script and restarted the sync service. The logs continue to be huge. Like 9GB+ for 24 hours of operation. I've been running for less than 30 minutes and my sync.log on the Linux box is over 50MB! The log is quite verbose, and looks to me like it's still running in debug mode. I've searched through the forums, but haven't found anything relevant. Maybe my search terms are wrong? Anyway, apologies if I'm retreading anything, but any help would be much appreciated. I'm sure this is just a config issue.
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"?
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?
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.