[Solved] Peer not found error: How to get info with CLI

[Opperpanter]

Hello,

Currently all my torrents from one tracker are reporting an error:

"Peer not found <hash>. Restart torrent."

For all torrents, the hash is the same.

I see this error using Remote Transmission (the desktop gui on win7 x64).

I wanted to get some information using the command line on my NAS where transmission daemon is running.

The command transmission-remote -t 52 -i (or -it or -ip) doesn't show me the tracker status.

Which command should give me the info of the tracker status and error message?

I am using Transmission 2.32 on Debian Squeeze.

Thanks,

[rb07]

For all torrents, the hash is the same.

That is strange!

I've never seen the message you quote, I really don't know what it is about, but the only hash is usually the torrent's, and its different for each torrent.

Which command should give me the info of the tracker status and error message?

The "-it" parameter shows both status, and, if available, the problem message.

But the error message you show is not about trackers.

Wild guess: you are blocking peers outside Transmission (i.e. firewall, iptables)... but I would expect a time-out, not a not-found... perhaps the "peer" is really a bogus address that causes this problem (in other words, somebody injected the bogus address into the tracker expecting to cause exactly the error you are seeing)... is the "hash" really a hash or an IPv6 address?

[Opperpanter]

it turned out that other people were having some similar issues with the same tracker as well.
In the end I decided to restart transmission-daemon and after that everything was ok.