RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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!

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

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

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

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

This should be now fixed with the rebase.

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