After updating my Rocky Linux 8.6, I found 6 services failed to start.
The system is running okay. My virtual machine is also running okay. Should I be worry about these services? Can I disable them from being started during boot?
Most of these appear to be run once type services that execute only if specific conditions are met.
Unless you have an isci device “iscsi-onboot” has no reason to run and this is true for a number of the others. Since you are using cockpit, after an update, it will usually note or ask you to restart some services, others may need you to reboot the system. I’ve had these “failed to start” warnings in the past but they usually do not persist after a reboot.
I’ve rebooted the system couple times since, the error is very consistent. I’m running a bios raid on the system. mdstat showing the raid is running nominally. I’m going leave the services alone. They don’t seems to be causing any trouble to the system. thanks
@kyiu as was what was explained by @jbkt23 the majority of these services run once, for example after the very first boot after installing your system. Therefore, they are nothing to worry about.
Here are the same services from my Rocky install which has been running for months and has zero problems whatsoever:
[root@rocky ~]# systemctl status loadmodules
● loadmodules.service - Load legacy module configuration
Loaded: loaded (/usr/lib/systemd/system/loadmodules.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-05-30 16:06:36 CEST; 23s ago
├─ ConditionPathExists=|/etc/rc.modules was not met
└─ ConditionDirectoryNotEmpty=|/etc/sysconfig/modules was not met
[root@rocky ~]# systemctl status systemd-binfmt
● systemd-binfmt.service - Set Up Additional Binary Formats
Loaded: loaded (/usr/lib/systemd/system/systemd-binfmt.service; static; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-05-30 16:06:36 CEST; 28s ago
├─ ConditionDirectoryNotEmpty=|/lib/binfmt.d was not met
├─ ConditionDirectoryNotEmpty=|/usr/lib/binfmt.d was not met
├─ ConditionDirectoryNotEmpty=|/usr/local/lib/binfmt.d was not met
├─ ConditionDirectoryNotEmpty=|/etc/binfmt.d was not met
└─ ConditionDirectoryNotEmpty=|/run/binfmt.d was not met
Docs: man:systemd-binfmt.service(8)
man:binfmt.d(5)
https://www.kernel.org/doc/html/latest/admin-guide/binfmt-misc.html
https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
[root@rocky ~]# systemctl status systemd-firstboot
● systemd-firstboot.service - First Boot Wizard
Loaded: loaded (/usr/lib/systemd/system/systemd-firstboot.service; static; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-05-30 16:06:36 CEST; 36s ago
└─ ConditionFirstBoot=yes was not met
Docs: man:systemd-firstboot(1)
[root@rocky ~]# systemctl status systemd-hwdb-update
● systemd-hwdb-update.service - Rebuild Hardware Database
Loaded: loaded (/usr/lib/systemd/system/systemd-hwdb-update.service; static; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-05-30 16:06:36 CEST; 43s ago
├─ ConditionNeedsUpdate=/etc was not met
└─ ConditionDirectoryNotEmpty=|/etc/udev/hwdb.d was not met
Docs: man:hwdb(7)
man:systemd-hwdb(8)
[root@rocky ~]# systemctl status systemd-sysusers
● systemd-sysusers.service - Create System Users
Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Mon 2022-05-30 16:06:36 CEST; 51s ago
└─ ConditionNeedsUpdate=/etc was not met
Docs: man:sysusers.d(5)
man:systemd-sysusers.service(8)
so nothing to worry about.
Technically you can effectively do:
systemctl disable <servicename>
replacing <servicename> with the services that are showing as failed, and then in the future they will never run again and will never show as failed.
Thank you for the update.
1 Like