2.50b1 and some trackers, is this a new problem?

[rb07]

Hi,

What's wrong with the first picture?

The tracker seems to be responding, but there is no detail on the number of seeders and leechers, and the real problem is that the torrent with that tracker is doing nothing. After the daemon asks for peers counts: voilà, it connects to a couple of those peers.


While at the same time another torrent which looks normal is acting normal (but I started this torrent from zero, to test):

Is this a transient problem with some trackers? (I see 2 trackers doing the same thing) or something else?

With version 2.42 everything was normal, I changed versions today. Should I test with the older version? I also tested the unreleased but tagged version 2.50, same result as 2.50b1.

[gunzip]

What's wrong with the first picture?

The tracker seems to be responding, but there is no detail on the number of seeders and leechers, ..

I wonder in that first case if announce worked, but the scrape failed, which might explain the lack of seeder and peer count. I've seen that happen on my end, where is some cases announce worked and scrape failed on a particular tracker even though spaced minutes apart, and even visa-versa. But most times this does not occur.

But it's hard to draw to general conclusions based on only a few observations. I guess it's something to keep an eye on.

[rb07]

if announce worked, but the scrape failed

In that case you get (or used to get*) a clear message about that, in the log, and in the torrent properties panel.

So far (1 day) the problem is not critical, the torrents that depend on that tracker seem to be working. The only thing, which is different from version 2.42, is that it takes until the next scrape or announce for the torrent to do something (i.e. even when it shows there are N peers it doesn't seem to contact them until the next scrape/announce).

* I just received a "Scrape error: Could not connect to tracker (announcer.c:1255)" in the log, and nothing shows in the properties panel. This is with another tracker (not the one in the first pic) that seems to be working as expected -- another difference is that this torrent has multiple first tier trackers, not just one, but none of those showed an error.

After the next scrape or announce (I'm not sure which corresponds to peers, and which to "peer counts") everything is back to normal. So only the log message showed there was a transient error.

Not one similar error message about the torrents on the tracker in the first picture.

[gunzip]

After the next scrape or announce (I'm not sure which corresponds to peers, and which to "peer counts") everything is back to normal.

i generally run only the daemon (not gtk or qt) and always with latest version (now at 2.50) . using the terminal-based interface transmission-remote-cli.py i get good real-time feedback of the announces and scrapes so i can tell, for example, in your second screenshot:

"Got a list of 80 peers 15 minutes ago" is result of successful ANNOUNCE

"Tracker had 2685 seeders and 835 leechers 15 minutes ago" is result of successful SCRAPE

a few months ago (well before 2.50b1 came out) a private tracker was returning "null" (not 0) for seeders and leechers on scrape attempts, but there were never any scrape errors reported -- nevertheless the torrents worked fine as the announces were always successful. this lasted only a week or so and problem eventually was resolved by the sysop of the torrent site. i think a lot of this "quirky" behavior can be attributed to the trackers themselves.

[rb07]

In case it is important: I'm also only using the daemon, the screenshot if from Transmission-Qt used as a front end to the daemon.

a few months ago (well before 2.50b1 came out) a private tracker was returning "null" (not 0) for seeders and leechers on scrape attempts, but there were were never any scrape errors reported. this lasted only a week or so and problem eventually was resolved by the sysop of the torrent site. i think a lot of this "quirky" behavior can be attributed to the trackers themselves.

That is interesting, and it could be the case. But I noticed the change in behavior from one day (2.42) to the next (2.50) so I think its improbable that something changed at the tracker.

Repeating the test (the first pic is from a torrent that has multiple files which I'm downloading one or two at a time) I could not reproduce the inactivity, this time it connected immediately, without needing a scrape/announce or anything. This is with version 2.50 .