deluged pauses torrents randomly

[krichter]

After adding a few hundred torrents (now ca. 6500) deluged pauses a few thousands of them randomly.

experienced with 2.0.0.dev7097+e3f5377+201707051516~ubuntu17.04.1 on Ubuntu 17.04

[krichter]

deluged.log is available at ​https://richtercloud.de:451/index.php/s/0KlLQOn3TfY6crb which can't be provided here because of restricted upload size limit which I think I reported before, but can't verify because of #3089.

[bro]

Maybe this will help: ​http://dev.deluge-torrent.org/ticket/2257#comment:3

[krichter]

Maybe this will help: ​​http://dev.deluge-torrent.org/ticket/2257#comment:3

I changed active_dht_limit, active_tracker_limit and active_lsd_limit to values 10 times higher than in the initial one which didn't bring any changes, i.e. torrents can be resumed, but then are paused randomly.

[Cas]

I have extracted these details below from the log. The only slight issue is that we do not log status.paused or status.auto_managed.

The torrent options when adding:

• 'auto_managed': True
• 'add_paused': False
• 'stop_at_ratio': False

Log from update_state:

State from lt was: seeding | Session is paused: False
Torrent state set from "None" to "Paused"

Strangely that outcome contradicts the code:

        elif not session_paused and status.paused and status.auto_managed:
            self.state = 'Queued'
        elif session_paused or status.paused:
            self.state = 'Paused'

Just to note that the actual torrent state is not being changed by Deluge it is simply visual contradiction.

I am thinking there is an issue with libtorrent (1.1.x) and/or with how we update the state of torrents for those with auto-managed flag:

If the torrent is auto-managed (flag_auto_managed), the torrent may be resumed at any point, regardless of how it paused. If it's important to manually control when the torrent is paused and resumed, don't make it auto managed.

If flag_auto_managed is set, the torrent will be queued, started and seeded automatically by libtorrent. When this is set, the torrent should also be started as paused. The default queue order is the order the torrents were added. They are all downloaded in that order. For more details, see queuing.

So to summarise when we show Paused it actually means Queued for auto_managed torrents.

[krichter]

Just to note that the actual torrent state is not being changed by Deluge it is simply visual contradiction.

I can confirm that since downloading torrents in the active section are marked as paused (based on GTK client view).

[Cas]

Milestone renamed

[Cas]

Ticket retargeted after milestone closed

[Cas]

Milestone renamed

[Cas]

Ticket retargeted after milestone closed