Upstart – Command Runs in Bash but Not from /etc/init: Troubleshooting

initupstart

I'm having some trouble with this init script.

When I run the command I'm passing to start-stop-daemon from the command line it works perfectly, even if I run it sudoed as the userid in the script, but for some reason the command:

sudo service start deluged

prints this:

deluged start/stopping

but I can't see any deluged processes using top, htop or ps aux, and I can't connect to it on the port it's supposed to be listening to (or any other port).

I'm out of ideas for what to try next. Running the init script fails before anything is written to the logfile, so I have no idea what's going wrong.

I'm 100% convinced the user and group exist and aren't typoed, but it's possible they're misconfigured in some way, since I made them manually and might have missed something. I'm also pretty sure that user has permission to access all the relevant files for the program.

Here's the script, I have no idea what I've done wrong (and I took most of this from the deluged documentation anyway!)

#deluged - Deluge daemon                                                                                                                         
#                                                                                                                                                 

# The daemon component of Deluge BitTorrent client. Deluge UI clients                                                                             
# connect to this daemon via DelugeRPC protocol.                                                                                                  



description "Deluge daemon"                                                                                                                       
author "Deluge Team"                                                                                                                              

start on filesystem and static-network-up                                                                                                         
stop on runlevel [016]                                                                                                                            

respawn                                                                                                                                           
respawn limit 5 30                                                                                                                                

env uid=debian-deluged                                                                                                                            
env gid=debian-deluged                                                                                                                            
env umask=007                                                                                                                                     

exec start-stop-daemon -S -c $uid:$gid -k $umask -x /usr/bin/python /usr/bin/deluged -L info -l /var/log/deluged/server.log -c /var/opt/deluged/config -p 8112 -- -d

Best Answer

The deluge docs have something similar to yours but I think this is a hangover from very old versions of Upstart. I'd try simplifying it down to something like this first:

description "Deluge daemon"
author "Deluge Team"

start on filesystem and static-network-up
stop on runlevel [016]

respawn
respawn limit 5 30

setuid debian-deluged
setgid debian-deluged
umask 007

exec /usr/bin/python /usr/bin/deluged -L info -l /var/log/deluged/server.log -c /var/opt/deluged/config -p 8112 -- -d

And then if that still doesn't work, check the permissions on /var/log/deluged/ and /var/log/deluged/server.log (that the debian-deluged user can write there). If it's still not working then, the upstart log files might help you out. Yours will be /var/log/upstart/deluged.log. If that shows nothing, we could just try launching the command as the right user:

sudo -u debian-deluged -g debian-deluged /usr/bin/python /usr/bin/deluged -L info -l /var/log/deluged/server.log -c /var/opt/deluged/config -p 8112 -- -d

Related Solutions

Ubuntu – upstart config to start sync daemon as non-root user

I think this should do it:

exec su -c command_to_execute - $RUN_AS_USER

Init vs Init.d – Difference Between /etc/init/ and /etc/init.d/

/etc/init.d contains scripts used by the System V init tools (SysVinit). This is the traditional service management package for Linux, containing the init program (the first process that is run when the kernel has finished initializing¹) as well as some infrastructure to start and stop services and configure them. Specifically, files in /etc/init.d are shell scripts that respond to start, stop, restart, and (when supported) reload commands to manage a particular service. These scripts can be invoked directly or (most commonly) via some other trigger (typically the presence of a symbolic link in /etc/rc?.d/).

/etc/init contains configuration files used by Upstart. Upstart is a young service management package championed by Ubuntu. Files in /etc/init are configuration files telling Upstart how and when to start, stop, reload the configuration, or query the status of a service. As of lucid, Ubuntu is transitioning from SysVinit to Upstart, which explains why many services come with SysVinit scripts even though Upstart configuration files are preferred. In fact, the SysVinit scripts are processed by a compatibility layer in Upstart.

.d in directory names typically indicates a directory containing many configuration files or scripts for a particular situation (e.g. /etc/apt/sources.list.d contains files that are concatenated to make a virtual sources.list; /etc/network/if-up.d contains scripts that are executed when a network interface is activated). This structure is usually used when each entry in the directory is provided by a different source, so that each package can deposit its own plug-in without having to parse a single configuration file to reference itself. In this case, it just happens that “init” is a logical name for the directory, SysVinit came first and used init.d, and Upstart used plain init for a directory with a similar purpose (it would have been more “mainstream”, and perhaps less arrogant, if they'd used /etc/upstart.d instead).

¹ _{not counting initrd}

Best Answer

Related Solutions

Ubuntu – upstart config to start sync daemon as non-root user

Init vs Init.d – Difference Between /etc/init/ and /etc/init.d/

Related Question