Tracker gave HTTP response code 404 (Not Found)

[dspolleke]

Hi All,

I am using Transmission 2.2.1 as found in the RPM packages
http://geekery.blog.com/2011/02/17/tran ... aemon-cli/
But i have tested and came accross the same problem using (stable) 2.12. and 2.13


I installed it on a headless box (linux router based on centos 5.5 i386 ) with multiple network cards and accessing the webguiserver via the internal network

i have tried to download several torrents but NONE seem to download. IT just sits there... In te logs i see that the tracker returns a 404. I find that hard to believe because if i fire up rtorrrent the same torrent can be downloaded..

Code: Select all

[11:10:42.837] Saved "/home/transmission/.config/transmission-daemon/torrents/some.torrent.527956236ac5aae6.torrent" (bencode.c:1716)
[11:10:42.837] some.torrent Pausing (torrent.c:1729)
[11:10:42.837] Saved "/home/transmission/.config/transmission-daemon/resume/some.torrent.527956236ac5aae6.resume" (bencode.c:1716)
[11:10:42.837] some.torrent Queued for verification (verify.c:257)
[11:10:42.837] some.torrent Verifying torrent (verify.c:215)
[11:10:44.850] some.torrent Tracker gave HTTP response code 404 (Not Found) (announcer.c:1124)

i can provide the real torrent name and file

anyone an idea

[Jordan]

If the tracker is returning a 404 when Transmission tries to announce, then you're not going to get any peers from that tracker, you'll have to rely on DHT or to find a new torrent.

[dspolleke]

Thanks for the reply

Yes, i understand that ..

And i have tried numerous (random) torrents. that downloaded on the same machine (using rtorrent) without hesitation.

So, it is illogical that on the same time (well the same day / hour) a tracker is able to hook me up to peers.. but transmission cannot.

[Jordan]

I feel like we're starting out with a symptom (404) and jumping straight to the problem (no peers) and missing the middle steps. What is the result of rtorrent's announce? what message does the tracker give rtorrent?

[dspolleke]

besides the point really..

Transmission is not doing what it is supposed to do. what i tried to prove with the rtorrent experiment is that the torrent is valid, the tracker works as designed and i get a valid download.

i usually launch the rtottent in a screen. so i don 't see any tracker messages..

What do you want me to look out for?

[blacke4dawn]

No, it's not besides the point.

How about checking the response or info gotten from the tracker, do you get the same when using transmission as when using rtorrent.

If you do then it's most likely a problem with transmission, but if you don't then it's most likely a problem with the tracker. See the point there, transmission can't be "better" than the info it gets.

[WLS]

besides the point really..

Transmission is not doing what it is supposed to do. what i tried to prove with the rtorrent experiment is that the torrent is valid, the tracker works as designed and i get a valid download.

i usually launch the rtottent in a screen. so i don 't see any tracker messages..

What do you want me to look out for?

Is it a HTTP or UDP tracker?