Bug 1282138

Summary:	boot messages missing and do not appear in boot.log
Product:	[Fedora] Fedora	Reporter:	Ronald Wahl <rwahl>
Component:	rsyslog	Assignee:	Tomas Heinrich <theinric>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	jlieskov, lkundrak, mah.darade, pvrabec, theinric
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-06 21:48:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ronald Wahl 2015-11-15 03:07:28 UTC

Description of problem:
The boot messages are missing after "Starting Switch Root" message (graphical boot disabled). They are also missing from the /var/log/boot.log file but there are different behaviours seen:

(1) It contains the same messages printed on the boot screen, i.e. the last is 
"Starting Switch Root" followed by <ESC>%G (seen with a hexdump utility like hexdump or xxd)
(2) It contains only <ESC>%G
(3) It is empty

When removing the "quiet" switch from the kernel command line the log seems to be complete (but also contains the kernel messages). All in all it looks like a race condition. Maybe a bug in the parser in rsyslog with escape sequences.

Upstream has already 0.8.14 and the ChangeLog lists some parsing bugs - not sure if this bug is fixed as well in that release.

Version-Release number of selected component (if applicable):
rsyslog-8.10.0-1.fc23.x86_64


How reproducible:
100%

Steps to Reproduce:
1. Boot F23 without rhgb on the kernel command line
2. Watch boot messages
3. Check /var/log/boot.log

Actual results:
Boot messages missing after "Starting Switch Root".
/var/log/boot.log incomplete as well.

Expected results:
All boot messages shown on console and in /var/log/boot.log

Additional info:
Currently I run a rather minimal installation (no graphical desktop) in a QEMU/KVM from SSD. That means boot is very fast. Maybe the timing is different when running not in a VM and on slower storage. Just in case you cannot reproduce the behaviour.

Comment 1 Ronald Wahl 2015-11-15 03:26:13 UTC

One thing is just coming to my mind: The messages on the boot screen are not printed by rsyslogd, are they? I.e. only the boot.log is written by rsyslogd. So actually the culprit may not be in rsyslogd itself. Any idea where the message get lost?

Comment 2 Ronald Wahl 2015-12-06 21:48:26 UTC


*** This bug has been marked as a duplicate of bug 1280452 ***