Bug 1126298

Summary:	Unable to boot when systemd's LogTarget is set to syslog-or-kmsg or syslog
Product:	Red Hat Enterprise Linux 7	Reporter:	GV <rhel>
Component:	systemd	Assignee:	systemd-maint
Status:	CLOSED ERRATA	QA Contact:	Frantisek Sumsal <fsumsal>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	fsumsal, jscotka, lnykryn, psklenar, systemd-maint-list
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	systemd-219-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 14:57:08 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 GV 2014-08-04 06:31:17 UTC

Description of problem:
Unable too boot is LogTarget in /etc/systemd/system.conf is set to syslog-or-kmsg or syslog.

Version-Release number of selected component (if applicable):
systemd 208-11

How reproducible:
Change LogTarget in /etc/systemd/system.conf to syslog-or-kmsg or syslog and reboot.

Actual results:
System cannot boot.

Expected results:
System boot normally.

Additional info:
I know systemd is really BAD (use-it since it was introduced to Fedora) but since is "community" linux I can more ol less accept-it like it is. But you people made-it even worse in RHEL7!

Comment 2 Lukáš Nykrýn 2014-08-04 11:18:18 UTC

Thanks for the bug report, we always appreciate constructive criticism. We need to backport http://cgit.freedesktop.org/systemd/systemd-stable/commit/?id=b7f2e5ac769ca4d9b7d28050ec662104635a7822

Comment 3 GV 2014-08-04 16:33:00 UTC

> If journald cannot process a message from PID1 for 10 ms then something is
> significantly wrong. It's better to lose the message and continue.
Really? Lose the message? That's the best systemd can do?

Comment 4 Lennart Poettering 2014-08-04 19:54:42 UTC

In PID the effective difference between "syslog" and "journal" is pretty minimal. We should probably stop documenting "syslog" and just implicitly turn all "syslog" log targets into "journal".

Comment 5 Lukáš Nykrýn 2014-09-29 10:26:17 UTC

Ok, dropping log messages even just from systemd itself isn't probaly a best way, but wee need more time for investigation.

Comment 7 Lukáš Nykrýn 2015-04-21 13:51:09 UTC

This should be now fixed with the rebase.

Comment 10 errata-xmlrpc 2015-11-19 14:57:08 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2092.html