Public bug reported:
This had been seen occasionally previously, but in raring is more
apparent, and made bug 1078926 more difficult to diagnose.
cloud-init has several upstart jobs which have 'console output'.
Often times output of these jobs does not reach the console. cloud-init-local and cloud-init would normally output data like:
Cloud-init v. 0.7.1 running 'init' at Mon, 03 Dec 2012 15:56:41 +0000. Up 6.81 seconds.
to their stdout.
The console output of a cloud image (collected from the hypervisor log
by an API call, ie 'euca-get-console-output') often times does not have
this data in it. The lost data is usually found in /var/log/boot.log
after inspection.
The attached file has missing output of:
Cloud-init v. 0.7.1 running 'init-local' at Mon, 03 Dec 2012 15:59:31 +0000. Up 5.95 seconds.
Related bugs:
* bug 1078926: raring instance failed to find EC2 datasource
* bug 682831: lost console output early in boot
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu2
ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
Uname: Linux 3.7.0-4-generic x86_64
ApportVersion: 2.6.3-0ubuntu2
Architecture: amd64
Date: Mon Dec 3 17:38:28 2012
DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
Ec2AMI: ami-00000177
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-4-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 --verbose
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-4-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 --verbose
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
** Affects: plymouth (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ec2-images raring
** Attachment added: "example console output with missing data"
https://bugs.launchpad.net/bugs/1086072/+attachment/3450746/+files/console-verbose-log.txt
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/1086072
Title:
some output to /dev/console does not reach /dev/console
Status in “plymouth” package in Ubuntu:
New
Bug description:
This had been seen occasionally previously, but in raring is more
apparent, and made bug 1078926 more difficult to diagnose.
cloud-init has several upstart jobs which have 'console output'.
Often times output of these jobs does not reach the console. cloud-init-local and cloud-init would normally output data like:
Cloud-init v. 0.7.1 running 'init' at Mon, 03 Dec 2012 15:56:41 +0000. Up 6.81 seconds.
to their stdout.
The console output of a cloud image (collected from the hypervisor log
by an API call, ie 'euca-get-console-output') often times does not
have this data in it. The lost data is usually found in
/var/log/boot.log after inspection.
The attached file has missing output of:
Cloud-init v. 0.7.1 running 'init-local' at Mon, 03 Dec 2012 15:59:31 +0000. Up 5.95 seconds.
Related bugs:
* bug 1078926: raring instance failed to find EC2 datasource
* bug 682831: lost console output early in boot
ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: plymouth 0.8.8-0ubuntu2
ProcVersionSignature: Ubuntu 3.7.0-4.12-generic 3.7.0-rc7
Uname: Linux 3.7.0-4-generic x86_64
ApportVersion: 2.6.3-0ubuntu2
Architecture: amd64
Date: Mon Dec 3 17:38:28 2012
DefaultPlymouth: Error: command ['readlink', '/etc/alternatives/default.plymouth'] failed with exit code 1:
Ec2AMI: ami-00000177
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
Lsusb:
Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Bochs Bochs
MarkForUpload: True
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-4-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 --verbose
ProcEnviron:
TERM=screen
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB:
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-4-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 --verbose
SourcePackage: plymouth
TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/01/2007
dmi.bios.vendor: Bochs
dmi.bios.version: Bochs
dmi.chassis.type: 1
dmi.chassis.vendor: Bochs
dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:svnBochs:pnBochs:pvr:cvnBochs:ct1:cvr:
dmi.product.name: Bochs
dmi.sys.vendor: Bochs
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1086072/+subscriptions