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

[Tim Heckman]

Hello James,

Thank you for taking the time to look in to this bug as well as get back
to me.  The explanation of the issue definitely makes the problem more
clear.  However, I am intrigued by the fact that something so important
is assumed, and that Upstart errors when it encounters something
different (such as there being no initramfs thus /dev/pts not being
mounted).  However, I'm not intimately familiar with the inner workings,
but I would hope there's a way to fix it without having to implement the
'--no-log' workaround.

The custom-compiled kernel that's being used to boot the system should
have sufficient PTY support enabled:

----
~# zgrep -i "pty" /proc/config.gz
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
----

Thank you for the suggestion for the workaround.  Sadly, I don't think
that's something I can implement due to some restrictions with the
environment that Ubuntu 12.04 LTS will be running in (at least in my
case).  But if this isn't something you guys are able to resolve in
Upstart before release, alternative options may need to be looked at.  I
would also love to be able to have job logging enabled, as I feel it is
an important addition to Upstart.

Thank you again for your time, James.  I look forward to seeing how this
issue irons out.

-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