[Bug 1041234] Re: Upgrade of resolvconf from 1.63ubuntu* to 1.63ubuntu15 fails: start: Job failed to start

progre55 1041234 at bugs.launchpad.net
Wed Aug 29 23:05:32 UTC 2012


Here is the md5sum output:

# md5sum /lib/init/upstart-job
a62543700eb4d3c63f105a7e85d5e99e  /lib/init/upstart-job

I can see that the start|stop|restart part of my upstart-job looks a bit
different:

=== code ===

start|stop|restart)
    $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"
    PID=$(status "$JOB" 2>/dev/null | awk '/[0-9]$/ { print $NF }')
    if [ -z "$PID" ] && [ "$COMMAND" = "stop" ]; then
        exit 0
    elif [ -n "$PID" ] && [ "$COMMAND" = "start" ]; then
        exit 0
    elif [ -z "$PID" ] && [ "$COMMAND" = "restart" ]; then
        start "$JOB"
        exit 0
    fi
    $COMMAND "$JOB"
    ;;

=== /code ===

Pay attention to the part that says " PID=$(status "$JOB" 2>/dev/null |
awk '/[0-9]$/ { print $NF }') ", and $JOB is resolvconf. So I guess it's
trying to get PID by "status resolvconf"? of course $PID would be null
(or whatever the bash equivalent is).

Here is a debug output:

=== code ===

# sh -x /etc/init.d/resolvconf start
+ set -e
+ basename /etc/init.d/resolvconf
+ INITSCRIPT=resolvconf
+ JOB=resolvconf
+ [ resolvconf = upstart-job ]
+ [ -z start ]
+ COMMAND=start
+ shift
+ [ -z  ]
+ ECHO=echo
+ echo Rather than invoking init scripts through /etc/init.d, use the service(8)
Rather than invoking init scripts through /etc/init.d, use the service(8)
+ echo utility, e.g. service resolvconf start
utility, e.g. service resolvconf start
+ echo

+ echo Since the script you are attempting to invoke has been converted to an
Since the script you are attempting to invoke has been converted to an
+ echo Upstart job, you may also use the start(8) utility, e.g. start resolvconf
Upstart job, you may also use the start(8) utility, e.g. start resolvconf
+ awk /[0-9]$/ { print $NF }
+ status resolvconf
+ PID=
+ [ -z  ]
+ [ start = stop ]
+ [ -n  ]
+ [ -z  ]
+ [ start = restart ]
+ start resolvconf
start: Job is already running: resolvconf

=== /code ===

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1041234

Title:
  Upgrade of resolvconf from 1.63ubuntu* to 1.63ubuntu15 fails: start:
  Job failed to start

Status in “resolvconf” package in Ubuntu:
  Incomplete

Bug description:
  I can see that the other bug (https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/929552) has expired, and it was actually addressing a different version.
  Today I tried applying the pending upgrades on my amazon ec2 based ubuntu 12.04 64-bit server, and got the following error:

  Setting up resolvconf (1.63ubuntu15) ...
  resolvconf start/running
  Processing triggers for resolvconf ...
  start: Job is already running: resolvconf
  invoke-rc.d: initscript resolvconf, action "start" failed.
  dpkg: error processing resolvconf (--configure):
   subprocess installed post-installation script returned error exit status 1
  Errors were encountered while processing:
   resolvconf
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Please tell me what more information I could provide.

  :~$ uname -a
  Linux ### 3.2.0-29-virtual #46-Ubuntu SMP Fri Jul 27 17:23:50 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1041234/+subscriptions




More information about the foundations-bugs mailing list