[Bug 980917] Re: Failed to create pty - disabling logging for job

[Adam Honse]

I'm having this same bug on the ARM port of Ubuntu.  I have
LEGACY_PTYS=y, LEGACY_PTY_COUNT=256, and UNIX98_PTYS=y on my custom
2.6.35 kernel (this is for the HP TouchPad tablet computer btw) and
after the system is booted there are /dev/ptmx, /dev/pts, and /dev/ptyXX
entries in the system.  I get the same errors on my other ARM device
(Archos 43 tablet with 2.6.37 kernel).  I think the main issue I have
isn't that job logging isn't enabled, it's that the dmesg is spammed
with error messages.  In the event that this error occurs it should not
spew 100's of lines of errors, it should print a single, detailed,
informative message and permanently disable logging for the session so
the error doesn't print again.

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

Title:
  Failed to create pty - disabling logging for job

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  I believe this bug is in Upstart due to similar bug that was recently
  fixed:

  - https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/936667

  I am booting Ubuntu 12.04 LTS (x86) as a domU under Xen.  After the
  previous bug was fixed, I still received the errors but the system now
  boots which is an improvement.  During the boot process I see a few
  combinations of this error:

  ====
  init: Failed to create pty - disabling logging for job
  init: Temporary process spawn error: No such file or directory
  ====

  After those two stop, I see a few more of these errors:

  ====
  init: Failed to create pty - disabling logging for job
  ====

  The above error also prints if I type "poweroff" or "shutdown"

  This system's ultimate destiny is to operate using a custom-compiled
  Linux kernel that does not exist on the filesystem.  Both the Ubuntu-
  supplied Linux kernel and the custom-compiled Linux kernel are
  afflicted by this bug.

  Any suggestions would be greatly appreciated.

  -Tim

  //edit: added more details, edited for clarity.

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