Opened 13 years ago

Closed 13 years ago

#2378 closed Bug (duplicate)

Mac client 1.74 on 10.6 complains, "Announcing too fast"

Reported by: plambert Owned by:
Priority: Normal Milestone: None Set
Component: Transmission Version: 1.74
Severity: Normal Keywords:
Cc: plambert@…

Description

I was seeing this problem occasionally with the 1.74 betas on 10.5. Unfortunately, I upgraded to 1.74 final at about the same time as I upgraded to Snow Leopard (10.6).

Now, nearly all of the torrents that I seed get this error, and don't continue seeding.

The problem never clears up, at least it has not after 2-3 days.

What other info can I provide to help find the problem?

Change History (9)

comment:1 Changed 13 years ago by plambert

  • Cc plambert@… added

comment:2 Changed 13 years ago by charles

I'm not seeing this. What tracker are you getting this message from?

comment:3 Changed 13 years ago by plambert

I have seen it on two unrelated trackers, however at this time, it's not reproducable. How did it know that I filed a ticket? :-)

The tracker where it was happening consistently was 1.tracker.tvtorrents.com.

Thanks!

comment:4 Changed 13 years ago by plambert

It's still happening, though not quite as often.

The torrents end up stopping, until I resume them.

I changed ISPs today, and hoped that'd help, but no difference—it is still happening, sometimes within a few minutes, and sometimes taking a long time.

I have 24 torrents seeding, though few (one or two) are active at any given time.

comment:5 Changed 13 years ago by livings124

Can you try current trunk and see what happens?

comment:6 Changed 13 years ago by livings124

#1844 might overlay with this.

comment:7 Changed 13 years ago by livings124

Also possibly #2388. Can you try running trunk?

comment:8 Changed 13 years ago by plambert

I have run Trunk for about 24 hours now, without seeing the problem.

Hooray!

comment:9 Changed 13 years ago by livings124

  • Resolution set to duplicate
  • Status changed from new to closed

Indeed, this does seem to be a result of #1844 and/or #2388.

Note: See TracTickets for help on using tickets.