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

[Dmitrijs Ledkovs]

On a regular trusty laptop with an SSD i did 6 boots (3 reboots and 3 cold boots), and compared the boot.logs.
My expectation is to have no less than 6 instances of each unique boot messages, that is not the case:
      1  * Starting Bridge socket events into upstart
      1  * Starting modem connection manager
      1  * Starting Restore Sound Card State
      1  * Starting System V initialisation compatibility
      2  * Starting bluetooth daemon
      2  * Starting configure network device
      2  * Starting system logging daemon
      3  * Starting save kernel messages
      3  * Stopping save kernel messages
      4  * Starting Bridge file events into upstart
      4  * Starting save udev log and update rules
      4  * Starting SystemD login management service
      4  * Stopping save udev log and update rules
      5  * Starting ACPI daemon
      5  * Starting enable remaining boot-time encrypted block devices
      5  * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated
      5  * Starting Reload cups, upon starting avahi-daemon to make sure remote queues are populated
      5  * Stopping cold plug devices
      5  * Stopping log initial device creation

bootlogs attached.

I'm not sure if this is the same or different problem.

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