Opened 12 years ago

Closed 12 years ago

#3361 closed Bug (invalid)

Tracker announces fail on DNS-323

Reported by: capone Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 2.00
Severity: Normal Keywords: tracker did not respond
Cc:

Description

I am running Transmission on the DNS-323. I have tried to resolve this issue with version, 1.82, 1.91, 1.92 and 2.00. All of the version that I have tried have the same problem.

I have Transmission running and downloading 9 torrents, all with multiple trackers. Transmission is reporting on all trackers on all torrents (some the same trackers and some different trackers) that the "tracker did not respond". I can load the same torrent file on 2 other machines, 1 windows w/ utorrent and 1 ubuntu w/ deluge and both download fine. However, transmission is reporting "tracker did not respond". I have tried upgrading/downgrading, stopping and starting the service, nothing works, letting it go over night seeing if it resolves itself.

If you need more info I can provide it. As for now, I will provide a screen shot of what I am seeing from one torrent and its trackers.

Attachments (2)

Transmission SS.png (19.3 KB) - added by capone 12 years ago.
Transmission SS2.png (109.4 KB) - added by capone 12 years ago.

Download all attachments as: .zip

Change History (13)

Changed 12 years ago by capone

comment:1 Changed 12 years ago by charles

Since you have Ubuntu installed -- does the GTK+ version of Transmission that comes with Ubuntu work?

comment:2 follow-up: Changed 12 years ago by capone

Ok. So, this is what I tried.

I downloaded ubuntu, put it on a USB key. Ran the live version from the key. Added 8 or 9 or the "problem" torrents, and the trackers are responding and the torrents are just downloading away...like normal.

Any ideas?

Changed 12 years ago by capone

comment:3 Changed 12 years ago by capone

I just tried pausing all the "problem" torrents on the DNS-323 and I added a Ubuntu torrent just to see what would happen. And the same problem happened, "tracker did not respond".

I took a screen shot for you to see, "Transmission SS2.png".

Thanks.

comment:4 in reply to: ↑ 2 Changed 12 years ago by charles

Replying to capone:

Ok. So, this is what I tried.

I downloaded ubuntu, put it on a USB key. Ran the live version from the key. Added 8 or 9 or the "problem" torrents, and the trackers are responding and the torrents are just downloading away...like normal.

So the same torrents announce properly on Ubuntu but not on the DNS-323?

comment:5 Changed 12 years ago by capone

Correct.

comment:6 Changed 12 years ago by charles

  • Summary changed from Tracker did not respond to Tracker announces fail on DNS-323

Sounds like a build issue on the DNS-323 to me. You may want to contact the person packaging Transmission on that platform.

comment:7 follow-up: Changed 12 years ago by capone

ah...you could be right. Since I last updated... the Ubuntu torrent has downloaded, and Transmission is still reporting "Tracker did not respond". So, not really sure what is going on there.

I guess I need to try completely removing any residue of Transmission and start fresh with 2.0.

comment:8 in reply to: ↑ 7 Changed 12 years ago by charles

Replying to capone:

ah...you could be right. Since I last updated... the Ubuntu torrent has downloaded, and Transmission is still reporting "Tracker did not respond". So, not really sure what is going on there.

DHT probably was able to find peers without help from the tracker.

comment:9 Changed 12 years ago by capone

Ok...another update

Got rid of Fonz's funplug and transmission...

Installed debian, then updated to lenny, then built transmission 2.0 (fixed some dependency issues) from the tarball.

Configured transmission for web access. Uploaded a fedora torrent, and right away, "Tracker did not respond."

Absolutely driving me nuts!

Any Ideas?

comment:10 Changed 12 years ago by capone

Ahhhh....Finally fixed it!

For some reason my DNS-323 was holding onto my old gateway 192.168.1.2...and I only noticed it through a traceroute.

After I ran the command ifconfig egiga0 del 192.168.1.2

I am back in business. Trackers connected right away! :)

I will let this run overnight and see how it looks in the morning. it has to re-verify local data at the moment... but my test torrent, fedora...connected right away and started downloading at over 400K in a few seconds. excellent.

comment:11 Changed 12 years ago by charles

  • Resolution set to invalid
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.