Opened 13 years ago

Closed 13 years ago

Last modified 13 years ago

#1677 closed Bug (invalid)

Daemon stops seeding but doesn't show it or any error message.

Reported by: rb07 Owned by: charles
Priority: Normal Milestone: None Set
Component: Daemon Version: 1.42
Severity: Major Keywords:
Cc:

Description

Context: transmission-daemon 1.42 running on Gentoo Linux (amd64 arch - dual Xeon)

As reported on the forum, this has happened twice, today was after restarting the daemon 3 days ago. Normal operation, a dozen or so torrents seeding with 3 trackers involved, with one tracker I haven't seen the problem and that probably is because its torrents are pretty active, the other 2 trackers have low and very low activity, there are 3 torrents on one tracker and 5 on the very low activity one.

All torrents on those low activity trackers loose their seeding status (looking from the tracker side) but transmission-daemon reports nothing, just that they are Idle which is not unusual.

The unusual part is this, taking one torrent as an example:

$ transmission-remote -n admin:password -t 23 -i
NAME
  Id: 23
  Name: 01 ...
  Hash: xyz

TRANSFER
  State: Idle
  Percent Done: 100%
  ETA: Unknown
  Download Speed: 0.0 KB/s
  Upload Speed: 0.0 KB/s
  Have: 355.4 MB (355.4 MB verified)
  Total size: 355.4 MB (355.4 MB wanted)
  Downloaded: 355.5 MB
  Uploaded: 223.1 MB
  Ratio: 0.63
  Corrupt DL: None
  Peers: connected to 0, uploading to 0, downloading from 0

HISTORY
  Date added:      Tue Jan  6 18:41:24 2009
  Date finished:   Wed Jan  7 09:59:46 2009
  Date started:    Tue Jan  6 18:41:24 2009
  Latest activity: Thu Jan  8 09:39:26 2009

TRACKER
  Latest announce: Wed Jan  7 17:42:25 2009
  Announce URL: http://www.xyz.net/tracker.php/xyz/announce
  Announce response: OK (200)
  Next announce:   Wed Dec 31 18:00:01 1969
  Latest scrape:   Thu Jan  8 02:13:22 2009
  Scrape response: OK (200)
  Next scrape:     Wed Dec 31 18:00:01 1969
  Tracker knows of 9 seeders and 2 leechers
  Tracker has seen 20 clients complete this torrent

ORIGINS
  Date created: Tue Jan  6 15:51:09 2009
  Public torrent: No
  Creator: Azureus/3.1.1.0
  Piece Count: 1422
  Piece Size: 262144

See the tracker "Next announce" and "Next scrape" dates?

Those are a big fat zero converted to date (and time zone shifted).

After I restarted the daemon, same torrent:

# transmission-remote -n admin:password -t 27 -i
NAME
  Id: 27
  Name: 01 ...
  Hash: xyz

TRANSFER
  State: Idle
  Percent Done: 100%
  ETA: Unknown
  Download Speed: 0.0 KB/s
  Upload Speed: 0.0 KB/s
  Have: 355.4 MB (355.4 MB verified)
  Total size: 355.4 MB (355.4 MB wanted)
  Downloaded: 355.5 MB
  Uploaded: 223.1 MB
  Ratio: 0.63
  Corrupt DL: None
  Peers: connected to 0, uploading to 0, downloading from 0

HISTORY
  Date added:      Tue Jan  6 18:41:24 2009
  Date finished:   Wed Jan  7 09:59:46 2009
  Date started:    Thu Jan  8 16:57:44 2009
  Latest activity: Thu Jan  8 16:58:36 2009

TRACKER
  Latest announce: Thu Jan  8 16:57:44 2009
  Announce URL: http://www.xyz.net/tracker.php/xyz/announce
  Announce response: OK (200)
  Next announce:   Thu Jan  8 17:27:49 2009
  Latest scrape:   Thu Jan  8 16:57:45 2009
  Scrape response: OK (200)
  Next scrape:     Thu Jan  8 17:12:46 2009
  Tracker knows of 12 seeders and 0 leechers
  Tracker has seen 22 clients complete this torrent

ORIGINS
  Date created: Tue Jan  6 15:51:09 2009
  Public torrent: No
  Creator: Azureus/3.1.1.0
  Piece Count: 1422
  Piece Size: 262144

Back to normal (except that I was kicked from one site for not seeding back).

Change History (13)

comment:1 Changed 13 years ago by Biiaru

Similar thing happens in 1.42 and up on Mac OS X as well. It will just stop talking to trackers after a bit.

comment:2 Changed 13 years ago by charles

Does this problem persist in the nightlies? We've done an awful lot of work on connectivity since 1.42.

comment:3 Changed 13 years ago by rb07

I don't see anything relevant in the tickets (and I searched twice before opening my report).

Something that may be interesting: I downgraded to 1.40 and from one of the trackers it is getting the famous "Tracker request failed. Got HTTP Status Code 0 (No Response)", could this be related to the fix/change made for that? I checked a torrent with this "Announce response" and the dates are fine (in the future, not the past like the problem I reported).

comment:4 follow-up: Changed 13 years ago by charles

I don't see anything relevant in the tickets (and I searched twice before opening my report).

That's not what I asked, though. Does this problem persist in the nightlies?

comment:5 in reply to: ↑ 4 Changed 13 years ago by rb07

Replying to charles:

That's not what I asked, though. Does this problem persist in the nightlies?

That's what Biiaru said on the second comment, doesn't it?

comment:6 Changed 13 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed

Not as far as I can tell. I have no idea what "on up" means since he didn't give a revision number.

Look, I'm not going to repeat myself a third time. Please reopen this ticket when you have more information available for me.

comment:7 Changed 13 years ago by Biiaru

As far as I can tell, it does not happen for me in r7651 on Leopard 10.5.6.

Though my problem was a bit different anyway. After a while, any communication with any tracker would cease. T would say "Connecting..." or "Please wait..." or something similar under the announce/scrape status and it would never actually announce/scrape after that time period, meaning any new torrents added in after that point would just not work. If at some point I do experience this problem again in 7651, I will reopen the ticket unless you want me to make a separate ticket with this description.

comment:8 follow-up: Changed 13 years ago by valentin

  • Resolution invalid deleted
  • Status changed from closed to reopened

Hi there! The same happens to me. When restarting the daemon the next announce date fixes, but after a while it's wrong again. Why is this case invalid? Is there any solution for this problem? I'm running transmission under Oleg.

comment:9 follow-up: Changed 13 years ago by charles

valentin: what version are you using? and, if it's not 1.50 beta 2, please upgrade to that and let us know if it works there.

comment:10 in reply to: ↑ 9 Changed 13 years ago by valentin

Replying to charles:

valentin: what version are you using? and, if it's not 1.50 beta 2, please upgrade to that and let us know if it works there.

My current version is 1.42-1. Can you tell me where can I find prebuilt .ipk version of the beta? Running it from source would take years to install as I run Oleg on Asus's WL500gp. Thx in advance.

comment:11 in reply to: ↑ 8 ; follow-up: Changed 13 years ago by charles

  • Resolution set to invalid
  • Status changed from reopened to closed

Replying to valentin:

Hi there! The same happens to me [in 1.42-1]. When restarting the daemon the next announce date fixes, but after a while it's wrong again. Why is this case invalid? Is there any solution for this problem? I'm running transmission under Oleg.

Please refer to this comment and this comment.

comment:12 in reply to: ↑ 11 Changed 13 years ago by valentin

Replying to charles:

Replying to valentin:

Hi there! The same happens to me [in 1.42-1]. When restarting the daemon the next announce date fixes, but after a while it's wrong again. Why is this case invalid? Is there any solution for this problem? I'm running transmission under Oleg.

Please refer to this comment and this comment.

Hi!

I'm not sure what comments should I read. Please help me out. What "nightlies" means?

comment:13 Changed 13 years ago by livings124

Beta 2 is linked on the main page.

Note: See TracTickets for help on using tickets.