Transmission cannot connect to tracker

Ask for help and report issues with the Mac OS X version of Transmission
Ryoujin
Posts: 576
Joined: Sat Jan 05, 2008 3:43 pm

Re: Transmission cannot connect to tracker

Post by Ryoujin »

It has been a while since I last posted here ^_^

I'm having the same problem, T doesn't connect to the tracker. This is with multiple files, using 2.61 (13407). It used to work just fine, haven't downloaded anything for a couple of weeks ago until today.

Code: Select all

2012-07-27 01:54:03 +0000 session.c:720 [Info] Transmission: Transmission 2.61 (13407) started
2012-07-27 01:54:03 +0000 rpc-server.c:803 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2012-07-27 01:54:03 +0000 tr-udp.c:58 [Error] UDP: Failed to set receive buffer: No buffer space available
2012-07-27 01:54:03 +0000 tr-udp.c:77 [Error] UDP: Failed to set receive buffer: requested 4194304, got 42080
2012-07-27 01:54:03 +0000 tr-dht.c:305 [Info] DHT: Reusing old id
2012-07-27 01:54:03 +0000 tr-dht.c:153 [Info] DHT: Bootstrapping from 145 IPv4 nodes
2012-07-27 01:54:04 +0000 rpc-server.c:803 [Info] RPC Server: Adding address to whitelist: 127.0.0.1
2012-07-27 01:54:04 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): initnatpmp succeeded (0)
2012-07-27 01:54:04 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendpublicaddressrequest succeeded (2)
EDITED
2012-07-27 01:54:04 +0000 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Not forwarded" to "Starting"
2012-07-27 01:54:12 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2012-07-27 01:54:12 +0000 natpmp.c:141 [Info] Port Forwarding (NAT-PMP): Found public address "190.219.1.219"
2012-07-27 01:54:12 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): sendnewportmappingrequest succeeded (12)
2012-07-27 01:54:12 +0000 natpmp.c:72 [Info] Port Forwarding (NAT-PMP): readnatpmpresponseorretry succeeded (0)
2012-07-27 01:54:12 +0000 natpmp.c:221 [Info] Port Forwarding (NAT-PMP): Port 65239 forwarded successfully
2012-07-27 01:54:12 +0000 port-forwarding.c:93 [Info] Port Forwarding: State changed from "Starting" to "Forwarded"
2012-07-27 01:55:21 +0000 announcer.c:1259 [Info] EDITED: Scrape error: Could not connect to tracker
2012-07-27 01:55:21 +0000 announcer.c:1268 [Info] EDITED: Retrying scrape in 302 seconds.
2012-07-27 01:55:28 +0000 announcer.c:1259 [Info] EDITED: Scrape error: Connection failed
2012-07-27 01:55:28 +0000 announcer.c:1268 [Info] EDITED: Retrying scrape in 313 seconds.
2012-07-27 01:55:28 +0000 announcer.c:1259 [Info] EDITED: Scrape error: Connection failed
2012-07-27 01:55:28 +0000 announcer.c:1268 [Info] EDITED: Retrying scrape in 356 seconds.
2012-07-27 01:55:28 +0000 announcer.c:994 [Info] EDITED: Connection failed
2012-07-27 01:55:28 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 346 seconds.
2012-07-27 01:55:28 +0000 announcer.c:994 [Info] EDITED: Connection failed
2012-07-27 01:55:28 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 918 seconds.
2012-07-27 01:55:28 +0000 announcer.c:994 [Info] EDITED: Connection failed
2012-07-27 01:55:28 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 926 seconds.
2012-07-27 01:55:28 +0000 announcer.c:994 [Info] EDITED: Connection failed
2012-07-27 01:55:28 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 316 seconds.
2012-07-27 01:55:28 +0000 announcer.c:994 [Info]  EDITED: Connection failed
2012-07-27 01:55:28 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 314 seconds.
2012-07-27 01:55:28 +0000 announcer.c:994 [Info] EDITED: Connection failed
2012-07-27 01:55:28 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 325 seconds.
2012-07-27 01:55:40 +0000 announcer.c:994 [Info] EDITED: Could not connect to tracker
2012-07-27 01:55:40 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 301 seconds.
2012-07-27 01:55:40 +0000 announcer.c:994 [Info] EDITED: Could not connect to tracker
2012-07-27 01:55:40 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 349 seconds.
2012-07-27 01:55:40 +0000 announcer.c:994 [Info] EDITED: Could not connect to tracker
2012-07-27 01:55:40 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 954 seconds.
2012-07-27 01:55:40 +0000 announcer.c:994 [Info] EDITED: Could not connect to tracker
2012-07-27 01:55:40 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 303 seconds.
2012-07-27 01:55:40 +0000 announcer.c:994 [Info] EDITED: Could not connect to tracker
2012-07-27 01:55:40 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 312 seconds.
2012-07-27 01:55:40 +0000 announcer.c:994 [Info] EDITED: Could not connect to tracker
2012-07-27 01:55:40 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 325 seconds.
2012-07-27 01:55:40 +0000 announcer.c:994 [Info] EDITED: Could not connect to tracker
2012-07-27 01:55:40 +0000 announcer.c:1003 [Info] EDITED: Retrying announce in 334 seconds.
Ryoujin
Posts: 576
Joined: Sat Jan 05, 2008 3:43 pm

Re: Transmission cannot connect to tracker

Post by Ryoujin »

x190 wrote:Trackers come---Trackers go. Yes, even the old reliables. Try triple c and DHT.

What?
Ryoujin
Posts: 576
Joined: Sat Jan 05, 2008 3:43 pm

Re: Transmission cannot connect to tracker

Post by Ryoujin »

Update: I left T opened with the non-connecting trackers up, came back after, lets say, two hours, and everything downloaded. If I go to the Inspector, I still see "Cannot connect to the tracker", tho.
Ryoujin
Posts: 576
Joined: Sat Jan 05, 2008 3:43 pm

Re: Transmission cannot connect to tracker

Post by Ryoujin »

Is this being looked? :/ Anything I can provide to see where's the problem?

Files eventually download, but not in a normal manner; I have to wait a while until it starts downloading and even when it downloads it seems it's not really thru the tracker, as everything that is under the Trackers tab says:

TRACKER URL
Announce error: Could not connect to tracker
Announce in progress...
Scrape error: Could not connect to tracker


Edit: Hmm, seems that it has to do something with HTTP and UDP trackers (?) For now I think I found a fix.
nick2k3
Posts: 13
Joined: Fri Dec 05, 2008 10:04 pm

Re: Transmission cannot connect to tracker

Post by nick2k3 »

From what I have learnt in these months the "could not connect to tracker" message does not prevent the torrent from downloading:
I guess that when T. cannot get peers from trackers it starts a DHT session to fetch some.

A definitive proof of this behaviour would be:
1) when T. is in a "Could not connect to tracker" state, DELETE all known peers data (I think dht.dat will do)..
2) restart T.
3a) if T can grab peers independently form the error message then it is a "visualization problem" (T. can grab peers but something underneath went wrong and it displays that message)

3b) if no peer is grabbed from tracker then there's something weird about how T. connects to tracker *.

* I guess T is the problem because when this error message occurs, simply running uTorrent against the same .torrent file will result in a regular tracker connection (anybody confirm???)

PS: as I have seen that this thread has evolved towards "the could not connect to tracker" issue but I started it pointing out a different bug:

2012-03-13 16:40:59 +0000 tr-udp.c:260 [Error] UDP: Couldn't bind IPv4 socket

which is still happening, can some mod "split" into two thread?
zloster12
Posts: 1
Joined: Sun Dec 02, 2012 10:53 pm

Re: Transmission cannot connect to tracker

Post by zloster12 »

I had similar problems: a lot of messages about "Scrape error: Could not connect to tracker".
I'm running transmission-daemon on a Ubuntu machine used as a file server. It seems that in some point of time I broke the DNS configuration of the network interfaces.
After I corrected the DNS configuration everything seems to work fine.
So my advise is if you encounter similar errors please check your (the machine running the transmission) DNS configuration and DNS servers accessibility.
hugolp
Posts: 2
Joined: Sat Oct 13, 2007 9:17 am

Re: Transmission cannot connect to tracker

Post by hugolp »

I am seeing the same problems with transmission-daemon and udp trackers, and I am 100% sure its not a DNS or other type of network problem. UDP trackers will work fine for a while and then transmission-daemon will be unable to access them. I am not sure why, but I suspect it has to do with restarting the system while a download is on. To solve the issue all I have to do is stop the downloads and restart the daemon. Then transmission-daemon will be able to access the udp trackers again. All this without changing my network configuration at all or even restarting the computer, just restarting the daemon will solve it (this is why I am sure its not a network issue and it is a transmission-daemon bug). No problem accessing http trackers at all.

Im using Ubuntu 12.10 and the transmission ppa (so the version is the last from the ppa).
dzidzitop
Posts: 8
Joined: Sun Dec 23, 2012 9:58 pm

Re: Transmission cannot connect to tracker

Post by dzidzitop »

I'm having the same situation as hugolp described.
Linux z 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux
Transmission GTK 2.73

Massive pausing of the torrents running, restarting the torrent client, starting the torrents helps much. However even in this case there is a number of 'scrape error' messages, all of which are related to the same server. So for some torrent servers it starts working, and it does not for others.
jgabor
Posts: 8
Joined: Thu Aug 09, 2012 2:57 pm

Re: Transmission cannot connect to tracker

Post by jgabor »

I'm also having a similar problem. transmission-daemon refuses to connect to a specific tracker, all other trackers works fine. It feels like there's some old cache or something that needs to be flushed, but I can't figure it out. I've flushed all DNS caches, deleted dht.dat and all other tricks found in this thread (I've even completely reinstalled transmission-daemon) but to no help at all. Deluge and other torrent clients have no trouble at all to connect to the same tracker using the same network settings as Transmission. I can even curl the announce URL without trouble.

I'm running Ubuntu 12.04 x64 with transmission-daemon 2.77.
pmmalmeida
Posts: 2
Joined: Tue May 14, 2013 8:57 pm

Re: Transmission cannot connect to tracker

Post by pmmalmeida »

Hi there guys,

I've used transmission (2.3X I think) on my iomega ix2-200 (non cloud edition) for some time with no hassle.
I then upgraded to cloud edition and upgraded my transmission to 2.77.
I cannot connect to any trackers, I always get "Scrape error: Connection failed".
If I use "randomize port on launch" and "use port forwarding on my router" (upnp) I can connect to trackers for a while after I restart trasmission-da, but it always goes back to scrape error.
Is this a bug in transmission? What can I do to solve this or work around it?

Thank you!
Pedro de Almeida
Portugal

Edit: Sorry I posted on mac =( Only saw it now...
pmmalmeida
Posts: 2
Joined: Tue May 14, 2013 8:57 pm

Re: Transmission cannot connect to tracker

Post by pmmalmeida »

x190 wrote:Is your ISP blocking ports?
Sorry I forgot to mention... Using other torrent clientes on other machines in the same networks works fine.
How can I be sure my ISP is not blocking any ports?
sysmaster
Posts: 1
Joined: Mon Jul 08, 2013 10:21 pm

Re: Transmission cannot connect to tracker

Post by sysmaster »

Funny I too have the same problem, also with 2.52, however not on Mac. (Updating this would be a horror here on my Debian (stable) box, since at least the .deb package of 2.7X requires libssl 1.0.0 and that would probably break more than 25 programs relating on 0.9.8 ...nah thanks)

Anyways...that problem is definitely there, and it must be T. related.

My scenario is probably way simpler than some of your guys' ones:

- Started downloading torrent, link was a magnet link (as usual these recent days). Worked perfectly.
- Figured out -OOPS- I don't have enough disk space, so I PAUSED the download, moved Location, and RESUMED the download.
- Now all trackers showed 'Connection error' in red.
- Even after 20 minutes, nothing happened.
[*]- Deleted files already downloaded (weren't much anyway) plus the torrent, then re-imported magnet link.

- Result: Magnetizing...yadayada...stayed at 0.00% for minutes, even though it dl'ed at hyper-speed when I first started it.
- OK. Set 'Randomize network port', restarted client, started from step [*] again, worked a treat.

Conclusion:
The fact THAT you have to restart the client everytime you pause magnet-driven downloads (because of the fact that it will NEVER connect to any tracker again after resuming d/l) is clearly a BUG. This simply must not happen, as it annoys the hell out of users.
As a provisorical approach, one could add a button that behaves as if the client was restarted (like 'Initialize all' or something). Because the way it is currently is not acceptable for me.
staxtopoutanos
Posts: 1
Joined: Wed Jul 31, 2013 6:31 pm

Re: Transmission cannot connect to tracker

Post by staxtopoutanos »

I had this problem too.After reading some posts and a few re-install ...i changed the "the peer listening port" from manual (51413, the default port).... and checked "Randomize port on launch".It worked.Transmission is for me the best but this issue irritated me a lot hope it will be fixed in future updates.Thanx to the Transmission Team for their work.
harlock59
Posts: 8
Joined: Sat Mar 12, 2011 12:56 am

Re: Transmission cannot connect to tracker

Post by harlock59 »

i have the same issue on transmission 2.92+ on windows
BalleClorin
Posts: 17
Joined: Sun Jan 10, 2010 9:27 pm

Re: Transmission cannot connect to tracker

Post by BalleClorin »

I had a similar problem, and it turned out to be a fault in the "bind-address-ipv6" setting in settings.json.
Post Reply