Systemd failed condition check message occur in dmesg

Solution Verified - Updated -

Issue

  • When start the OS for the first time, executing "dmesg | egrep -i 'fail|error|warn'", the following is displayed:
[    1.321376] systemd[1]: Create System Users was skipped because of a failed condition check (ConditionNeedsUpdate=/etc).
[    1.376299] systemd[1]: dracut ask for additional cmdline parameters was skipped because all trigger condition checks failed.
[    3.892220] systemd[1]: Dispatch Password Requests to Console Directory Watch was skipped because of a failed condition check (ConditionPathExists=!/run/plymouth/pid).
[    3.894605] systemd[1]: multipathd control socket was skipped because of a failed condition check (ConditionPathExists=/etc/multipath.conf).
[    3.912621] systemd[1]: Kernel Module supporting RPCSEC_GSS was skipped because of a failed condition check (ConditionPathExists=/etc/krb5.keytab).
[    3.936650] systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
  • Compared with RHEL8.6, there is no such error message output. For example, systemd-sysusers.service, RHEL 8.6 and RHEL 9.0 are configured with ConditionNeedsUpdate, but RHEL 8.6 has no error output to dmesg.
  • Would systemd's info should be output to dmesg?

Environment

  • Red Hat Enterprise Linux (RHEL) 9.0
  • systemd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content