Opened 10 years ago

Closed 10 years ago

#4344 closed Bug (fixed)

Zero Peers observed with Transmission 2.32

Reported by: lordcantgamer Owned by:
Priority: High Milestone: 2.40
Component: Transmission Version: 2.32
Severity: Major Keywords:


I have a problem with [b]zero peers while I am seedingb. This is leading to decreased upload speed. I am on a private tracker, I have PEX - DHT - LPD and uTP disabled (best uploading speed is observed this way). I am seeding multiple files at the same time. If I restart transmission, it will get more peers, after 30-60 mins transmission will lose the peers again.

(I checked the torrent files with uTorrent, I can observe lots of peers connected from seeds & leechers at the same time, but not with Transmission)

As can be observed in the above picture, announcing gets enough peers, but after a while transmission goes back to zero peers.

Change History (9)

comment:2 Changed 10 years ago by jordan

In the imageshack picture, it looks like the announce response contained 0 seeders and 0 leechers...

comment:3 Changed 10 years ago by livings124

lordcantgamer: ping

Are there seeders and leechers on this torrent?

comment:4 Changed 10 years ago by lordcantgamer

Yes, there actually seeders and peers when I try a different torrent client, or check the torrent seeds and peers from the tracker.

comment:5 Changed 10 years ago by saggy00

I have the same problem on version 2.33(ubuntu maverick). Trasmission says that scrapes but no scrape data are visible(zeros only). I have observed that the scrape problem appears on php trackers and not on xbtt.

I have been experimeneted with scrape.php and the problem remains on the occassions below:

  1. Scrape all torrents
  2. Scrape singe torrent
  3. Multi-Scrape

I could send you my scrape.php if you want.

comment:6 follow-up: Changed 10 years ago by livings124

Scrape data shouldn't impact actual peers connected to. That data is informational.

comment:7 in reply to: ↑ 6 Changed 10 years ago by gunzip

Replying to livings124:

Scrape data shouldn't impact actual peers connected to. That data is informational.

i wonder if this occasional problem could be related to this:


520            if( allAreSeeds && tr_torrentIsPrivate( tor ) )
521                tr_peerMgrMarkAllAsSeeds( tor );

these exact same lines used to be in announcer.c and caused me lots of headaches. they have since been removed ( r12517 ) but still remain here in torrent.c

i made my own manual patch to comment out these lines in torrent.c and have had no undesirable side effects. my past experience indicates these lines can incorrectly cause transmission to shed all peers.

comment:8 Changed 10 years ago by jordan

gunzip, I've committed your change in r12903, so it'll show up in 2.40 beta 2.

comment:9 Changed 10 years ago by livings124

  • Milestone changed from None Set to 2.40
  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.