[Bug 1235231] Re: plymouth loses output to /dev/console (such as ci-info: messages)

[Bug Watch Updater]

Launchpad has imported 1 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=71996.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2013-11-25T15:00:16+00:00 Scott Moser wrote:

During early boot, plymouth captures writes to /dev/console. As I
understand it, it is supposed to re-play that content later. Whether or
not it intends to is not the issue. In Ubuntu cloud-images (and in other
cases) users may write data to /dev/console that needs to be seen on the
other side (ie a serial logger or 'get-console-ouptput' EC2 api call).

This bug is easily reproducible on a local kvm, a cloud such as EC2 or a
local lxc container.  In my opinion, it should be considered "data
loss".  The issue is that a user cannot reliably write data to
/dev/console.

See the attached 'my-logger.conf' for an upstart job that simply writes
data early in boot to /dev/console. Sometimes data "lost" is available
in /var/log/boot.log, but sometimes it doesn't even seem to make it
there. bug 682831 (http://pad.lv/682831) has an attachment 'myhack-init'
that does a similar thing but starts outputting by replacing /sbin/init
and then calling /sbin/init itself.

I'd really appreciate it if someone was able to take a look at this.
I'm willing to help reproduce it and can even give access to some cloud-
instances that can reproduce if necessary.

Reply at: https://bugs.launchpad.net/ubuntu/+source/cloud-
init/+bug/1235231/comments/24


** Changed in: plymouth
       Status: Unknown => Confirmed

** Changed in: plymouth
   Importance: Unknown => Medium

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

Title:
  plymouth loses output to /dev/console (such as ci-info: messages)

Status in The Plymouth splash screen:
  Confirmed
Status in “cloud-init” package in Ubuntu:
  Confirmed
Status in “plymouth” package in Ubuntu:
  Confirmed

Bug description:
  During early boot, plymouth captures writes to /dev/console.  As I
  understand it, it is supposed to re-play that content later.  Whether
  or not it intends to is not the issue.  In our cloud-images (and in
  other cases) users may write data to /dev/console that needs to be
  seen on the other side (ie a serial logger or 'get-console-ouptput'
  api call).

  See the attached 'my-logger.conf' for an upstart job that simply
  writes data early in boot to /dev/console.  Sometimes data "lost" is
  available in /var/log/boot.log, but sometimes it doesn't even seem to
  make it there.  bug 682831 has an attachment 'myhack-init' that does a
  similar thing but starts outputting by replacing /sbin/init and then
  calling /sbin/init itself.

  Related bugs:
   * bug 682831:  lost console output early in boot

  == Original bug report ==
  On precise cloud images, I get a console output line like this:

  ci-info: eth0  : 1 192.168.122.204 255.255.255.0   52:54:00:7f:d8:ca^M

  On saucy cloud images, this is missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1235231/+subscriptions