Azureus announce interval

[ColinM]

I'm getting this warning right after starting to seed a new torrent:

Tracker Status: Error (Last announce: 141 secs ago. Please ANNOUNCE less frequently. Cache is only fluched every 3 minutes)

After this, it goes to a 17:00 announce interval with no error listed.

Maybe this is a bug that can't be fixed? Is Azureus hammering the tracker at the first little bit only to be calmed down after the first announce?

[U2Lynne]

I've noticed that Azureus has a very small announce interval at the beginning. I think it does that just while trying to initially connect to the tracker. I don't think it can be change in Azureus though. I would just ignore the error since it corrects itself.

[gsmyth79]

You can change it under Preferences -> Tracker -> Server -> Tracker client poll interval. I put mine at like 600 seconds.

[ColinM]

Originally Posted by gsmyth79

You can change it under Preferences -> Tracker -> Server -> Tracker client poll interval. I put mine at like 600 seconds.

Too bad the wording threw me off. I looked right at that section and moved along because it didn't exactly make sense to me.

Should be:

Tools > Options > Tracker > Server

Maybe my example is only for v2.2.0.2, which is what I'm running.

Thanks.

[gsmyth79]

Originally Posted by ColinM

Maybe my example is only for v2.2.0.2, which is what I'm running.

Thanks.

That might be the difference. Or it could be a Mac/PC thing. Glad you found it though.

I think the setting that gsmyth79 referred to only applies if you are running a tracker through Azureus. I don't think it has any effect on how often Azureus connects to other trackers.

But have a look at Options > Tracker > Client > Read Timeout - Make sure that's set to at least 60s. That might solve the problem. If that doesn't help, try a higher value and see what happens.

EDIT: The more I think about it, it won't make any difference. When you seed in Azureus it makes two announces about 60s apart then after that it depends on the tracker and the number of peers. I think the issue lies with the TTD tracker. So, as Lynne says, ignore it.

[gsmyth79]

Originally Posted by uhclem

I think the setting that gsmyth79 referred to only applies if you are running a tracker through Azureus. I don't think it has any effect on how often Azureus connects to other trackers.

But have a look at Options > Tracker > Client > Read Timeout - Make sure that's set to at least 60s. That might solve the problem. If that doesn't help, try a higher value and see what happens.

Hmmm you may be right. I read somewhere you should make the number I was talking about higher but I can't remember where. My read timeout is at 60 and I haven't had the problem that Colin is talking about ever. And I haven't noticed any difference since I changed the client poll interval either. So that change may make no difference at all. Oh well.

Azureus is such a pain in the ass. BitComet it where it's at!

[ColinM]

Originally Posted by pete's montreux

Azureus is such a pain in the ass. BitComet it where it's at!

I only switched to Azureus from Shadow's 5.8.7 because some sites starting banning it. Fookers!!!

I'm not ready to switch again, so forget it.

Originally Posted by ColinM

I only switched to Azureus from Shadow's 5.8.7 because some sites starting banning it. Fookers!!!

I'm not ready to switch again, so forget it.

Just messing.

[psubliminal]

Originally Posted by pete's montreux

Azureus is such a pain in the ass. BitComet it where it's at!

Bit Comet hammers trackers; on one torrent site I frequent, it is considered the client of choice for leeches and cheats (not saying that applies to you, just that 95% of people banned for cheating or having too low a ratio use Bit Comet). I guess it's possible to somehow fix it so the tracker doesn't know you're downloading; then when you have all the files you start seeding and build up a great share ratio. Bit Lord is another client based on Bit Comet.