Bug 2065322
| Summary: | systemd services fail to start | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | GV <rhel> | ||||
| Component: | systemd | Assignee: | David Tardon <dtardon> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Frantisek Sumsal <fsumsal> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 8.5 | CC: | benny_bao, dtardon, frank.ramsay, jamacku, jbilling, kazen, lombcy, mateusz.kusiak, msekleta, rmetrich, sgardner, smahanga, soutteri, systemd-maint-list, yijun_shen | ||||
| Target Milestone: | rc | Keywords: | Bugfix, Triaged, ZStream | ||||
| Target Release: | 8.7 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | systemd-239-60.el8 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | |||||||
| : | 2086553 (view as bug list) | Environment: | |||||
| Last Closed: | 2022-11-08 10:49:54 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1798275, 2016147, 2072062, 1846002, 1965064, 2086553 | ||||||
| Deadline: | 2022-08-23 | ||||||
| Attachments: |
|
||||||
|
Description
GV
2022-03-17 16:46:37 UTC
Please attach the logs for these services. E.g.: # journalctl -b -u loadmodules.service # systemctl reset-failed loadmodules
# 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 Thu 2022-03-17 21:29:44 EET; 14min ago
├─ ConditionPathExists=|/etc/rc.modules was not met
└─ ConditionDirectoryNotEmpty=|/etc/sysconfig/modules was not met
# systemctl reset-failed sys-fs-fuse-connections.mount
# systemctl status sys-fs-fuse-connections.mount
● sys-fs-fuse-connections.mount - FUSE Control File System
Loaded: loaded (/usr/lib/systemd/system/sys-fs-fuse-connections.mount; static; vendor preset: disabled)
Active: inactive (dead)
Condition: start condition failed at Thu 2022-03-17 21:29:44 EET; 14min ago
└─ ConditionPathExists=/sys/fs/fuse/connections was not met
Where: /sys/fs/fuse/connections
What: fusectl
Docs: https://www.kernel.org/doc/Documentation/filesystems/fuse.txt
https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
# systemctl reset-failed systemd-sysusers.service
# systemctl status systemd-sysusers.service
● 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 Thu 2022-03-17 21:29:44 EET; 14min ago
└─ ConditionNeedsUpdate=/etc was not met
Docs: man:sysusers.d(5)
man:systemd-sysusers.service(8)
# systemctl reset-failed systemd-hwdb-update.service
# systemctl status systemd-hwdb-update.service
● 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 Thu 2022-03-17 21:29:44 EET; 14min ago
├─ ConditionNeedsUpdate=/etc was not met
└─ ConditionDirectoryNotEmpty=|/etc/udev/hwdb.d was not met
Docs: man:hwdb(7)
man:systemd-hwdb(8)
.... reboot ....
#journalctl -b -u loadmodules
-- Logs begin at Thu 2022-03-17 21:45:33 EET, end at Thu 2022-03-17 21:48:11 EET. --
-- No entries --
# systemctl status loadmodules
● loadmodules.service - Load legacy module configuration
Loaded: loaded (/usr/lib/systemd/system/loadmodules.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit)
Condition: start condition failed at Thu 2022-03-17 21:45:41 EET; 2min 30s ago
├─ ConditionPathExists=|/etc/rc.modules was not met
└─ ConditionDirectoryNotEmpty=|/etc/sysconfig/modules was not met
#journalctl -b -u sys-fs-fuse-connections.mount
-- Logs begin at Thu 2022-03-17 21:45:33 EET, end at Thu 2022-03-17 21:48:11 EET. --
-- No entries --
# systemctl status sys-fs-fuse-connections.mount
● sys-fs-fuse-connections.mount - FUSE Control File System
Loaded: loaded (/usr/lib/systemd/system/sys-fs-fuse-connections.mount; static; vendor preset: disabled)
Active: failed (Result: start-limit-hit)
Condition: start condition failed at Thu 2022-03-17 21:45:41 EET; 2min 30s ago
└─ ConditionPathExists=/sys/fs/fuse/connections was not met
Where: /sys/fs/fuse/connections
What: fusectl
Docs: https://www.kernel.org/doc/Documentation/filesystems/fuse.txt
https://www.freedesktop.org/wiki/Software/systemd/APIFileSystems
#journalctl -b -u systemd-sysusers.service
-- Logs begin at Thu 2022-03-17 21:45:33 EET, end at Thu 2022-03-17 21:48:11 EET. --
-- No entries --
# systemctl status systemd-sysusers.service
● systemd-sysusers.service - Create System Users
Loaded: loaded (/usr/lib/systemd/system/systemd-sysusers.service; static; vendor preset: disabled)
Active: failed (Result: start-limit-hit)
Condition: start condition failed at Thu 2022-03-17 21:45:41 EET; 2min 30s ago
└─ ConditionNeedsUpdate=/etc was not met
Docs: man:sysusers.d(5)
man:systemd-sysusers.service(8)
#journalctl -b -u systemd-hwdb-update.service
-- Logs begin at Thu 2022-03-17 21:45:33 EET, end at Thu 2022-03-17 21:48:11 EET. --
-- No entries --
# systemctl status systemd-hwdb-update.service
● systemd-hwdb-update.service - Rebuild Hardware Database
Loaded: loaded (/usr/lib/systemd/system/systemd-hwdb-update.service; static; vendor preset: disabled)
Active: failed (Result: start-limit-hit)
Condition: start condition failed at Thu 2022-03-17 21:45:41 EET; 2min 30s ago
├─ ConditionNeedsUpdate=/etc was not met
└─ ConditionDirectoryNotEmpty=|/etc/udev/hwdb.d was not met
Docs: man:hwdb(7)
man:systemd-hwdb(8)
The odd thing: no logs except the first failed boot (I rebooted several times, journal is volatile):
# grep -E "loadmodules|sys-fs-fuse-connections|systemd-sysusers|systemd-hwdb-update" /var/log/messages | grep -v 07:55:12
#
touch /.autorelabel && reboot did not help. Nor did booting with selinux in permissive mode.
Created attachment 1866504 [details]
Very blurry image
*** Bug 2068495 has been marked as a duplicate of this bug. *** Full analysis in BZ #2068495. I cannot reproduce this, but I am pretty sure we need https://github.com/systemd/systemd/pull/21030 . *** Bug 2076860 has been marked as a duplicate of this bug. *** *** Bug 2081739 has been marked as a duplicate of this bug. *** The root cause analysis was somehow done in BZ #2068495 (along with a reproducer). Test rpms are available at https://people.redhat.com/dtardon/systemd/bz2065322-start-limit-hit/ . (In reply to David Tardon from comment #11) > Test rpms are available at > https://people.redhat.com/dtardon/systemd/bz2065322-start-limit-hit/ . The issue seems to be fixed (tried several reboots and everything was fine). Thank you! fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/270 *** Bug 2108529 has been marked as a duplicate of this bug. *** *** Bug 2117158 has been marked as a duplicate of this bug. *** Hello, will this change affect RHEL8.6? (In reply to Mateusz Kusiak from comment #24) > Hello, > will this change affect RHEL8.6? There's a 8.6.z clone of this (bug 2086553) if that's what you mean. 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 (systemd bug fix and enhancement update), 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://access.redhat.com/errata/RHBA-2022:7727 |