[Bug 543506] Re: Some services not started on boot, runlevel returns "unknown"

Michael Gorven michael at gorven.za.net
Tue Jul 19 14:34:03 UTC 2011


*** This bug is a duplicate of bug 554172 ***
    https://bugs.launchpad.net/bugs/554172

I ran into this on a machine upgraded from Karmic to Lucid. The problem
was that the ifupdown package hadn't been upgraded (it was on 0.6.8nmu+1
IIRC) and the upstart init files for networking weren't in /etc/init
(which meant that lo was never started and so rc-sysvinit was never
started). Installing Lucid's ifupdown package fixed the problem.

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

Title:
  Some services not started on boot, runlevel returns "unknown"

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: upstart

  On Lucid with:

  # apt-cache policy upstart
  upstart:
    Installed: 0.6.5-4
    Candidate: 0.6.5-4
    Version table:
   *** 0.6.5-4 0
          500 http://apt.interlinx.bc.ca lucid/main Packages
          100 /var/lib/dpkg/status

  during boot, upstart just seems to stop starting jobs.  A number of
  jobs are started but all of the jobs that should be started never gets
  complete.  I end up (though having a job that starts a shell on a tty)
  having to manually:

  # service ssh start
  # service rc-sysinit start
  (at least)

  to get the system up into a semblance of a multi-user run-level.

  I'd be happy to provide more information but I'm at a bit of a loss as
  to how to debug this situation.

  FWIW, my "debug shell" job which gives me a shell that I can debug
  upstart from is:

  description     "Start a debug shell"

  start on startup

  expect fork

  script
      exec /root/open -c 12 /bin/bash
  end script

  I have no doubt it's probably not 100% correct as I'm really only just
  cribbing it up from what I can see in other jobs.  Hopefully I have
  not exacerbated the problem with that job.

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




More information about the foundations-bugs mailing list