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

[Tim Heckman]

James: It seems that this is a chicken and egg problem when someone
doesn't have an initramfs.  I'm quite alright with logging being
disabled if "/dev/pts" isn't mounted.  The problem I have is the large
amount of unhelpful errors that are printed on the console.  If this
could be a concise error, that would be great:

"init: Failed to create pty - temporarily disabling job logging"

And that should be the only error, in my opinion.  On the opposing side,
I can see where having the specific job that wasn't logged noted.
However, that doesn't happen now.  And if it flooded the console, I
don't think I'd be for it.

Again, without knowing how Upstart processes jobs (maybe I should fix
that), I would probably be okay with something like:

"init: Failed to create pty - disabling job logging for the following:
Job1, Job2, Job3, etc."

Simply add a job to the end of the comma-separated list if it isn't
logged.

-Tim

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