remo Posted March 21, 2014 Report Share Posted March 21, 2014 We are having issues with files being overwritten by older versions. No need to say that this is annoying. I told my guys to enable the debug log, but unfortunately, debug.log only contains FFFF and sync.log doesn't show us enough. Once we realize that a file has been overwritten, it's long gone from the sync.log. It looks like only the last 10-15 minutes are kept in the log file. While this might be nice to avoid a full harddisk, it's a bit tricky for us to get more information about the actual problem. All clients are currently using version 1.2.91 on Windows and one client runs on an ARM Linux NAS.Any ideas on how to catch more data in sync.log? Quote Link to comment Share on other sites More sharing options...
RomanZ Posted March 21, 2014 Report Share Posted March 21, 2014 remo, That's rather strange. 1.2.91 has no any log rotation mechanism. So, as soon as BTSync starts - it is killing the old log and writing a new one until it dies. My guess would be that btsync gets closed / crashes and restarted, that's why you can't see the beginning of the log. You can try using ProcessMonitor utility to see what is actually happening to BTSync. Quote Link to comment Share on other sites More sharing options...
remo Posted March 31, 2014 Author Report Share Posted March 31, 2014 The process has the same PID, unlikely it gets restarted. I can reproduce this behaviour on all computers we're using! sync.log is reset after about 10MB / 15minutes of data. I've had a closer look with process monitor, seems like there are two calls which might cause this issue. One is definitely coming from btsync where sync.log.old is created, but there's another one from svchost.exe. Not sure why the service process does that though.. UPDATE: Couldn't upload my export of process monitor, you can find it here http://www.mesch.ch/sync.log Quote Link to comment Share on other sites More sharing options...
RomanZ Posted March 31, 2014 Report Share Posted March 31, 2014 The behavior you describe is actually native for 1.3.67. The log rotation size can be adjusted by changing the advanced preference "log_size" to bigger value (10Mb by default). Are you confident you are using 1.2? Did you upgrade to 1.3 and then downgraded? Quote Link to comment Share on other sites More sharing options...
remo Posted April 1, 2014 Author Report Share Posted April 1, 2014 Yes, 100% sure! Happens on all kinds of computers and since 1.3 doesn't get installed automatically, all of our computers are still on 1.2.91..I guess I'll upgrade to 1.3 and increase the log size. Quote Link to comment Share on other sites More sharing options...
RomanZ Posted April 1, 2014 Report Share Posted April 1, 2014 Remo, I would also suggest upgrading to 1.3 so you'll get a control over log rotation. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.