You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Every time I restart the container, a large number of completed torrents (always the same ones) resume as if they haven't been completed. Additionally, a larger number of torrents are forced into a Checking state. The behavior is as if the torrent state on disk isn't being saved correctly. The deluge logs show the following:
16:18:10 [WARNING ][deluge.core.torrentmanager :1622] Bad shutdown detected so archiving state files 16:18:10 [WARNING ][deluge.common :190 ] Too many existing archives for state. Deleting oldest archive.
I removed perms.txt to reset config file permissions in the container with no change in behavior (some file permissions did change).
The text was updated successfully, but these errors were encountered:
Every time I restart the container, a large number of completed torrents (always the same ones) resume as if they haven't been completed. Additionally, a larger number of torrents are forced into a Checking state. The behavior is as if the torrent state on disk isn't being saved correctly. The deluge logs show the following:
16:18:10 [WARNING ][deluge.core.torrentmanager :1622] Bad shutdown detected so archiving state files 16:18:10 [WARNING ][deluge.common :190 ] Too many existing archives for state. Deleting oldest archive.
I removed perms.txt to reset config file permissions in the container with no change in behavior (some file permissions did change).
The text was updated successfully, but these errors were encountered: