Ticket #1546 (closed defect: invalid)

Opened 3 years ago

Last modified 13 months ago

Tracker: Timed Out

Reported by: FUSiON Owned by: rakshasa
Priority: highest Component: rtorrent
Version: Severity: normal
Keywords: Cc:

Description

Yesterday i installed a new Debian Box and a fresh rtorrent/libtorrent per SVN.

If i add a torrent, rtorrent can't connect to the tracker (testest with some different tracker): Tracker: [Timed Out]

I've testet it with a very clean debian box with the TuT from  http://flipsidereality.com/blog/linux/rtorrent-with-wtorrent-on-debian-etch-complete-howto/

And the problem is still there.

On my older debian Box, i have only updated the rtorrent with the latest SVN ... there it works.

So the question: could it be, that rtorrent can't connect to tracker since latest release of rtorrent on a fresh installation?

Change History

  Changed 3 years ago by hammer

yes confirmed, exactly the same problem.

compiled from svn yesterday.

BUT: if i add several torrents, most of the time one states that tracker status is ok (and transfer is working). after a while it switches back to: rtorrent [tracker timed out].

@top - poster: have you tried to add several other torrents from different trackers?

  Changed 3 years ago by FUSiON

I've tried actually 2 private tracker with different torrents. None of these will start and ended with tracker timed out.

I will try some open trackers yet. be patient :D

greetz

FUSiON

  Changed 3 years ago by anonymous

Mininova and TPB tested: same prob :/

  Changed 3 years ago by anonymous

try upgrading libcurl

  Changed 3 years ago by anonymous

c-ares-1.5.3 curl-7.19.2

just installed (curl with cares support) ... same prob :/

  Changed 3 years ago by FUSiON

ok after recompiling rtorrent / libtorrent after the libcurl install .. it works fine

ok conclusion:

if you have a fresh debian installation you need to install the actual libcurl (  http://curl.haxx.se/download.html ) with the actual c-ares (  http://c-ares.haxx.se/ )

first install c-ares then libcurl (libcurl: ./configure --enable-ares)

After that .. compile libtorrent and rtorrent.

greetz

FUSiON

  Changed 3 years ago by rakshasa

  • status changed from new to closed
  • resolution set to invalid

  Changed 3 years ago by anonymous

solution confirmed :)

  Changed 3 years ago by anonymous

solution double confirmed :)

  Changed 3 years ago by anonymous

solution triple confirmed :)

  Changed 3 years ago by anonymous

very weird, on my home debian 4 box, this worked with no problem, on my dedicated server i had to do the above to get it to work.

solution quadruple confirmed. :)

  Changed 3 years ago by orlando.agostinho@gmail.com

Hi,

I have Debian etch 64bits, now it's working! Thanks!

Please, someone can explain why this?

Thanks!

  Changed 3 years ago by anonymous

Some systems trigger the bug in libcurl and many others don't. I don't think anybody really knows the details. But since it's fixed by upgrading libcurl it's not all that important.

  Changed 3 years ago by rockabillaboogie@gmail.com

I had the same problem, but only after an upgrade from 0.8.2 -> 0.8.4 (it worked fine on an initial install of 0.8.2). I can confirm that the above solution worked.

  Changed 3 years ago by Asher

Same solution for CentOS 5 with 0.12.5 and 0.8.5.

  Changed 2 years ago by anonymous

Fusions solution worked for me as well.

Using debian 4, with libtorrent 12.4 / rtorrrent 8.4.

  Changed 2 years ago by anonymous

FUSiON is a genious.

This should be on the main page or something.

  Changed 2 years ago by anonymous

worked for me too! tnx a lot!!

  Changed 2 years ago by firefly

Sweet... fixed my issues as well.. Debian 4 now running

*** rTorrent 0.8.6/0.12.6 ***

thank you!

  Changed 16 months ago by anonymous

Some systems trigger the bug in libcurl and many others don't. I don't think anybody really knows the details.  Christian Louboutin|  Christian Louboutin discount|  Christian Louboutin boots|But since it's fixed by upgrading libcurl it's not all that important.

follow-up: ↓ 22   Changed 13 months ago by anonymous

Apparently this also happens when the tracker is running on a port. In my case the tracker is public but the announce is on port 2710.

I'll try recompiling curl,c-ares,libtorrent, rtorrent and get back to you again if the problem remains. :)

in reply to: ↑ 21   Changed 13 months ago by anonymous

Replying to anonymous:

Apparently this also happens when the tracker is running on a port. In my case the tracker is public but the announce is on port 2710. I'll try recompiling curl,c-ares,libtorrent, rtorrent and get back to you again if the problem remains. :)


Tried it. Not working.
Currently I'm using Slackware 12.2 (on my server) and Slackware 13.1x64 (on my desktop).

@Server:
1. c-ares 1.7.4
2. curl-7.19.2 (--enable-ares)
3. libtorrent 0.12.6
4. rtorrent 0.8.6

@Desktop:
1. c-ares 1.7.4
2. curl-7.20.1 (--enable-ares)
3. libtorrent 0.12.6
4. rtorrent 0.8.6

This may be a problem in rtorrent ?
The announce url the torrent site I'm using (in Bulgaria) looks like this:
 http://p2p.arenabg.com:2710/(md5hash_of_something)/announce

Sometimes it downloads the torrents without any problems... Sometimes it just doesn't start ("Tracker: [Tried all trackers.]")

I hope this helps but if any other information is required you may contact me at fl00d _ at _ itnews-bg.com(remove " _ " from the mail and replace "at" with @)

Note: See TracTickets for help on using tickets.