Cas wrote: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.
…