Your invoke-rc.d is original, so that's not the problem.
Nevertheless, when the resolvconf job is already started and "invoke-
rc.d resolvconf start" is done, on my system it remains silent (apart
from the "Rather than... start resolvconf" advisory) and exits zero
whereas on your system we see
start: Job is already running: resolvconf
invoke-rc.d: initscript resolvconf, action "start" failed.
The "Rather than... start resolvconf" comes from /lib/init/upstart-job
to which /etc/init.d/resolvconf is a symlink. Here is the relevant
code.
===snip===
case $COMMAND in
start|stop)
$ECHO
$ECHO "Since the script you are attempting to invoke has been converted to
an"
$ECHO "Upstart job, you may also use the $COMMAND(8) utility, e.g. $COMMAND
$JOB"
if status "$JOB" 2>/dev/null | grep -q ' start/'; then
RUNNING=1
fi
if [ -z "$RUNNING" ] && [ "$COMMAND" = "stop" ]; then
exit 0
elif [ -n "$RUNNING" ] && [ "$COMMAND" = "start" ]; then
exit 0
elif [ -n "$DISABLED" ] && [ "$COMMAND" = "start" ]; then
exit 0
fi
$COMMAND "$JOB"
;;
===snip===
Here you see how upstart-job is supposed to exit 0 when the job to be
started is already running. But in your case somehow "$COMMAND $JOB",
i.e., "start resolvconf", is getting run anyway (not necessarily from
the line quoted above).
Please post the output of " md5sum /lib/init/upstart-job".
(I see one possible bug in upstart-job, by the way. Nothing unsets
RUNNING before the aforementioned code block, so if RUNNING happens
already to have some value in the inherited environment then the script
may falsely think that the job is running when it's not. But that can't
be the cause of your problem. A cause of your problem would be
something like: the script falsely thinks that the job is not running
when it is.)
Can you reproduce the failure? If so, can you use shell tracing
features to find out *where* "start resolvconf" gets executed the second
time, when it returns nonzero status?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1041234
Title:
Upgrade of resolvconf from 1.63ubuntu* to 1.63ubuntu15 fails: start:
Job failed to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1041234/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
