Upstart scripts can't be started/stopped manually following upgrade to 12.04 from 10.04

[Jean-Yves Avenard]

Starting / stopping a script is done as follow:
$ sudo service mythtv-backend stop
or
$ sudo service mythtv-backend start

following an upgrade from 10.04 to 12.04, this always return the error:
/usr/bin/service: 123: exec: stop: not found

$ ls -l /sbin/stop
lrwxrwxrwx 1 root root 7 Apr 27 01:26 /sbin/stop -> initctl

$ sudo /etc/init.d/mythtv-backend stop
Rather than invoking init scripts through /etc/init.d, use the service(8)
utility, e.g. service mythtv-backend stop
/etc/init.d/mythtv-backend: 54: /etc/init.d/mythtv-backend: initctl: not found

it is possible to do it manually with:
$ /sbin/stop mythtv-backend

[Jean-Yves Avenard (jyavenard)]

it seems that the service script assumes that /usr/sbin is in the PATH ; when /usr/sbin isn't ; it will fail.

[Mario Limonciello (superm1)]

Something went wrong with the transition I think. What version of mythtv were you running on 10.04? To reproduce this, probably need to do that upgrade as well.

[Mario Limonciello (superm1)]

Oh but reading that further, the issue is an upstart issue? /usr/sbin/ needing to be in $PATH? Why isn't /usr/sbin in your path? Was this something you manually changed,?

[kusemuckl (kusemuckl)]

Just did an update from 11.10 to 12.04 and have exactly the same problem.

[kusemuckl (kusemuckl)]

For me the problem was, that I did not accept the new sudoers file, because I had made changes.
However the new file would have included the line

Defaults secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

which solves the problem for me.

[Thomas Mashos (tgm4883)]

We really do appreciate you opening this ticket to help improve Mythbuntu, but it needs to be closed for a number of reasons. The biggest one is that upstream has moved on to a new version and believes this to be fixed. Could you please verify if this issue still exists in the latest version?

Please do not let the closing of this ticket dissuade you from opening a new ticket if this (or any other) problem occurs with the newer versions.