fyi: For 1.2 you should be using deluge-web as deluge -u web is depreciated. This is more for reference as I doubt this is part of the actual problems you are having.
Thanks for this. I've managed to get 1.2.0 working, by deleting the config folder then starting again with a fresh installation. I can start deluge-web manually, as well as the daemon, or I can run the daemon from inside the web UI. However, the initscript doesn't work. When I try to run it, nothing appears to happen, and the processes aren't started (although they did start once, then they closed very quickly after that). Do I need to reboot before I can test an initscript?
melat0nin wrote:
However, the initscript doesn't work. When I try to run it, nothing appears to happen, and the processes aren't started (although they did start once, then they closed very quickly after that). Do I need to reboot before I can test an initscript?
There is no need to reboot, once the init files are in place you can start and stop through init.d. There is no feedback when you start it so you can check it using ps.
melat0nin wrote:
However, the initscript doesn't work. When I try to run it, nothing appears to happen, and the processes aren't started (although they did start once, then they closed very quickly after that). Do I need to reboot before I can test an initscript?
There is no need to reboot, once the init files are in place you can start and stop through init.d. There is no feedback when you start it so you can check it using ps.
media@media-server:/var/log$ /etc/init.d/deluge-daemon start
start-stop-daemon: Unable to open pidfile `/var/run/deluged.pid' for writing: Permission denied (Permission denied)
start-stop-daemon: Unable to open pidfile `/var/run/deluge-web.pid' for writing: Permission denied (Permission denied)
and with sudo, I get no feedback. Either way, neither the daemon nor the web ui seem to execute. I made sure the permissions were correct on /etc/init.d/deluge-daemon (sudo chmod 755 /etc/init.d/deluge-daemon) but that didn't help.
Thanks for your help! I think I have it working now. I followed the wiki to create the deluge user (I didn't want to do this initially, but in the end I just told deluge to download to my main account's Download folder, and chmodded it to 777, so the end-result is the same), then created the initscripts as detailed in the wiki, and it appears to run fine, including after reboot. Am very happy with the result, and the Ajax web UI in 1.2.0 looks amazing!
melat0nin wrote:Thanks for your help! I think I have it working now. I followed the wiki to create the deluge user (I didn't want to do this initially, but in the end I just told deluge to download to my main account's Download folder, and chmodded it to 777, so the end-result is the same), then created the initscripts as detailed in the wiki, and it appears to run fine, including after reboot. Am very happy with the result, and the Ajax web UI in 1.2.0 looks amazing!
Glad you finally got it working
It is best practice, for security, to create a sandbox user for startup daemon processes. The drawback with deluge, as I found out too, is the resulting file permissions issue.
melat0nin wrote:Thanks for your help! I think I have it working now. I followed the wiki to create the deluge user (I didn't want to do this initially, but in the end I just told deluge to download to my main account's Download folder, and chmodded it to 777, so the end-result is the same), then created the initscripts as detailed in the wiki, and it appears to run fine, including after reboot. Am very happy with the result, and the Ajax web UI in 1.2.0 looks amazing!
Glad you finally got it working
It is best practice, for security, to create a sandbox user for startup daemon processes. The drawback with deluge, as I found out too, is the resulting file permissions issue.
I've just discovered that very problem (permissions). Is it solved by adding umask arguments to the DEAMON1_ARGS and DAEMON2_ARGS lines?