Post Sun Nov 18, 2012 3:42 am

Upstart On Ubuntu Desktop 12.10

Serviio 1.0.1 working just great under Ubuntu Desktop 12.10.

created a /etc/init/serviio.conf which looks like so:

  Code:
start on (started network-interface
or started network-manager
or started networking)
expect daemon
script
exec 2>>/dev/.initramfs/serviio.log
set -x
   exec /home/user/serviio-1.0.1/bin/serviio.sh
end script


I have quadruple-checked that a /home/user/serviio-1.0.1/bin/serviio.sh exists with permissions -rwxrwxrwx user user

Manually issuing a 'sudo service serviio start' command works just fine but the service isn't starting at boot.


cat /dev/.initramfs/serviio.log results in the following:

-----------------------------
+ exec /home/user/serviio-1.0.1/bin/serviio.sh
/proc/self/fd/9: 4: exec: /home/user/serviio-1.0.1/bin/serviio.sh: not found
-----------------------------

sudo cat /var/log/upstart/serviio.log yields:

-----------------------------
/bin/sh: 1: exec: /home/user/serviio-1.0.1/bin/serviio.sh: not found
-----------------------------

So far as I've been able to tell this means that /home/user/serviio-1.0.1/bin/serviio.sh does not exist or cannot be read at the time upstart is attempting to run the /etc/init/serviio.conf job I created above.

But as I mentioned I have quadruple-checked every character in this path it is correct. My only suspiciion is that I'm using an encrypted fs however from what I gather from some skimming of the Upstart cookbook it seems as though encrypted filesystems have to be up before the initial Upstart start itself.

My drive is <2TB as well although I'm not even sure that would matter by the time upstart begins.

Anyone got an idea as to what gives? I'm grasping at straws here.

Thanks!