Comment 284 for bug 554172

On Tue, Sep 21, 2010 at 04:09:39PM -0000, Marcus Bointon wrote:
> I'm running the updated upstart and plymouth-free grub2 config on two
> newly installed amd64 boxes (bog-standard Dell 2950s) with today's
> 2.6.32-24-server kernel, and I'm still finding a whole bunch of services
> fail to start (cron, apache2, mysql, fail2ban, sysstat, postfix, openntpd,
> mysql-mmm), along with the unknown runlevel issue. All of them (except
> sysstat for some reason) start fine if I run telinit 2. One of them
> reported the localhost interface breakage, but the other did not.

If the runlevel is not set at boot, the issue you're seeing is unrelated to
this bug. The rc-sysinit job is failing to trigger, either because you have
filesystems configured in /etc/fstab that are not being found and mounted at
boot time, or because you don't have a properly configured loopback
interface in /etc/network/interfaces.

> It doesn't seem likely that all of these major, common packages have bugs
> with identical symptoms - it's got to be a problem with upstart - so
> reporting bugs on the packages is probably a waste of time.

Yes, in that case the appropriate thing to do would be to file a *single*
bug against upstart describing the problem. In any case, following up to
this bug, which has been fixed, is not the correct approach.

> This is a really major problem as it can (and does for us) render servers
> non-functional and insecure by default - why is it marked as 'wontfix' and
> downgraded from critical with no obvious pointer to a better bug?

What is marked as 'wontfix' for the lucid and maverick releases is the
kernel issue that led to this problem. The user-facing issue has been
addressed.

--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/
<email address hidden> <email address hidden>