Hash checking large files causes ruTorrent and rTorrent to lose conn.

[jith45]

I've been using rTorrent/ruTorrent on my seedbox slice for over a year now without so much as a days problem. However, recently my provider has forced me to move to a new server and I am now experiencing a very frustrating problem. When hash-checking torrents, the connection to rTorrent breaks, and I get a message in the log stating, "The request to rTorrent has timed out."

rTorrent seems to still be running though, as it eventually comes right and when ruTorrent refreshes, the torrent has hashed and is ready to go. On my old box, I was able to see the status change to "checking", along with the percentage complete. Not so with the new box. Strangely enough, my provider was unable to pinpoint any significant differences between the two machines and the response was basically, "Start using Deluge."

So this irritated me enough to go out and get my own dedicated server and try for myself. Well, much to my dismay, I am experiencing the same problem on my new machine!!!

Any advice would be MUCH appreciated, thank you.

Specs:
i5 2300
16GB RAM
rTorrent 0.8.9
libTorrent 0.12.9
ruTorrent 3.3

 

[das329717]

Increase your rTorrent timeout in settings and / or check the box marked ignore timeouts.
Chances are the box is under more load than the last one or the setting above have altered.

 

[jith45]

Are you referring to the "Request timeout" setting? It is already rather high at 30,000ms and ticking "ignore timeouts" simply suppresses the message.

 

[das329717]

30 seconds is the default but if your box under load often setting it to 45 - 60 can solve the issue.
People get freaked out by seeing a timeout as the logger tab keeps it there and doesn't display "rTorrent now responding" type message

 

[jith45]

Thanks das, however its not merely a matter of freaking out when there is no activity. Having used rTorrent on my first seedbox, I've seen first-hand what is *supposed* to happen when hash checking in ruTorrent, so I can see that something is amiss.

I could increase the timeout to ten minutes and it wouldn't change the fact that ruTorrent stops responding when it should not. At no point whatsoever, even if I wait for a 5 minutes, does the status of the torrent in ruTorrent change to "Checking".

rTorrent itself seems to lock up. If I attach the screen session, rTorrent is unresponsive (yet I can see it eating up CPU time)

 

[das329717]

From this line I understood the problem was temporary "rTorrent seems to still be running though, as it eventually comes right and when ruTorrent refreshes, the torrent has hashed and is ready to go"

 

[jith45]

That's correct. Ultimately, the hash check completes and everything is fine.

The problem is that during the hash checking process, ruTorrent has no connection to rTorrent. Its almost as if rTorrent is too busy to accept any requests from ruTorrent. The result is the appearance that rTorrent or ruTorrent has crashed. This should not happen. Even during a hash check, ruTorrent should be able to query rTorrent and I should see the progress of the hash check.

 

[shwetha17]

This is very likely the problem that changeset #1246 fixes, which means either apply it, get a rT distro that does, or use git head.