Opened 6 years ago
#3182 new bug
Deluged start with existing lock file crashes local network
Reported by: | gentoofoo | Owned by: | |
---|---|---|---|
Priority: | major | Milestone: | needs verified |
Component: | Core | Version: | 1.3.12 |
Keywords: | Cc: |
Description
If deluged doesn't shut down cleanly (such as after a power failure), the lock file remains in the config directory. Upon trying to start deluged again via ssh I lose all connectivity on the local network where my server is running. I need to shutdown my server and restart my local network before I can connect to my server again. Looking through deluged.log i noticed this:
There is a deluge daemon running with this config directory! You cannot run multiple daemons with the same config directory set. If you believe this is an error, you can force a start by deleting /home/{user}/.config/deluge/deluged.pid
Which led me to deleting the lock file and restarting deluged successfully. Deluge should handle this situation more gracefully