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

[fresh-nes]

Hi,

I am working on a Pandaboard ES.
I try to boot my Pandaboard over NFS, using Ubuntu 12.04
My NFS connection is OK, but it stops during the start of modules.
When I boot the same fs, using an SD card, it works fine.
(I use the kernel option --no-log in order to avoid "init: Failed to create pty - disabling logging for job")

====
…
[ 9.431549] Sending DHCP requests .
[ 11.005828] smsc95xx 1-1.1:1.0: eth0: link up, 100Mbps, full-duplex, lpa 0xCDE1
[ 11.871856] ., OK
[ 11.909912] IP-Config: Got DHCP answer from 10.1.2.21, my address is 10.1.9.22
[ 11.918365] IP-Config: Complete:
[ 11.921752] device=eth0, addr=10.1.9.22, mask=255.255.0.0, gw=10.1.2.251,
[ 11.928161] host=10.1.9.22, domain=xxx.xxx, nis-domain=(none),
[ 11.936035] bootserver=10.1.2.21, rootserver=10.1.9.40, rootpath=
[ 11.943511] Waiting 2sec before mounting root device…
[ 13.963836] VFS: Mounted root (nfs filesystem) on device 0:14.
[ 13.970977] devtmpfs: mounted
[ 13.974334] Freeing init memory: 420K
* Starting network connection manager[ OK ]
* Starting mDNS/DNS-SD daemon[ OK ]
* Starting User Mode Init Manager for TI shared transport[ OK ]
* Starting bluetooth daemon[ OK ]
* Starting load fallback graphics devices[ OK ]
* Starting Userspace bootsplash[ OK ]
* Stopping load fallback graphics devices[ OK ]
====

And nothing else.

Could you explain me how to modify my upstart in order to boot my
Pandaboard over NFS, using Ubuntu 12.04

Best regards,
PixMe

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