[SOLVED] Error: Sorry, minimum announce interval = 20

[roseysd850]

I am getting this error on only one tracker I use, and no one there seems to know what is happening. When something downloads, it downloads just fine, but then pauses when switching to seeding with the error "Error: Sorry, minimum announce interval = 20 sec." No amount of refreshing works. I have to manually remove the torrent and then add it, let it check the pieces, then it will work. I got ltconfig plugin working, but I dont see any settings which look like they would change anything.

[roseysd850]

Any ideaz?

[Cas]

I think you are better asking on libtorrent mailing list.

[roseysd850]

I think you are better asking on libtorrent mailing list.

they're telling me its not libtorrent, its deluge. the tracker is telling me it's not them, its my client.

[Cas]

I saw your discussion on mailing list but you never followed up on it. There was nothing in that discussion that it's not libtorrent related (nor blame Deluge), the actual error message is from your tracker, the only thing Deluge does is prefix it with Error because libtorrent marked it as a tracker Error, which it is. Deluge does nothing to a torrent with a tracker error, other than show the message but you are saying that the torrent is stuck in a paused state and cannot resume it? It is up to you to provide more information logs and screenshots etc...

[roseysd850]

I saw your discussion on mailing list but you never followed up on it. There was nothing in that discussion that it's not libtorrent related (nor blame Deluge), the actual error message is from your tracker, the only thing Deluge does is prefix it with Error because libtorrent marked it as a tracker Error, which it is. Deluge does nothing to a torrent with a tracker error, other than show the message but you are saying that the torrent is stuck in a paused state and cannot resume it? It is up to you to provide more information logs and screenshots etc...

Here's what the libtorrent guys said, and BTW, the issue isn't that im downloading torrents in less than 20 seconds. I have decent internet, but not that speed. Anyway:

> Any ideas?

Check the log to see if deluge ended up announcing to this tracker
within 20 seconds for any torrent. If you complete a download in less
than 20 seconds for instance, perhaps the tracker has a bug where it
considers the "completed" announce to be subject to the minimum announce
interval.

It also appears that deluge doesn't handle torrents in an error state
very well. Deluge need to call clear_error() in order to resume a
torrent in an error state (which explains why you have to remove and
re-add the torrent instead of just starting it again). Perhaps it's a
bit harsh to put the torrent in an error state because the tracker says
there's an error, but it doesn't seem completely unreasonable.

You may also ask the tracker operator exactly what that error message
means (and by "exactly" I mean all the details in when it gets
triggered, for instance, does it apply to event=completed announces? it
probably shouldn't).

If it turns out you are completing torrents in less than 20 seconds, and
everyone agrees that the tracker's behavior is reasonable (which doesn't
sound reasonable to me), libtorrent could be made to honor the minimum
announce interval even for event=completed announces. Assuming this is
the problem that is.
…

[Cas]

I read the mailing list and jumping between here and libtorrent is not a productive discussion.

It is up to you to provide more information logs and screenshots etc...

I have not seen any evidence to provide you with any more help from Deluge p.o.v. I already said that from looking at the code Deluge it is not pausing the torrent, many torrents will error on a tracker but we never stop the torrent. However without you providing more info this discussion is going nowhere.

[roseysd850]

what would help figure this out? I'll post aanything I can•

[Cas]

... provide ... logs and screenshots ...

I thought this was fairly self-explanatory, provide Deluge logs and screenshots of the torrent in paused state...

[roseysd850]

Well, I figured it out after a lot of head banging and a lot of crying.

Turns out SickRage was to blame. In testing libtorrent I could manually download torrents from the problem tracker and they would behave normally. It dawned on me that it was only the ones that were downloaded automatically through SickRage that messed up. Apparently the setting " Seed ratio: -1 (-1 SickRage default to seed forever, or leave blank for downloader default)" screws up deluge. Deleting that value fixed everything. Thanks again for your time in helping me with this.