Deluge service won't start anymore on Raspbian

[clemenules]

My deluge service won't start anymore, no idea why, apart from running sudo apt update/upgrade I haven't changed anything recently. Has worked flawlessly on my RPi for years, now I'm stumped. Any ideas?

Code: Select all

$ sudo systemctl status deluged.service
deluged.service - Deluge Bittorrent Client Daemon
   Loaded: loaded (/etc/systemd/system/deluged.service; enabled; vendor preset: enabled)
   Active: inactive (dead) since Fri 2022-01-14 22:06:47 CET; 6min ago
  Process: 1654 ExecStart=/usr/bin/deluged -d (code=exited, status=0/SUCCESS)
 Main PID: 1654 (code=exited, status=0/SUCCESS)

Jan 14 22:06:45 raspberrypi systemd[1]: Started Deluge Bittorrent Client Daemon.
Jan 14 22:06:47 raspberrypi deluged[1654]: [ERROR   ] 22:06:47 rpcserver:378 Couldn't listen on any:58846: [Errno 98] Address already in use.
Jan 14 22:06:47 raspberrypi systemd[1]: deluged.service: Succeeded.

and

Code: Select all

 $ sudo nano /etc/systemd/system/deluged.service

[Unit]
Description=Deluge Bittorrent Client Daemon
After=network-online.target

[Service]
Type=simple
User=deluge
Group=deluge
UMask=000

ExecStart=/usr/bin/deluged -d

Restart=on-failure

# Configures the time to wait before service is stopped forcefully.
TimeoutStopSec=300

[Install]
WantedBy=multi-user.target

Also

Code: Select all

$ netstat | grep 58846

Doesn't return anything. So why all of a sudden is Deluge complaining the port is taken?

[zone4444]

Try this please:

Code: Select all

sudo lsof -i :58846

[clemenules]

sudo lsof -i :58846 didn't return anything.

Executing (random, to me, because I don't understand what I'm doing) the following based on some search result:

Code: Select all

$ sudo rm /var/lib/deluge/.config/deluge/deluged.pid

seemed to get it working again. No idea why. I'd like to understand a little better though, any clues?

[zone4444]

I might be wrong... but I think you already had an instance of the deluged service running, thus why the port was taken. Executiing rm .pid might have just terminated the old instance allowing you to run the deluge daemon once more.