Activity log for bug #980917

Date Who What changed Old value New value Message
2012-04-13 15:24:03 Tim Heckman bug added bug
2012-04-13 15:24:39 Tim Heckman 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. However, during the boot process I see a lot of these errors: ==== init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory ==== These combination of errors print, and then this line is spat out multiple times: ==== init: Failed to create pty - disabling logging for job ==== I'm currently using a custom compiled kernel that exists outside of the filesystem. The issue also is present on the distribution-supplied Linux kernel. Any suggestions would be greatly appreciated. -Tim 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. However, during the boot process I see a lot of these errors: ==== init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory ==== These combination of errors print, and then this line is spat out multiple times: ==== init: Failed to create pty - disabling logging for job ==== I'm currently using a custom compiled kernel that exists outside of the filesystem. The issue also is present on the Ubuntu-supplied Linux kernel. Any suggestions would be greatly appreciated. -Tim
2012-04-13 15:24:53 Tim Heckman 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. However, during the boot process I see a lot of these errors: ==== init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory ==== These combination of errors print, and then this line is spat out multiple times: ==== init: Failed to create pty - disabling logging for job ==== I'm currently using a custom compiled kernel that exists outside of the filesystem. The issue also is present on the Ubuntu-supplied Linux kernel. Any suggestions would be greatly appreciated. -Tim 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. However, during the boot process I see a lot of these errors: ==== init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory ==== These combination of errors print, and then this line is spat out multiple times: ==== init: Failed to create pty - disabling logging for job ==== I'm currently using a custom compiled kernel that exists outside of the filesystem. The issue also is present on the Ubuntu-supplied Linux kernel booted under PV-GRUB. Any suggestions would be greatly appreciated. -Tim
2012-04-13 17:48:17 Tim Heckman 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. However, during the boot process I see a lot of these errors: ==== init: Failed to create pty - disabling logging for job init: Temporary process spawn error: No such file or directory ==== These combination of errors print, and then this line is spat out multiple times: ==== init: Failed to create pty - disabling logging for job ==== I'm currently using a custom compiled kernel that exists outside of the filesystem. The issue also is present on the Ubuntu-supplied Linux kernel booted under PV-GRUB. Any suggestions would be greatly appreciated. -Tim 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.
2012-04-18 18:52:15 Tim Heckman tags precise ubuntu
2012-04-19 04:16:37 Launchpad Janitor upstart (Ubuntu): status New Confirmed
2012-04-20 03:08:46 Ricardo Salveti bug added subscriber Ricardo Salveti
2012-04-25 10:01:56 James Hunt upstart (Ubuntu): assignee James Hunt (jamesodhunt)
2012-04-25 14:29:10 staticsafe bug added subscriber Sadiq Saif
2012-04-26 22:17:02 Oliver Smith bug added subscriber chemicaloliver
2012-04-26 23:40:46 karit bug added subscriber karit
2012-04-27 00:25:02 Wanderson Santiago dos Reis bug added subscriber Wanderson Santiago dos Reis
2012-04-27 02:36:02 Jacob Peddicord bug added subscriber Jacob Peddicord
2012-04-27 15:45:09 Simon Déziel bug added subscriber Simon Déziel
2012-04-27 18:25:37 Matt Nordhoff bug added subscriber Matt Nordhoff
2012-04-27 18:38:10 James Taylor bug added subscriber James Taylor
2012-04-28 04:08:08 Andrew Dunn bug added subscriber Andrew Dunn
2012-04-28 04:16:28 AllenS bug added subscriber AllenS
2012-04-30 19:42:38 Wolfram Pfeiffer bug added subscriber Wolfram Pfeiffer
2012-04-30 20:36:57 trunet bug added subscriber trunet
2012-05-02 17:17:19 Ben Coleman bug added subscriber Ben Coleman
2012-05-05 12:11:42 Denis Klementjev bug added subscriber denis klementjev
2012-05-07 06:18:45 Will Dowling bug added subscriber Will Dowling
2012-05-08 19:15:34 Diego Abadan bug added subscriber Diego Abadan
2012-05-08 20:10:08 Anders G. Jørgensen bug added subscriber Anders G. Jørgensen
2012-05-10 22:43:56 Benjamin Pollack bug added subscriber Benjamin Pollack
2012-05-14 22:38:34 Christopher M. Balz bug added subscriber Christopher M. Balz
2012-05-21 20:50:39 j bug added subscriber j
2012-05-24 14:41:01 Matteo Settenvini bug added subscriber Matteo Settenvini
2012-07-04 15:36:06 Colin Watson upstart (Ubuntu): importance Undecided Medium
2012-07-04 15:36:48 Colin Watson nominated for series Ubuntu Precise
2012-07-04 15:36:48 Colin Watson bug task added upstart (Ubuntu Precise)
2012-07-04 15:36:56 Colin Watson upstart (Ubuntu Precise): status New Triaged
2012-07-04 15:37:02 Colin Watson upstart (Ubuntu Precise): importance Undecided Medium
2012-07-04 15:37:55 Colin Watson upstart (Ubuntu Precise): assignee James Hunt (jamesodhunt)
2012-07-04 15:37:57 Colin Watson upstart (Ubuntu Precise): milestone ubuntu-12.04.1
2012-07-04 15:38:00 Colin Watson upstart (Ubuntu): status Confirmed Triaged
2012-07-11 03:30:18 Tv bug added subscriber Tv
2012-07-16 20:54:41 Alexey Subbotin bug added subscriber Alexey Subbotin
2012-07-26 16:24:24 Steve Langasek upstart (Ubuntu Precise): milestone ubuntu-12.04.1 ubuntu-12.04.2
2012-08-08 10:40:41 Launchpad Janitor upstart (Ubuntu): status Triaged Fix Released
2012-08-08 13:39:47 James Hunt 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. [PROBLEM] This bug causes Upstart to display 1 error message / job that is started that should have its output logged (by default ''all'' jobs are thus affected) if it is unable to create a pseudoterminal device, which is required for Upstart job logging. [IMPACT] This bug affects all users that: - boot their systems without an initramfs - have non-standard /dev setups (for example a static /dev). Backporting this fix to precise makes sense since: - precise is an LTS. - this bug is variously annoying/intimidating to users. - this bug stops Upstart from logging job output at boot time. - the comments on this bug show that users are already running in the environments outlined above. [FIX DETAILS] Upstart will now mount /dev as a devtmpfs filesystem if it fails to find expected device entries (/dev/ptmx and /dev/pts/) on the disk at boot time. If any of the following devices do not exist (after any /dev mount attempt): - /dev/ptmx (for pty support, required for Upstart job logging). - /dev/null - /dev/tty - /dev/console - /dev/kmsg (for early message logging) [TEST CASE] To reproduce this issue: 1) hold down control key at power-on to enter grub menu. 2) press 'e' to edit the top (default) kernel command-line. 3) modify the line beginning with "linux" such that: 3.1) "quiet" is removed. 3.2) "splash" is removed. 3.3) "root=" is set to the *device name*, rather than a UUID (generally, this will be something like "root=/dev/sda1"). 3.4) add "rootfstype=<filesystem_type>" (this will be either "rootfstype=ext4" or "rootfstype=ext3"). 3.5) You'll now have a linux line something like this: "linux /boot/vmlinuz-3.2.0-27-generic root=/dev/sda1 rootfstype=ext4 ro" 4) *delete* the line beginning "initrd" entirely. 5) Press Control+x or F10 to boot. 6) Watch the boot messages and you will see various error messages including the following repeated multiple times: - "init: Failed to create pty - disabling logging for job". [REGRESSION POTENTIAL] None identified. This fix is in upstream Upstart and quantal as of upstart version 1.5-0ubuntu8 (added to archive on 8 August 2012). [PRE-SRU 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.
2012-08-08 13:40:00 James Hunt upstart (Ubuntu Precise): status Triaged In Progress
2012-08-08 13:40:07 James Hunt summary Failed to create pty - disabling logging for job Failed to create pty - disabling logging for job [SRU]
2012-10-25 09:29:04 DynamicBits bug added subscriber DynamicBits
2012-11-21 14:51:26 Launchpad Janitor branch linked lp:~jamesodhunt/ubuntu/precise/upstart/sru-bug-980917
2012-11-21 14:56:20 James Hunt attachment added source package diff for Upstart 1.5-0ubuntu7 in Precise https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+attachment/3440350/+files/ubuntu-precise-upstart-1.5-0ubuntu7.diff
2012-11-21 14:56:55 James Hunt attachment added source package diff for Upstart 1.5-0ubuntu7.1 in Precise https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/980917/+attachment/3440351/+files/ubuntu-precise-upstart-1.5-0ubuntu7.1.diff
2012-11-21 15:01:15 James Hunt bug added subscriber Ubuntu Stable Release Updates Team
2012-11-21 15:01:32 James Hunt upstart (Ubuntu Precise): status In Progress Fix Committed
2012-11-21 15:01:57 James Hunt bug added subscriber James Hunt
2012-12-19 01:27:19 Chris Halse Rogers bug added subscriber SRU Verification
2012-12-19 01:27:22 Chris Halse Rogers tags precise ubuntu precise ubuntu verification-needed
2012-12-28 03:50:16 Hongwu Li tags precise ubuntu verification-needed precise ubuntu verification-done
2013-01-18 16:05:06 Colin Watson tags precise ubuntu verification-done precise ubuntu
2013-01-18 16:05:08 Colin Watson tags precise ubuntu precise ubuntu verification-needed
2013-01-22 14:45:54 Alessio Igor Bogani tags precise ubuntu verification-needed precise ubuntu verification-done
2013-01-24 19:33:52 Adam Conrad removed subscriber Ubuntu Stable Release Updates Team
2013-01-24 19:34:12 Launchpad Janitor upstart (Ubuntu Precise): status Fix Committed Fix Released