[Bug 980917] Re: Failed to create pty - disabling logging for job
Colin Watson
cjwatson at canonical.com
Wed Jul 4 15:36:01 UTC 2012
So, running without an initramfs isn't currently a supported
configuration due mainly to bugs such as this, although we would like to
make it so in future for various reasons. As such I can't currently
justify a priority higher than Medium. However, if the fix turns out
not to be too intrusive (on which I'll have to defer to James) then it
would be a reasonable target for 12.04.1 as the impact is clearly
serious for those who encounter it.
** Changed in: upstart (Ubuntu)
Importance: Undecided => Medium
** Also affects: upstart (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: upstart (Ubuntu Precise)
Status: New => Triaged
** Changed in: upstart (Ubuntu Precise)
Importance: Undecided => Medium
** Changed in: upstart (Ubuntu Precise)
Assignee: (unassigned) => James Hunt (jamesodhunt)
** Changed in: upstart (Ubuntu Precise)
Milestone: None => ubuntu-12.04.1
** Changed in: upstart (Ubuntu)
Status: Confirmed => Triaged
--
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:
Triaged
Status in “upstart” source package in Precise:
Triaged
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
More information about the foundations-bugs
mailing list