[Transmission] "Peer not found. Restart the torrent." message extremely often

[Miroslav Hadzhiev]

Binary package hint: transmission

I get extremely often the message (for some of the torrents in a disorderly manner):

Tracker gave an error: Peer not found. Restart the torrent. - Idle

And, of course, Transmission DOES NOT restart these torrents automatically. In the end of the day I realize that I do not seed the most part of my downloaded torrents.

ProblemType: Bug
Architecture: amd64
Date: Wed Nov 4 21:28:05 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/transmission
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: transmission-gtk 1.75-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: transmission
Uname: Linux 2.6.31-14-generic x86_64

[Charles Kerr (charlesk)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

[Miroslav Hadzhiev (xtigyro)]

Sorry for the delayed answer!

Yes, the bug is reproducible and there are not any specific steps. In other words,

I download a torrent file, load it in Transmission, the downloading is completed and after some time Transmission stops seeding it.

I'll attach a torrent file (70 mb data will be downloaded), the tracker is the biggest one in Bulgaria - http://www.zamunda.net/ .

[Miroslav Hadzhiev (xtigyro)]

Charles, do you need some more information? If it is so, do not hesitate to ask me for. (:

[Charles Kerr (charlesk)]

Xtigyro, sorry for the delay. I'll try to test this torrent tonight.

[СкручЪ (skru4arq)]

Yeah, I have the same problem. It's not the torrent itself, it's not the tracker either. I haven't tried what would happen with a torrent from TPB or IsoHunt (where from I usually download) because I don't seed them more than a day, but when I seed Zamunda (yup, the same tracker) and ArenaBG torrents (another Bulgarian tracker) for more than two or three days shit happens. Usually when I redownload the torrent it's ok, but it's still pretty annoying.
BTW, half a month ago it was ok.

[Charles Kerr (charlesk)]

Sorry for the very long delay in getting back to this, especially after I said I'd test it on 12/09/09. Unfortunately my tests were unhelpful as the tracker would not respond to my announces, either in Transmission or in Deluge.

The text of that error message is coming from the tracker. It's intentionally human-readable because these errors are intended to be read and handled by end users, rather than the torrent clients. There's no programmatic way of the torrent client handling this.

For more information on this error and why it's occurring, you need to go talk to one of the tracker admins. If they have suggestions for how a torrent client can avoid this message, please feel encouraged to reopen this ticket with more information.

[Miroslav Hadzhiev (xtigyro)]

@ charles:

ok, I totally agree with you but the torrent is stopped and Transmission is not seeding it. On the other hand, there is not such an error in Deluge (for example).

[СкручЪ (skru4arq)]

Nor any other torrent client.

btw, I haven't noticed before, but if you restart Transmission the "peer not found" error disappears.

[Miroslav Hadzhiev (xtigyro)]

Or if you start and stop the torrent which is stopped with the very message.

[СкручЪ (skru4arq)]

Hm... A couple months ago it didn't work

[Miroslav Hadzhiev (xtigyro)]

Charles, what I should write to the administrators of http://www.zamunda.net/ (btw this is the biggest torrent tracker in Bulgarian) and http://arenabg.com/?

[Miroslav Hadzhiev (xtigyro)]

I can confirm that the this problem does not occur in Deluge, utorrent, Vuze, qBittorrent, KTorrent and BitComet.

[Miroslav Hadzhiev (xtigyro)]

So the problem "appears" in Deluge but it seems Deluge does not stop seeding it (ignores the error returned by the tracker).

[Miroslav Hadzhiev (xtigyro)]

And yes, the problem still occurs in Transmission (ver. 2.12).

[Nicolay Giraldo (nicolay-g)]

Zamunda only works correctly if your IP is from Bulgaria.

[Lyubomir (mystiquewolf)]

This is still an issue.