deluged and deluge-web violate home dir when they should not

[Xebec]

Binary package hint: deluge

Summary: deluged with deluge-web silently fail to start during system start.
$ deluged --version
1.2.3

I have a Karmic with home dir encryption on. Followed this guide: http://dev.deluge-torrent.org/wiki/UserGuide/InitScript/Ubuntu to set up the daemon on startup. DAEMON1_ARGS and DAEMON2_ARGS were edited to avoid unmounted home directory:

DAEMON1_ARGS="-d -c /media/raid5/deluge_config/deluge -L debug -l /media/raid5/deluge_config/deluged.log"
DAEMON2_ARGS="-c /media/raid5/deluge_config/deluge -L debug -l /media/raid5/deluge_config/deluged.log"

Since deluged dies silently, I could only deduce the reason of its failure from the following:

1. When I execute the following, the configuration at /media/raid5/deluge_config/deluge is picked up and both daemons always start successfully:
sudo /etc/init.d/deluge-daemon start
2. When I change the user to the one that does not have home folder encryption, the daemons start successfully on reboot.

I removed all references to my home folder from all deluge config files - did not help.

[Cas (calumlind)]

 Would be helpful to know if this still happens with 1.3.2?

[Launchpad Janitor (janitor)]

[Expired for deluge (Ubuntu) because there has been no activity for 60 days.]

[TToft (ttoft)]

Newest deluge and ubuntu still does this.

[Cas (calumlind)]

Can you please enable debug logging to see what errors are produced.

[Cas (calumlind)]

Reviewing this I can only conclude that there is not an issue with Deluge but with start-stop-daemon failing to start because the location that you are using to store the config and log files is not available. It suggests that the mount point is not available at the point that deluge init script is being run and as expected start-stop-daemon will quietly fail.

If there was any issue with deluged/deluge-web starting and not finding a directory etc. then there would be error log output in /media/raid5/deluge_config/deluged.log.

Just to add that in the OP init script details, for DAEMON2_ARGS the log file name is the same as in DAEMON1_ARGS so will be clobbered.