[Bug 912558] Re: log.c Assert failed - err=>number == EIO

[James Hunt]

I think we now understand what is happening here. Essentially, the
problem occurs when jobs refer to binaries that don't exist on the
system. The common case of this scenario is if you've installed a
package with a job file in /etc/init/, but then removed the package. The
binaries have now been removed, but the configuration files remain
(unless you 'purge' the package).

The specific scenario causing the failure is if Upstart attempts to run
a single-line *non-existent* command with no shell meta-characters in
it, the assertion fires.

-- 
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/912558

Title:
  log.c Assert failed - err=>number == EIO

Status in “upstart” package in Ubuntu:
  Confirmed
Status in “upstart” source package in Precise:
  Confirmed

Bug description:
  Whilst booting, init has an issue and causes a core dump -> kernel
  panic.

  Appending --no-log to the kernel cmd line allows a successful boot.

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