Systemd[1]: Condition check resulted in <?> being skipped

🛈 SYSTEM INFORMATION

Operating system Ubuntu Linux 20.04.3
Webmin version 1.984
Usermin version 1.834
Virtualmin version 6.17-3
Authentic theme version 19.84.7

Since going over to Ubuntu 20.04 I have seen these in my syslog. Quite a lot of stuff being skipped. What do you think I should do about all these?

||systemd[1]: Condition check resulted in ShPlymouth Boot Screen being skipped.|
||systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped.|
||kernel: [    4.693593] systemd[1]: Condition check resulted in System Slice being skipped.|
||kernel: [    4.980208] systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.|
||kernel: [    4.990001] systemd[1]: Condition check resulted in OpenVSwitch configuration for cleanup being skipped.|
||kernel: [    4.997748] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.|
||kernel: [    5.319608] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.|
||kernel: [    5.319688] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.|
||systemd[1]: Condition check resulted in LXD - agent - 9p mount being skipped.|
||systemd[1]: Condition check resulted in LXD - agent being skipped.|
||systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.|
||systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.|
||systemd[1]: Condition check resulted in Authentication service for virtual machines hosted on VMware being skipped.|
||systemd[1]: Condition check resulted in Service for virtual machines hosted on VMware being skipped.|
||systemd[1]: Condition check resulted in Process error reports when automatic reporting is enabled (file watch) being skipped.|
||systemd[1]: Condition check resulted in Timer to automatically fetch and run repair assertions being skipped.|
||systemd[1]: Condition check resulted in Unix socket for apport crash forwarding being skipped.|
||systemd[1]: Condition check resulted in Login to default iSCSI targets being skipped.|
||systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped.|
||systemd[1]: Condition check resulted in Set the CPU Frequency Scaling governor being skipped.|
||systemd[1]: Condition check resulted in Pollinate to seed the pseudo random number generator being skipped.|
||systemd[1]: Condition check resulted in RPC Remote Quota Server being skipped.|
||systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.|
||systemd[1]: Condition check resulted in Secure Boot updates for DB and DBX being skipped.|
||systemd[1]: Condition check resulted in Automatically repair incorrect owner/permissions on core devices being skipped.|
||systemd[1]: Condition check resulted in Wait for the Ubuntu Core chooser trigger being skipped.|
||systemd[1]: Condition check resulted in Thermal Daemon Service being skipped.|
||systemd[1]: Condition check resulted in Ubuntu Advantage reboot cmds being skipped.|
||systemd[1]: Condition check resulted in Auto import assertions from block devices being skipped.|

I dunno, but has nothing to do with Virtualmin, so I’ve moved it to General category.

You can look in the systemd unit files to see what conditions there are for starting them and that will allow you to understand why they aren’t, but if you aren’t using these services, you probably shouldn’t care.

1 Like

I asked this question on askubuntu: boot - Systemd[1]: Condition check resulted in <?> being skipped - Ask Ubuntu

1 Like

They’ll likely know better than us.

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.