[Bug 936667] Re: Upstart early job logging causes boot failure for systems with no initramfs (error is "No available ptys")

[Christian Kujau]

Booting Linux 3.3.0-rc5 (vanilla, no initramfs) with
upstart-1.4-0ubuntu9 (from James' upstart-job-logging PPA) went fine,
even w/o the "--no-log" kernel option. However, at the end of the
booting process, syslog says:

 kernel: [   17.913723] init: No available ptys
 kernel: [   17.913826] init: Failed to create pty - disabling logging
 kernel: [   17.915596] init: Temporary process spawn error: No such file or directory
 kernel: [   17.929426] init: No available ptys
 kernel: [   17.929531] init: Failed to create pty - disabling logging
 kernel: [   17.931403] init: Temporary process spawn error: No such file or directory
 kernel: [   17.939599] init: No available ptys
 kernel: [   17.939687] init: Failed to create pty - disabling logging
 kernel: [   17.947603] init: Temporary process spawn error: No such file or directory
 kernel: [   17.976511] init: plymouth-stop pre-start process (605) terminated with status 1

The "Failed to create pty - disabling logging" message is also printed
on the local console and repeated every now and then. Maybe this
(debugging?) information can be omitted in the final version?

$ ls -l /dev/ptmx 
crw-rw-rw- 1 root tty 5, 2 Mar  7 01:34 /dev/ptmx

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

Title:
  Upstart early job logging causes boot failure for systems with no
  initramfs (error is "No available ptys")

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  When booting 12.04 after a recent update, I see "init(4): no available
  ptys" being displayed faster than a machine gun. When I add --no-log
  as a kernel option and I'm able to boot just fine.

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