2.3 Connection failed error

Ask for help and report issues with the Mac OS X version of Transmission
Jordan
Transmission Developer
Posts: 2312
Joined: Sat May 26, 2007 3:39 pm
Location: Titania's Room

Re: 2.3 Connection failed error

Post by Jordan »

My mail is jordan @ tra... ...bt.com
Oyseka
Posts: 4
Joined: Thu May 26, 2011 4:18 am

Re: 2.3 Connection failed error

Post by Oyseka »

OK thanks, I have mailed them to you.
danex
Posts: 1
Joined: Thu Jun 02, 2011 2:36 am

Re: 2.3 Connection failed error

Post by danex »

I have the same issue but after calling my isp (as I had changed the settings for my netcom nb7 modem to allow the peer listening port to be open in transmission as it always says closed) I had this connection failed issue after a few minutes of downloading. I reset the modems initial settings and transmission still downloads even though the port is closed. Also after transmissions connections failed and wouldn't download anything my internet browswer wouldn't open any pages. So maybe its changing the modem settings?
CrashWarez
Posts: 3
Joined: Sat Jun 04, 2011 2:52 am

Re: 2.3 Connection failed error

Post by CrashWarez »

Ok, i have seem the same error in my mac... Why can i help you developers to fix it? i have take some ss to send for you guys.

I see that a friend already send some SS, but if you need, i can send more. At First i think that was in magnetic function, but i have try download torrents with the original torrent and the problem still on.. Its no the tracker because i try a several trackers and nothing. Iam from Brazil.

Nevertheless, I would say that this is the best torrent app i have ever seen. Thansks and congratulations to the team of Developers.
CrashWarez
Posts: 3
Joined: Sat Jun 04, 2011 2:52 am

Re: 2.3 Connection failed error

Post by CrashWarez »

sorry, i wanted to have said "how".
lazybones
Posts: 220
Joined: Sun Jan 24, 2010 12:41 am

Re: 2.3 Connection failed error

Post by lazybones »

Using the daemon I have seen issues with two very common public trackers when they are listed as udp:// however transmission can connect to them when they are listed as http. Other udp trackers seem to work fine.
Endavent
Posts: 4
Joined: Sun May 22, 2011 3:55 pm

Re: 2.3 Connection failed error

Post by Endavent »

I tried version 2.32 and I still have the same problem : no error message, no yellow warning, but no more downloads or uploads !

Since 2.3 I can't no more exchange data with other users ...

Reverting to old 2.22 works each time, hopefully. I'm stuck with it, anyway
johnea
Posts: 3
Joined: Sat Jul 23, 2011 7:20 pm

Re: 2.3 Connection failed error

Post by johnea »

OK, I've RTFM'd and I've installed the latest svn r12579.

I'm still seeing the widespread incidence of announce errors:

Mostly - Tracker gave HTTP response code 0 (No Response)
Some - Peer not found 2b5385...long hash

I'm not on the MAC platform, but headless linux via the web interface. I'm not sure if this should be posted in a separate thread in the Web interface board, since my symptoms are exactly as described in this thread.

This is definitely related to which tracker is involved. Some trackers give the error consistently (and yet torrents still seed), others will work for a while and then give the error, other work without fail and never give the error.

I think maybe the torrents that are still seeding while announce error is present may be through DHT.

If the torrent is still working, I guess this could be considered a user interface bug, since the error message overwrites the number of seeds/leaches and xfer rates on the torrent status line.

Don't know if it's related, but in the web interface, in the Inspector/Tracker tab, The Seeders/Leachers/Downloads stats are often all 0 or N/A on trackers that are giving the announce errors.

An example of two trackers that are consistently giving the return 0 announce error:
http://tracker.archlinux.org:6969 - running opentracker
http://torrents.freebsd.org:8080 - running XBNBT 85b.1.1 SVN 335 Flat-File Release based on BNBT Beta 8.5 CVS

An example of two trackers that have never given an announce error:
http://tracker.bakabt.com:2710 - running in-house custom coded tracker
http://tracker.tracker.example.com:80 - don't know which tracker package is in use
(interesting, apparently one is not allowed to type m i n i n o v a . o r g here, it comes out tracker.example.com )
(per forum rules: I don't think these tracker names are "private information" these are all publicly accessible servers)

There are other trackers (including most dedicated public tracker sites) that give errors intermittently.

So I would say a recipe to recreate the error would be to seed the archlinux core dual iso. Torrent file found here:
http://www.archlinux.org/iso/2010.05/ar ... so.torrent

Please advise if I should start a new thread in Web interface board or file a trac ticket.

Thank you for a great BT client! I hope I can contribute to overcoming this issue...

johnea
johnea
Posts: 3
Joined: Sat Jul 23, 2011 7:20 pm

Re: 2.3 Connection failed error

Post by johnea »

Hi x190,

I can see why you'd have a hard time finding that torrent given the way forums rewrite user's text.

Those ...'s are so confusing. Maybe that little check box at the bottom should say:
"Do not automatically mangle URLs" 8-)

The fact that it's the archlinux core dual iso torrent might have led you to it, or not

Here I'll put it in some quote meta so it's all nice:
http://www.archlinux.org/iso/2010.05/ar ... so.torrent

Let me know if you need any more help finding it. Thanx...

johnea
johnea
Posts: 3
Joined: Sat Jul 23, 2011 7:20 pm

Re: 2.3 Connection failed error

Post by johnea »

Thanks for looking at this.

I've attached a screenshot of the return 0 announce error message obscuring the number of peers and upload/download rate stats in the web ui.

Did you see this when you let the download start?

If I delete the torrent and readd, the UL/DL rates show at first, then this announce error message obscures them. In all cases the torrent continues to seed.

Sometimes half of the torrents in the active tab have this, or the "peer not found" announce error, covering their stats.

Should I file a trac ticket as a Web User Interface issue?

Thanks again!

johnea

p.s. That ratio in the screenshot is obviously not right, but that's a different bug 8-)
Attachments
announce error message obscuring per torrent stats in web ui even though torrent continues to seed
announce error message obscuring per torrent stats in web ui even though torrent continues to seed
announce-error-obscuring-stats.png (9.15 KiB) Viewed 4110 times
Post Reply