sysv initscripts not started on boot
Bug #504957 reported by
Andrew Aylett
This bug report is a duplicate of:
Bug #497299: upstart not starting init-scripts (event net-device-up IFACE=lo missing).
Edit
Remove
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
upstart (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: upstart
On boot, upstart isn't starting the legacy sysv initscripts. The `runlevel` command returns 'unknown'.
I have a workaround:
axa@artemis:~$ runlevel
unknown
axa@artemis:~$ sudo telinit 2
axa@artemis:~$ runlevel
N 2
The debug information collected with ubuntu-bug is from before switching runlevels.
ProblemType: Bug
Architecture: i386
Date: Fri Jan 8 21:21:57 2010
DistroRelease: Ubuntu 9.10
ExecutablePath: /sbin/init
Package: upstart 0.6.3-11
ProcEnviron: PATH=(custom, no user)
ProcVersionSign
SourcePackage: upstart
Uname: Linux 2.6.31-16-generic i686
To post a comment you must log in.
i have the same problem here with upstart 0.6.3-11.
The runlevel command returns "unknown'. No runlevel daemon are running with this version, CTRL-ALT-F[1-6] also do not show any login prompt, just nothing but black screen (I have x windows server auto-login user configured). Gnome becomes less usable without some crucial daemons running like cups.
Although running 'sudo init 2' in xterm load all runlevel 2 daemons. This does not sound proper.
Downgrading to upstart 0.6.3-10 seems to solve the problem, that points out that 0.6.3.11 is sort of buggy. Unknown runlevel does not make sense at all in unix-based os.
In my opinion, the urgency level of this bug should be raised due to the reason that if user can't their operating started properly, all eye candy features will be meaningless.