Daemon occassionally stops listening on chosen port

[einpoklum]

I have a headless deluge daemon running on my Debian Wheezy box. For the past several weeks, I've occasionally come home to notice my client (on another machine) has been disconnected, and the service appears to be down. Doing

Code: Select all

netstat -tna

I see nothing listening on the relevant port.

In the log I see something like this:

Code: Select all

[INFO    ] 11:00:07 rpcserver:203 Deluge Client connection made from: 10.0.0.2:57608
[INFO    ] 11:00:07 rpcserver:203 Deluge Client connection made from: 10.0.0.2:57610
... more of the same...
[INFO    ] 11:00:08 rpcserver:203 Deluge Client connection made from: 10.0.0.2:57631
[INFO    ] 11:00:08 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 11:00:08 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
... more of the same...
[INFO    ] 11:00:08 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 11:00:08 rpcserver:203 Deluge Client connection made from: 10.0.0.2:57633
[INFO    ] 11:00:08 rpcserver:223 Deluge client disconnected: Connection to the other side was lost in a non-clean fashion: Connection lost.
[INFO    ] 11:00:09 rpcserver:203 Deluge Client connection made from: 10.0.0.2:57634

Restarting the daemon fixes things (at least for a few hours or days).

What's going on?

[Cas]

Is deluged crashing?

[RogueElement]

I started having similar problems almost immediately after upgrading to Ubuntu 13.10. I can start deluged from deluge-gtk and things are fine for a while, then everything just stops working. deluged continues to run, but deluge-gtk is no longer connected to it. If I restart deluge-gtk, it can't connect to the instance of deluged that it started. Error logs show "connection refused" errors, as well as errors telling me that I can't launch more than one instance of deluged using the same configuration. I also use Flexget to automate torrents and Flexget will make a connection to deluge, but will hang indefinitely trying to actually send a torrent to it.

I've tried completely removing and reinstalling Deluge, including deleting the configuration directory and rebuilding it all several times. I've gone back through the setup to make sure I'm not missing anything. This was working flawlessly for years without a problem and only recently has been giving me nothing but grief.