[Deluge/2.1.1 libtorrent/2.0.8.0] docker image doesn't work anymore

[flashback]

Hi all, I've been using deluge since years, and dockered deluge for more than one year now.
I'm actually running other dockers inside a raspberry pi 4:
Linux raspi-guard 6.1.19-v8+ #1637 SMP PREEMPT Tue Mar 14 11:11:47 GMT 2023 aarch64 GNU/Linux
and other dockers works perfectly:

docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
de350c237aea ugeek/webdav:arm64 "/bin/sh -c '/entryp…" 18 hours ago Up 18 hours 0.0.0.0:8080->80/tcp webdav
e407bbffa7db amir20/dozzle:latest "/dozzle" 18 hours ago Up 18 hours 0.0.0.0:8087->8080/tcp dozzle
1ea6a7e694fe portainer/agent:latest "./agent" 18 hours ago Up 18 hours 0.0.0.0:9001->9001/tcp agent
8c6976401634 adguard/adguardhome "/opt/adguardhome/Ad…" 18 hours ago Up 18 hours adguardhome-raspi
75584fff93c1 portainer/portainer-ee:latest "/portainer" 5 weeks ago Up 3 days 0.0.0.0:8000->8000/tcp, 0.0.0.0:9443->9443/tcp, 9000/tcp portainer

This is the configuration inside docker-compose.yml:

deluge:
image: linuxserver/deluge:latest
container_name: deluge
ports:
- "6881:6881"
- "6881:6881/udp"
- "8112:8112"
network_mode: host
environment:
- PUID=1000
- PGID=1000
- TZ=Europe/Rome
# - UMASK_SET=022 #optional
- DELUGE_LOGLEVEL=debug #optional
volumes:
- /media/share9/parziali/:/downloads
- /media/share9/dockers/deluge/config:/config
restart: unless-stopped

Since a few days the dockered deluge starts but suddenly exits with (just the latter part of the logs):

11:16:35 [DEBUG ][deluge.core.alertmanager :1622] Alerts queued: 1
11:16:35 [DEBUG ][deluge.core.alertmanager :1622] session_stats_alert: session stats (291 values): 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 7, 0, 0, 39, 18, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,0, 0, 0, 0, 0, 0, 0, 1932, 0, 0, 0, 1120, 0, 0, 0, 40, 0, 69, 0, 10448, 7424, 0, 0, 0, 0, 1, 85, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 34, 8, 0, 0, 0, 0, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 0
11:16:35 [DEBUG ][deluge.core.alertmanager :1622] Handling alert: session_stats_alert
11:16:35 [DEBUG ][deluge.core.alertmanager :1622] Alerts queued: 1
11:16:35 [DEBUG ][deluge.core.alertmanager :1622] session_stats_alert: session stats (291 values): 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 8, 0, 0, 39, 18, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,0, 0, 0, 0, 0, 0, 0, 1932, 0, 0, 0, 1120, 0, 0, 0, 40, 0, 69, 0, 10448, 7424, 0, 0, 0, 0, 1, 85, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 34, 8, 0, 0, 0, 0, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 0
11:16:35 [DEBUG ][deluge.core.alertmanager :1622] Handling alert: session_stats_alert
[ls.io-init] done.
11:16:36 [DEBUG ][deluge.core.alertmanager :1622] Alerts queued: 1
11:16:36 [DEBUG ][deluge.core.alertmanager :1622] session_stats_alert: session stats (291 values): 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 0, 0, 39, 18, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0,0, 0, 0, 0, 0, 0, 0, 1932, 0, 0, 0, 1120, 0, 0, 0, 40, 0, 69, 0, 10448, 7424, 0, 0, 0, 0, 1, 85, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 34, 8, 0, 0, 0, 0, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 0
11:16:36 [DEBUG ][deluge.core.alertmanager :1622] Handling alert: session_stats_alert
11:16:36 [DEBUG ][deluge.core.alertmanager :1622] Alerts queued: 1
11:16:36 [DEBUG ][deluge.core.alertmanager :1622] session_stats_alert: session stats (291 values): 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 10, 0, 0, 40, 18, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1960, 0, 0, 0, 1148, 0, 0, 0, 41, 0, 70, 0, 10552, 7734, 0, 0, 0, 0, 2, 85, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 34, 8, 0,0, 0, 0, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 0
11:16:36 [DEBUG ][deluge.core.alertmanager :1622] Handling alert: session_stats_alert
11:16:36 [INFO ][deluge.ui.web.server :1622] Shutting down webserver
11:16:36 [DEBUG ][deluge.ui.web.server :1622] Saving configuration file
11:16:36 [WARNING ][deluge.config :477 ] Unable to open config file: /config/web.conf because: [Errno 2] No such file or directory: '/config/web.conf'
11:16:36 [DEBUG ][deluge.config :485 ] Saving new config file /tmp/web.conf.p53dg1xo
11:16:36 [DEBUG ][deluge.config :499 ] Backing up old config file to /config/web.conf.bak
11:16:36 [WARNING ][deluge.config :502 ] Unable to backup old config: [Errno 2] No such file or directory: '/config/web.conf'
11:16:36 [DEBUG ][deluge.config :507 ] Moving new config file /tmp/web.conf.p53dg1xo to /config/web.conf
11:16:37 [INFO ][deluge.core.daemon :1622] Deluge daemon shutting down, waiting for components to shutdown...
11:16:37 [DEBUG ][deluge.core.core :1622] Core stopping...
11:16:37 [INFO ][deluge.core.core :1622] Saving the session.state at: /config/session.state
11:16:38 [DEBUG ][deluge.core.torrentmanager :1622] Creating the temporary file: /config/state/torrents.state.tmp
11:16:38 [DEBUG ][deluge.core.alertmanager :1622] Alerts queued: 1
11:16:38 [DEBUG ][deluge.core.alertmanager :1622] session_stats_alert: session stats (291 values): 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 11, 0, 0, 40, 18, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 1960, 0, 0, 0, 1148, 0, 0, 0, 41, 0, 70, 0, 10552, 7734, 0, 0, 0, 0, 2, 85, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 34, 8, 0,0, 0, 0, 107, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 9, 0
11:16:38 [DEBUG ][deluge.core.alertmanager :1622] Handling alert: session_stats_alert
11:16:38 [DEBUG ][deluge.core.torrentmanager :1622] Creating backup of torrents.state at: /config/state/torrents.state.bak
11:16:38 [DEBUG ][deluge.core.torrentmanager :1622] Saving torrents.state to: /config/state/torrents.state
11:16:38 [DEBUG ][deluge.core.daemon :1622] Remove pid file: /config/deluged.pid
11:16:38 [INFO ][deluge.core.daemon :1622] Deluge daemon shutdown successfully
11:16:38 [INFO ][deluge.core.daemon_entry :1622] Exiting...
Caught SIGTERM signal!
Tell Deluged to shut down

I tried deleting the content of configure directory to let the process create new config files, with no results.
I can post the entire logs if it's usefull, obviously I used the debug option.
In the full logs I can't find anything like an error, the first words of every rows are just DEBUG or INFO.

Can anybody try to help me figuring out the problem ?

Thank you.

[mhertz]

Sorry I have no good help i'm afraid. As you say, the logs are clean so not really usefull, except it states to have catched a sigterm, so sounds like something tried close it. I know libtorrent 2.x uses a lot of cached memory and some have reported OOM issues because of it i.e. crashes, I googled quickly, and found some pi4 users have issues with bigger files crashing the app, rsync, dd and transmission etc. It was also speculated being because of faulty USB driver or something, and possibly zfs. I googled if oom-killer doesn't just send sigkill signal, so ruled out here, but read it can either send sigterm followed by sigkill, or just sigkill alone, so could still be the case from your logs I presume.

If you use systemd, then could try adding a 'MemoryMax=1G' or something, to your deluged sevice file.

Also, as workaround, and as you say only happened recently, then could try an older tag of the image, so in your compose file you change 'latest' to instead a tag, which you can find here: https://hub.docker.com/r/linuxserver/deluge/tags?page=1. Then 'stop' and 'rm' the image and rebuild it.

Also, you can check if you actually had an OOM issue, with grepping dmesg or syslog etc for kill or oom etc.

Anyway, sorry no easy help and just some random theories, and hopefully others can help you better thanks.

Good luck.

[flashback]

Hi, thanks anyway for the answer, it's something to think about.
Nevertheless I'm using this since a few months with no problems, just a couple days ago I realized it's broken (without any major change to the system that I remember).
I use this script (maybe it's usefull for somebody) to stop (if running), delete container (if any), delete image (if any), and the pull it again:

container=`docker ps | grep deluge`
if [ $container ]; then
echo "quitting deluge.,"
docker stop deluge
else
echo -ne "\nno running deluged daemons, deleting the container.."
for a in $(docker container ls -a | grep deluge | awk '{print $1}'); do echo -n $a; docker rm $a 1>&2>/dev/null; done
echo -ne "..and the image.."
for a in $(docker images | grep deluge | awk '{print $3}'); do echo $a; docker rmi --force $a 1>&2>/dev/null; done
echo -e "\nnow downloading the image and then start it..\n"
docker-compose -f /media/share9/dockers/docker-compose.yml up -d deluge
echo -e "\nand now logs..\n"
docker logs -f deluge
fi

and then recreate the container with docker-compose.

No weird messages on dmesg, usual stuff.
Is there somebody willing to take a look at the full logs searching for an error ?

Thank you.

[mhertz]

You're welcome, and btw, i'm sorry about the systemd comment, as got confused momentarilly, sorry.

Anyway, if you're not getting help from others later, then can send it to me if wanted, but note it has no error's, as per your own comment in first post(info and debug solely).

Last, check also the docker logs, first 'sudo docker logs deluge', and then general e.g. sudo systemctl status docker, or from journalctl -xu docker etc. Also can enable debug-logging for more output, guide here: https://docs.docker.com/config/daemon/logs/

Anyway as said, please others post if having any tips or thoughts in general.

[flashback]

Hi, I need to investigate further, but the problem has gone simply changing the container_name inside docker-compose.yml.
Thank you fopr the quick answer and support.

[tg44]

I have a same but different issue. Both with latest 2.1.1 and 2.0.5 the daemon starts, the webui comes up, it shows that the daemon online, I can connect to it, and after about 2 minutes the ui says that the daemon went offline, but actually the daemon runs on the server without an issue, it just stops to speak with the WebGUI. With every restart I can do things on the GUI for about 1-2 minutes. There is nothing in the logs. (I tried the debug logs too, but literally nothing.) I tried to read back for similar issues, with not much luck. I'm open to any ideas...

(My system drive failed 2 days ago, but I restarted the compose files on the hdds "as is" after a new ssd and os install, which means new latest container versions, which means new bugs in the new versions I had the same configs from before, only the version should be different, and I have no idea what was the previous one.)

[mhertz]

Do docker logging reveal anything relevant e.g 'sudo docker logs deluge' ?

If haven't already, then try a clean profile, e.g copy /config to other place momentarily, and delete it for a clean test(with Deluge stopped).

Is it the Linux-server image(lsio)?

[basher]

What mhertz said. Also try logging on debug level and see if anything useful is spit out.

[tg44]

I tried the debug level, nothing relevant appeared. I tried with empty config, and it seems to work (but I'm not sure bcs it seems to die after some torrents getting active). The problem is migrating the list of torrents (I tried to move the *.torrent-s from config/state, but I think its not that easy to bootstrap back a new instance).

Image is;

Code: Select all

linuxserver/deluge:2.0.5

In the logs I have;

Code: Select all

on_alert_performance:  - : performance warning: upload limit too low (download rate will suffer), upload_limit_too_low`

Code: Select all

on_alert_performance: xxxx: performance warning: max outstanding piece requests reached, outstanding_request_limit_reached`

But as I researched these, they should be normal.

[ambipro]

I tried the debug level, nothing relevant appeared. I tried with empty config, and it seems to work (but I'm not sure bcs it seems to die after some torrents getting active). The problem is migrating the list of torrents (I tried to move the *.torrent-s from config/state, but I think its not that easy to bootstrap back a new instance).

Image is;

Code: Select all

linuxserver/deluge:2.0.5

In the logs I have;

Code: Select all

on_alert_performance:  - : performance warning: upload limit too low (download rate will suffer), upload_limit_too_low`

Code: Select all

on_alert_performance: xxxx: performance warning: max outstanding piece requests reached, outstanding_request_limit_reached`

But as I researched these, they should be normal.

We'd need full logs of when the problem is occurring, not two snippets of single lines, that's not helpful....and these aren't errors at all.

Also, you are using a different version of deluge, which is outdated and 2.1.1 is available from linuxserver's repo, I'd advise you try updating... and see if that resolves your issue.

Finally, to migrate the torrents list, you'll need to copy the entire "state" folder, not just the .torrents, unless you want to recheck all torrent files I guess. Up to you on that front. Also you may want to copy your plugins folder if you use any, and core.conf if you don't want to reset your settings, but that would only take a few minutes at most.

I'd suggest instead of posting your issue in someone else's thread, make your own with a title relevant to your situation (version, issue, etc) as well as provide full logs of when the situation is occurring if you still have issues after upgrading and all that.

Even if you don't see something, we might.