Deluge daemon doens't start anymore

General support for problems installing or using Deluge
Post Reply
badabing
New User
New User
Posts: 2
Joined: Tue Jul 28, 2026 6:03 am

Deluge daemon doens't start anymore

Post by badabing »

Code: Select all

[ERROR   ][deluge.core.daemon_entry      :1653] Unable to start deluged: 'unknown name in settings_pack: ignore_resume_timestamps'
Everytime I start deluged now I get this error, even though there is no "ignore_resume_timestamps" on config file. What should I do?
User avatar
ambipro
Moderator
Moderator
Posts: 773
Joined: Thu May 19, 2022 3:33 am
Contact:

Re: Deluge daemon doens't start anymore

Post by ambipro »

Can you elaborate a bit on your setup? Are you running this natively or with Docker? If docker what image? If not Docker have you recently updated or are you running a dev branch? I see you're using Cachy, for some reason I believe this is the nix distro that runs everything in Docker from their "app store" thing, so if so which image (it would be linuxserver or binhex most likely if my memory is correct in this about Cachy)

Context around this error and when it suddenly started appearing can help us figure out what's going on and troubleshoot the issue for you, I have some theories but without anymore information like what I requested above it's just assumptions/guesses, so if you can fill in the blanks I'm sure we can sort you out.
mkvlrn
New User
New User
Posts: 1
Joined: Tue Jul 28, 2026 9:56 pm

Re: Deluge daemon doens't start anymore

Post by mkvlrn »

I had this issue on arch. It was a recent update to libtorrent-rasterbar, so downgrading it to 2.0 fixed the issue for me.
Last edited by mkvlrn on Tue Jul 28, 2026 10:00 pm, edited 1 time in total.
User avatar
ambipro
Moderator
Moderator
Posts: 773
Joined: Thu May 19, 2022 3:33 am
Contact:

Re: Deluge daemon doens't start anymore

Post by ambipro »

If that's indeed the issue with this, then try downgrading to 2.0.9 or earlier, or perhaps give 1.2.x branch a try. If it's running in Docker you could just try a previous image tag instead of latest.

Thanks for the information mkvlrn
badabing
New User
New User
Posts: 2
Joined: Tue Jul 28, 2026 6:03 am

Re: Deluge daemon doens't start anymore

Post by badabing »

I tried downgrading libtorrent-rasterbar to 2.0, but downgrading to anything 2.0.9 or lower gives you:

Code: Select all

  File "/usr/lib/python3.14/site-packages/deluge/_libtorrent.py", line 22, in <module>
    import deluge.libtorrent as lt
ModuleNotFoundError: No module named 'deluge.libtorrent'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.14/site-packages/deluge/_libtorrent.py", line 25, in <module>
    import libtorrent as lt
ModuleNotFoundError: No module named 'libtorrent'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/deluged", line 8, in <module>
    sys.exit(start_daemon())
             ~~~~~~~~~~~~^^
  File "/usr/lib/python3.14/site-packages/deluge/core/daemon_entry.py", line 87, in start_daemon
    from deluge.core.daemon import is_daemon_running
  File "/usr/lib/python3.14/site-packages/deluge/core/daemon.py", line 20, in <module>
    from deluge.core.core import Core
  File "/usr/lib/python3.14/site-packages/deluge/core/core.py", line 25, in <module>
    from deluge._libtorrent import LT_VERSION, lt
  File "/usr/lib/python3.14/site-packages/deluge/_libtorrent.py", line 27, in <module>
    raise LibtorrentImportError('No libtorrent library found: %s' % (ex))
deluge.error.LibtorrentImportError: No libtorrent library found: No module named 'libtorrent'
Then, after downgrading to 2.0.13, it gave me:

Code: Select all

[ERROR   ][deluge.core.daemon_entry      :1653] Unable to start deluged: module 'OpenSSL.crypto' has no attribute 'X509Req'
And after downgrading python-pyopenssl to a version where that attribute still exists, it gave me:

Code: Select all

  File "/usr/bin/deluged", line 8, in <module>
    sys.exit(start_daemon())
             ~~~~~~~~~~~~^^
  File "/usr/lib/python3.14/site-packages/deluge/core/daemon_entry.py", line 87, in start_daemon
    from deluge.core.daemon import is_daemon_running
  File "/usr/lib/python3.14/site-packages/deluge/core/daemon.py", line 20, in <module>
    from deluge.core.core import Core
  File "/usr/lib/python3.14/site-packages/deluge/core/core.py", line 39, in <module>
    from deluge.core.rpcserver import export
  File "/usr/lib/python3.14/site-packages/deluge/core/rpcserver.py", line 29, in <module>
    from deluge.crypto_utils import check_ssl_keys, get_context_factory
  File "/usr/lib/python3.14/site-packages/deluge/crypto_utils.py", line 12, in <module>
    from OpenSSL import crypto
ModuleNotFoundError: No module named 'OpenSSL'
So here I am stuck again...

To elaborate, I am installing Deluge natively from my machine, and no dependency is in Docker or similar. Cachy does not install anything in a Docker, it's a normal distro.
User avatar
ambipro
Moderator
Moderator
Posts: 773
Joined: Thu May 19, 2022 3:33 am
Contact:

Re: Deluge daemon doens't start anymore

Post by ambipro »

That first error shows that you did successfully remove the libtorrent dep, but have not installed any - thus you received the error stating ultimately "No module named 'libtorrent' - I would recommend using a venv to consolidate your deluge installation and its dependencies in one python "instance", or if you are already using a venv then making sure when you install libtorrent that you are installing it inside the venv using the absolute path of the pip binary inside the venv folder you've used for deluge.

Alternatively, if you are using python globally, you should ensure that you install libtorrent's previous versions such as the command given at the top of the pypi page, https://pypi.org/project/libtorrent/2.0.9/ - and ensure that --no-cachedir for good measure to ensure that there is no previously cached version (likely the one you had problems with that was just released) being utilized during the package install.
Post Reply