Latest Deluge Docker container keeps eating memory and crashes

LSIO Discussion Container Support
1

It would seem the latest deluge container keeps crashing and eating memory.

The output of the container log below.
Caught SIGTERM signal!
Tell Deluged to shut down.
s6-supervise svc-deluged: warning: finish script lifetime reached maximum value - sending it a SIGKILL
18:13:14 [INFO ][deluge.configmanager:49 ] Setting config directory to: /config
18:13:14 [INFO ][deluge.core.daemon :1622] Deluge daemon 2.1.1
18:13:14 [INFO ][deluge.core.core :1622] Successfully loaded session.state: /config/session.state
18:13:14 [INFO ][deluge.core.core :1622] Successfully loaded session.state: /config/session.state.bak
18:13:14 [INFO ][deluge.core.alertmanager :1622] Alert Queue Size set to 10000
18:13:14 [INFO ][deluge.core.rpcserver :1622] Starting DelugeRPC server :58846
18:13:14 [ERROR ][deluge.core.daemon_entry :1622] Unable to start deluged: [(‘SSL routines’, ‘’, ‘ee key too small’)]
18:13:14 [INFO ][deluge.core.daemon_entry :1622] Exiting…
Caught SIGTERM signal!
Tell Deluged to shut down.
s6-supervise svc-deluged: warning: finish script lifetime reached maximum value - sending it a SIGKILL
18:13:26 [INFO ][deluge.configmanager:49 ] Setting config directory to: /config
18:13:26 [INFO ][deluge.core.daemon :1622] Deluge daemon 2.1.1
18:13:26 [INFO ][deluge.core.core :1622] Successfully loaded session.state: /config/session.state
18:13:26 [INFO ][deluge.core.core :1622] Successfully loaded session.state: /config/session.state.bak
18:13:26 [INFO ][deluge.core.alertmanager :1622] Alert Queue Size set to 10000
18:13:26 [INFO ][deluge.core.rpcserver :1622] Starting DelugeRPC server :58846
18:13:26 [ERROR ][deluge.core.daemon_entry :1622] Unable to start deluged: [(‘SSL routines’, ‘’, ‘ee key too small’)]
18:13:26 [INFO ][deluge.core.daemon_entry :1622] Exiting…
Caught SIGTERM signal!
Tell Deluged to shut down.

I’m unsure why its currently doing this, none of the others seem to have this issue. I’m sure its something simple that i’v missed somewhere

2

Please provide the output of uname -mr && docker -v, your docker run or compose, and your container logs starting with our ASCII logo. If you use any ui to deploy containers (portainer, Synology, mention that

3

Ubuntu Server
5.15.0-101-generic x86_64
Docker version 26.0.0, build 2ae903e

deluge:
image: lscr.io/linuxserver/deluge:latest
container_name: deluge
security_opt:
- no-new-privileges:true
environment:
- PUID=1000
- PGID=1000
- TZ=Australia/Brisbane
volumes:
- /home/docker/deluge:/config
- /home/Downloads:/downloads
restart: unless-stopped
labels:
traefik.enable: true
networks:
web:

deluge |
deluge | Brought to you by linuxserver.io
deluge | ───────────────────────────────────────
deluge |
deluge | To support LSIO projects visit:
deluge | Donate | LinuxServer.io
deluge |
deluge | ───────────────────────────────────────
deluge | GID/UID
deluge | ───────────────────────────────────────
deluge |
deluge | User UID: 1000
deluge | User GID: 1000
deluge | ───────────────────────────────────────
deluge |
deluge | [custom-init] No custom files found, skipping…
deluge | 21:13:51 [INFO ][deluge.configmanager:49 ] Setting config directory to: /config
deluge | 21:13:51 [INFO ][deluge.core.daemon :1622] Deluge daemon 2.1.1
deluge | 21:13:51 [INFO ][deluge.core.core :1622] Successfully loaded session.state: /config/session.state
deluge | 21:13:51 [INFO ][deluge.core.core :1622] Successfully loaded session.state: /config/session.state.bak
deluge | 21:13:51 [INFO ][deluge.core.alertmanager :1622] Alert Queue Size set to 10000
deluge | 21:13:51 [INFO ][deluge.core.rpcserver :1622] Starting DelugeRPC server :58846
deluge | 21:13:51 [ERROR ][deluge.core.daemon_entry :1622] Unable to start deluged: [(‘SSL routines’, ‘’, ‘ee key too small’)]
deluge | 21:13:51 [INFO ][deluge.core.daemon_entry :1622] Exiting…
deluge | Caught SIGTERM signal!
deluge | Tell Deluged to shut down.
deluge | s6-supervise svc-deluged: warning: finish script lifetime reached maximum value - sending it a SIGKILL
deluge | 21:14:03 [INFO ][deluge.configmanager:49 ] Setting config directory to: /config
deluge | 21:14:04 [INFO ][deluge.core.daemon :1622] Deluge daemon 2.1.1
deluge | 21:14:04 [INFO ][deluge.core.core :1622] Successfully loaded session.state: /config/session.state
deluge | 21:14:04 [INFO ][deluge.core.core :1622] Successfully loaded session.state: /config/session.state.bak
deluge | 21:14:04 [INFO ][deluge.core.alertmanager :1622] Alert Queue Size set to 10000
deluge | 21:14:04 [INFO ][deluge.core.rpcserver :1622] Starting DelugeRPC server :58846
deluge | 21:14:04 [ERROR ][deluge.core.daemon_entry :1622] Unable to start deluged: [(‘SSL routines’, ‘’, ‘ee key too small’)]
deluge | 21:14:04 [INFO ][deluge.core.daemon_entry :1622] Exiting…
deluge | Caught SIGTERM signal!
deluge | Tell Deluged to shut down.
^CGracefully stopping… (press Ctrl+C again to force)
[+] Stopping 1/1
:heavy_check_mark: Container deluge Stopped 11.9s
canceled

4

What’s the output of id docker
and
ls -lan /home/docker/deluge

5

ls -lan /home/docker/deluge
total 4148
drwx------ 9 1000 1000 4096 Mar 28 18:33 .
drwxr-xr-x 36 1000 1000 4096 Jan 6 12:43 …
drwxr-xr-x 2 1000 1000 4096 Mar 10 16:38 archive
-rw------- 1 1000 1000 72 Aug 20 2019 auth
-rw-r–r-- 1 1000 1000 2379917 Mar 23 03:05 blocklist.cache
-rw------- 1 1000 1000 377 Mar 23 03:05 blocklist.conf
-rw-r–r-- 1 1000 1000 308 Jun 24 2019 blocklist.conf~
-rw------- 1 1000 1000 377 Mar 16 03:07 blocklist.conf.bak
-rw-r–r-- 1 1000 1000 315 Mar 16 2023 blocklist.download
-rw------- 1 1000 1000 2988 Feb 12 2022 core.conf
-rw-r–r-- 1 1000 1000 2487 Jan 30 2019 core.conf~
-rw------- 1 1000 1000 2953 Dec 15 2019 core.conf.bak
-rw-r–r-- 1 1000 1000 1396825 Mar 28 21:14 deluged.log
-rw-r–r-- 1 1000 1000 5723 Jun 28 2019 dht.state
-rw-r–r-- 1 1000 1000 231 Jun 18 2015 files_tab.state
-rw-r–r-- 1 1000 1000 1703 Mar 11 2015 gtkui.conf
-rw-r–r-- 1 1000 1000 1666 Mar 8 2015 gtkui.conf~
-rw------- 1 1000 1000 260 Jun 28 2019 hostlist.conf
-rw-r–r-- 1 1000 1000 168 May 8 2015 hostlist.conf.1.2~
-rw-r–r-- 1 1000 1000 168 Jun 18 2015 hostlist.conf.1.2.old
-rw------- 1 1000 1000 209 Jun 28 2019 hostlist.conf.bak
drwxr-xr-x 2 1000 1000 4096 Mar 10 2015 icons
drwxr-xr-x 2 1000 1000 4096 Jun 18 2015 ipc
-rw------- 1 1000 1000 10317 Mar 16 12:04 label.conf
-rw-r–r-- 1 1000 1000 4657 Jun 20 2019 label.conf~
-rw------- 1 1000 1000 10252 Mar 16 02:11 label.conf.bak
-rw-r–r-- 1 1000 1000 296 Jun 18 2015 peers_tab.state
drwxr-xr-x 3 1000 1000 4096 Nov 11 2016 plugins
-rw-r–r-- 1 1000 1000 2327 Mar 28 18:10 session.state
-rw-r–r-- 1 1000 1000 5655 Mar 26 03:04 session.state.bak
drwxr-xr-x 2 1000 1000 4096 Mar 30 2015 ssl
drwxr-xr-x 2 1000 1000 16384 Mar 28 18:10 state
-rw-r–r-- 1 1000 1000 109 Jun 18 2015 tabs.state
drwxr-xr-x 2 1000 1000 4096 Apr 25 2023 torrents
-rw-r–r-- 1 1000 1000 2682 Jun 18 2015 torrentview.state
-rw-r–r-- 1 1000 1000 56 May 18 2015 ui.conf
-rw------- 1 1000 1000 138850 Mar 28 18:10 web.conf
-rw------- 1 1000 1000 138850 Mar 28 17:48 web.conf.bak

id docker
id: ‘docker’: no such user

6

hm /home/docker would’ve implied username is docker, but thats fine :smiley: it can be overridden and permissions look fine.

it seems the root of the issue is 18:13:26 [ERROR ][deluge.core.daemon_entry :1622] Unable to start deluged: [(‘SSL routines’, ‘’, ‘ee key too small’)] but i have no real input as I dont use deluge myself

7

I started running into the same issue on Unraid 6.11.5 within the last few days. Reverting back to 2.0.5 allowed deluge to start again. Looking at the latest commits on github, I could only see Bot Updating Package Versions and then I found someone posted a comment on the commit history: Bot Updating Package Versions · linuxserver/docker-deluge@eac11b7 · GitHub.

I rectified this by simply deleting the daemon.cert and daemon.pkey in the config/ssl directory, and restarting the container. This created new certificates that were to the current standard.

Doing the same in my config/ssl directory worked. It generated new ssl files and deluge container started up on the latest branch.

1 Like
8

Amazing thank you :slight_smile:

9

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.