Opened 13 years ago

Closed 12 years ago

#1359 closed Bug (fixed)

Transmission shows no tracker error when unable to contact the tracker

Reported by: persept Owned by:
Priority: Normal Milestone: 1.40
Component: libtransmission Version: 1.34+
Severity: Normal Keywords:
Cc:

Description

Transmission is not able to contact the tracker and displays Announcing "In Progress" continually for the 15 minutes (so far) since the torrent has been added yet it does not report that there is an error contacting the tracker. I believe in previous versions it would show an error in the main window next to the torrent that couldn't contact the tracker. Also 8:08 PM is the time I added the transfer.

Attachments (1)

web.patch (1.4 KB) - added by fulgas 13 years ago.

Download all attachments as: .zip

Change History (15)

comment:1 Changed 13 years ago by persept

Attatching my image as an example isn't working, I get this error page when I try: http://aieo.us/images/tracerror.html You can see the screenshot though here: http://aieo.us/images/noerror.png

comment:2 Changed 13 years ago by livings124

What version is this?

comment:3 Changed 13 years ago by persept

the latest nightly

comment:4 Changed 13 years ago by charles

Yep, this is a known problem. I'm still tinkering with the new curl code to get it right.

Changed 13 years ago by fulgas

comment:5 Changed 13 years ago by fulgas

Hi, Could it be related to the fact that when the queue is higher than the MAX CONCORRENTS TAKS it won't be processed? since still_running won't be decreased over time?

regards,

Nelson Silva

comment:6 Changed 13 years ago by charles

  • Milestone changed from None Set to 1.40
  • Resolution set to fixed
  • Status changed from new to closed

This is working now for me in trunk. Please reopen this ticket if you see the problem again.

comment:7 Changed 13 years ago by charles

  • Version changed from 1.34 to 1.34+

comment:8 Changed 12 years ago by persept

  • Component changed from Transmission to Mac Client
  • Resolution fixed deleted
  • Status changed from closed to reopened

Ways to replicate on os x. Create a new torrent with any file, set the tracker to a website that doesn't exist. Open the torrent. No error shows up in the transmission window about transmission not being able to contact the tracker. On the other hand, if transmission can contact a tracker and the tracker explicitly returns an error I have seen transmission show the error in the window.

comment:9 Changed 12 years ago by livings124

  • Component changed from Mac Client to libtransmission

I'm seeing this as well.

comment:10 Changed 12 years ago by charles

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

fixed in r6970. If we can't connect to the tracker within 60 seconds, we now timeout, log an error message, and set a time for the next announce attempt.

comment:11 Changed 12 years ago by livings124

  • Resolution fixed deleted
  • Status changed from closed to reopened

I'm still seeing "in progress..." for a tracker that doesn't exist for an indefinite span of time.

comment:12 Changed 12 years ago by charles

livings124: For longer than 60 seconds?

comment:13 Changed 12 years ago by livings124

Yes, hence the "indefinite" ;)

comment:14 Changed 12 years ago by charles

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

Ah, I had been trying to connect to a closed port on a real server. That's the test case that was fixed in r6970. To get the "indefinite" error I had to munge the announce URL's domain name as you mentioned.

Fixed now in r6983.

Note: See TracTickets for help on using tickets.