krtaylor Posted October 28, 2014 Report Share Posted October 28, 2014 I have around 8 systems with an interlocking mesh of about a dozen separate sync shares. Not all are shared on all systems. All systems are running 1.4.93; all are Windows 7 excpt for one Linux. Most of the sync shares are fairly large, up to a few hundred GB. After several weeks of indexing and transmission, all the shares are complete, with on exception. One of the Windows systems cannot complete the sync. On that system itself, it thinks it has everything. On the other peers, they think it needs another 300mb, but it isn't taking it. We tried deleting the library files on the problem system. It took several days to re-index everything, but it ended up the same way as before. Standard advice is to provide log files, but, what should be included in them? - Which system, the problem system or the peers, or both? - Log files of just anytime whe the systems are sitting there, or specifically when BTS is starting up? Quote Link to comment Share on other sites More sharing options...
RomanZ Posted October 29, 2014 Report Share Posted October 29, 2014 @krtaylor In general - yes, we'll need logs to identify your "not syncing" issue root cause. Though, there are couple of things you can quickly check yourself prior sending us logs. 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.