My Favorites

Close

Please to see your favorites.

  • Bookmark
  • Email Document
  • Printer Friendly
  • Favorite
  • Rating:

System dropping into emergency target with "systemd-journald[<pid>]: Failed to open runtime journal: No such file or directory"

This document (7024334) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 15 and it's service packs
SUSE Linux Enterprise Server 12 and it's service packs

Situation

System boots up very slowly, printing messages like:

[  124.566003] systemd-journald[627]: Failed to open runtime journal: No such file or directory
[  124.573039] systemd-journald[628]: Failed to open runtime journal: No such file or directory
[  124.579604] systemd-journald[634]: Failed to open runtime journal: No such file or directory
[  124.585817] systemd-journald[636]: Failed to open runtime journal: No such file or directory
[  124.590887] systemd-journald[640]: Failed to open runtime journal: No such file or directory

and on the console one can see that systemd-journald.service is failing multiple times

System seems to hang every now and then and does not finish booting.
It may even greet the user as "New installation" and ask for a locale to be set.
Finally it drops into emergency target asking for the root password.

Resolution

Log in as root user and either create an empty file /etc/machine-id which will be populated upon next reboot, or better run:

systemd-machine-id-setup

Cause

File /etc/machine-id is missing from the system.

/etc/machine-id contains a unique identifier for the system.
Journald uses this identifier to store it's journal in /run/log/journal/<machine-id>/
systemd-journald.service fails if it can't access or create the directory.
Since journald is considered critical, boot will fail and the system ends in emergency target.

If /etc/machine-id is empty, systemd will populate it during boot, problem only exists if /etc/machine-id is missing.

Additional Information

SUSE engineering is aware of the problem and this document will be updated once a fix is available.

Regarding the "New installation" and local settings asked, this is caused by systemd-firstboot service which get's activated if machine-id is not available.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7024334
  • Creation Date:11-DEC-19
  • Modified Date:11-DEC-19
    • SUSESUSE Linux Enterprise Server
< Back to Support Search

SUSE Support Forums

Get your questions answered by experienced Sys Ops or interact with other SUSE community experts.

Join Our Community

Support Resources

Learn how to get the most from the technical support you receive with your SUSE Subscription, Premium Support, Academic Program, or Partner Program.


SUSE Customer Support Quick Reference Guide SUSE Technical Support Handbook Update Advisories
Support FAQ

Open an Incident

Open an incident with SUSE Technical Support, manage your subscriptions, download patches, or manage user access.

Go to Customer Center