Swisstengu Posted July 18, 2013 Report Share Posted July 18, 2013 Hello,I'm doing some load-test with Sync:~340G, dispatched in 149k+ files, with recursions (more than 10 subdirectories)I'm wanting to sync those data from one host (call it "master") to two others (call them "slaves").At the begining, Sync seemed to work as expected, syncing data and so. Then, after about 6G of transmitted data, nothing seems to move.I enabled the debug, and found out many errors, like:Torrent magnet (…HASH…) status:137 error:<NULL> meta:0 conns:1 io:0What does it mean?Thank you!Cheers,C. Quote Link to comment Share on other sites More sharing options...
GreatMarko Posted July 18, 2013 Report Share Posted July 18, 2013 It's just an informational status message only and nothing to worry about!According to the developers "Log message started with Torrent... is just a status message. It does not mean any error." - Please see this thread Quote Link to comment Share on other sites More sharing options...
Swisstengu Posted July 18, 2013 Author Report Share Posted July 18, 2013 Hello,Thank you for the information - I'm poking a bit around as I'm getting some troubles with Sync - but I maybe just should wait a bit for it to index all files and create Magnets for them.Cheers,C. Quote Link to comment Share on other sites More sharing options...
Shot2 Posted August 12, 2013 Report Share Posted August 12, 2013 Same error messages here (v1.1.69 Win or v1.1.48 Ubuntu "master" side, v1.1.48 client side). Syncing to that client has been stuck for days now (no progression), I get hundreds of thousands of such errors for 10s of thousands of files:Torrent Archive.zip status:137 error:<NULL> meta:1 conns:1 io:0More worrying: for these thousands of files, it uploads something to the client (a few KB), then transfer speeds drop to zero. After a few hours/days, the same files reoccur with same issues and symptoms. Today only, it has uploaded ~3GB of data but to no avail... Wash, rinse, repeat. Nothing changes. The debug log file is now at ~500MB.Even if purportedly a "status message", it would be nice to have some actual reason for this mess... I know developers of closed-source software like to obfuscate the inner workings of their babies, but it could actually help to know the meaning of that cryptic "status:137 error:<NULL>". 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.