Torrent hangs on "connecting to tracker..."

[rratss]

This problem has been around ever since I started using rTorrent. Torrents will intermittently hang on "Connecting to tracker..." and the only way to clear this up is to restart rTorrent. I've tried this on 2 separate boxes -- one with Slackware 10.2 and one with Slackware 11.0. Both have the newest packages of all necessary libraries. I've experienced it with versions 0.6.2, 0.6.3, 0.6.4 and the current SVN version of 0.7.0. I know other people who have this same issue but have not been able to find a solution.

[rakshasa]

How long does it hang? Since if libcurl is compiled without cares support it will hang on hostname lookups.

Anyway, try again and when it hangs for a reasonable amount of time, run "gdb -p <pid>" and then "bt". Post the backtrace here.

[anonymous]

Replying to rakshasa:

How long does it hang? Since if libcurl is compiled without cares support it will hang on hostname lookups. Anyway, try again and when it hangs for a reasonable amount of time, run "gdb -p <pid>" and then "bt". Post the backtrace here.

ok, I'll wait till it happens again and send you the backtrace before I install curl with c-ares support.

[artifex@freemail.hu]

I have the same problem. Sometimes stopping and starting torrent is help but sometimes starting another torrent helps as well. Sometimes everything works fine. Each torrents are on the same tracker so I think it's not a tracker problem. It looks like the start command is hold back or freeze the process of command queue and another start command is free up or unfreeze again.

[anonymous]

Replying to artifex@freemail.hu:

I have the same problem. Sometimes stopping and starting torrent is help but sometimes starting another torrent helps as well. Sometimes everything works fine. Each torrents are on the same tracker so I think it's not a tracker problem. It looks like the start command is hold back or freeze the process of command queue and another start command is free up or unfreeze again.

Same thing happens here. It's a shame, but back to btdownloadcurses for me <3

[rratss]

after adding some good DNS servers to my resolv.conf, I haven't had this problem occur anymore

[anonymous]

Replying to rakshasa:

How long does it hang? Since if libcurl is compiled without cares support it will hang on hostname lookups. Anyway, try again and when it hangs for a reasonable amount of time, run "gdb -p <pid>" and then "bt". Post the backtrace here.

here's the backtrace:

#0 0x404d58b2 in select () from /lib/libc.so.6 #1 0x000f2178 in ?? () #2 0x00000000 in ?? ()

[anonymous]

never mind. it was a tracker problem

[iive <iive@abv.bg>]

It's not tracker problem. It is not DNS problem either, it would hang at "Resolving" part.

Right now I'm running 5 torrent, 4 using the same tracker. One of the torrent always have "Connecting..." until some of the other torrents tries to connect to tracker. Then the message vanishes, but appear on another torrent. It happens on all 5 torrents. I'm sure it is not DNS problem because 2 of the torrents that use same tracker have synchronized themselves (connecting to tracker together at the same time) and one of the stacks, while the other doesn't.

It may be libcurl fault (I'm also using slackware 11.0, curl 7.15.5), it could also be rtorrent not hiding the message after connect (and they were actually successful).

I'll try to compile the newest version of curl (7.16.1) and report again.

Anyway libcurl seems to cause a lot of strange problem. If it works for you then I'd be happy to know your version and the options used to build it.

[rakshasa]

7.15.5 lacks one of the patches I sent in, so the answer is to upgrade.