I have found a significant difference between the syslogs of an "N 2" boot and 
an "unknown" boot.
See syslog_N2 and syslog_unknown, attached.  I find using  diffuse  to look at 
them side-by-side very useful.
I've changed times and process numbers to nn:nn:nn and nnn to make taking diffs 
easier.

Start at line 702 in syslog_N2 (S2 below) and syslog_unknown (SU below).

In the SU we see
  "... init: rpc_pipefs post-stop process (821)"

In the S2 log, we don't see an  "init:" entry until line 741, and it is
  "... init: rsyslog state changed from post-start to running"

In fact we don't see an "init:" line for rsyslog state change in SU!
And rsyslog is the last state changes we see in /var/log/boot.log.

Is that the race condition?

To find out, I added   ...  and  started rsyslog  ...  to the "start on"
stanza.  The syslog said:

        :
        :
May 26 09:37:42 autoaud-broad1 kernel: [    0.901105] ACPI: Power Button [PWRF]
May 26 09:37:42 autoaud-broad1 init: Failed to spawn rc-sysinit main process: 
unable to open console: Input/output error
May 26 09:37:42 autoaud-broad1 init: rc-sysinit goal changed from start to stop
May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from spawned to 
stopping
May 26 09:37:42 autoaud-broad1 init: Handling stopping event
May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from stopping to 
killed
May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from killed to 
post-stop
May 26 09:37:42 autoaud-broad1 init: rc-sysinit state changed from post-stop to 
waiting
May 26 09:37:42 autoaud-broad1 init: Handling stopped event
May 26 09:37:42 autoaud-broad1 init: Handling net-device-up/failed event
May 26 09:37:42 autoaud-broad1 init: Handling started/failed event
        :
        :

((more experimentation attempting to detect the presence of
/dev/console))

I commented out the  "console output"  stanza  in  /etc/init/rc-
sysinit.conf  and I seem to have a reliable boot.

I suspect the race condition was with whatever makes /dev/console
writable.

Suggestion:  failure of the  console  stanza should cause an error
message, not stop the *.conf file.

-- 
Some services not started on boot, runlevel returns "unknown"
https://bugs.launchpad.net/bugs/543506
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to