RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2065322 - systemd services fail to start
Summary: systemd services fail to start
Keywords:
Status: CLOSED ERRATA
Alias: None
Deadline: 2022-08-23
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: systemd
Version: 8.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 8.7
Assignee: David Tardon
QA Contact: Frantisek Sumsal
URL:
Whiteboard:
: 2068495 2076860 2081739 2108529 2117158 (view as bug list)
Depends On:
Blocks: 1798275 2016147 2072062 1846002 1965064 2086553
TreeView+ depends on / blocked
 
Reported: 2022-03-17 16:46 UTC by GV
Modified: 2022-11-08 12:38 UTC (History)
15 users (show)

Fixed In Version: systemd-239-60.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2086553 (view as bug list)
Environment:
Last Closed: 2022-11-08 10:49:54 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Very blurry image (4.37 MB, image/png)
2022-03-17 19:59 UTC, GV 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github redhat-plumbers systemd-rhel8 pull 270 0 None open Propagate condition failed state from service to path unit 2022-05-10 12:21:51 UTC
Github systemd systemd pull 17031 0 None Merged core: propagate start limit hit from triggered unit to path unit 2022-05-10 12:20:22 UTC
Github systemd systemd pull 21030 0 None Merged core: Propagate condition failed state from service to path unit. 2022-04-12 14:45:18 UTC
Red Hat Bugzilla 2017589 1 unspecified CLOSED After upgrade on one machine systemd-ask-password-console.path fail with error "start request repeated too quickly" 2022-08-14 17:13:56 UTC
Red Hat Issue Tracker RHELPLAN-115977 0 None None None 2022-03-17 16:49:59 UTC
Red Hat Knowledge Base (Solution) 6952061 0 None None None 2022-05-04 13:14:40 UTC
Red Hat Product Errata RHBA-2022:7727 0 None None None 2022-11-08 10:50:26 UTC

Internal Links: 2117158

Description GV 2022-03-17 16:46:37 UTC 
Description of problem:
After systemd was updated to version systemd-239-51.el8_5.5.x86_64, at every reboot the following services fail to start:

# grep -E "loadmodules|sys-fs-fuse-connections|systemd-sysusers|systemd-hwdb-update" /var/log/messages
Mar 17 07:55:12 xxx systemd[1]: loadmodules.service: Start request repeated too quickly.
Mar 17 07:55:12 xxx systemd[1]: loadmodules.service: Failed with result 'start-limit-hit'.
Mar 17 07:55:12 xxx systemd[1]: sys-fs-fuse-connections.mount: Start request repeated too quickly.
Mar 17 07:55:12 xxx systemd[1]: sys-fs-fuse-connections.mount: Failed with result 'start-limit-hit'.
Mar 17 07:55:12 xxx systemd[1]: systemd-sysusers.service: Start request repeated too quickly.
Mar 17 07:55:12 xxx systemd[1]: systemd-sysusers.service: Failed with result 'start-limit-hit'.
Mar 17 07:55:12 xxx systemd[1]: systemd-hwdb-update.service: Start request repeated too quickly.

Everything else work. Reverting to systemd-239-51.el8_5.3.x86_64 and all the above services start just fine.

Version-Release number of selected component (if applicable):
systemd-239-51.el8_5.5.x86_64
Comment 1 David Tardon 2022-03-17 18:17:40 UTC 
Please attach the logs for these services. E.g.:

# journalctl -b -u loadmodules.service
Comment 2 GV 2022-03-17 19:57:42 UTC 
# 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.
Comment 3 GV 2022-03-17 19:59:56 UTC 
Created attachment 1866504 [details]
Very blurry image
Comment 4 David Tardon 2022-03-25 15:23:07 UTC 
*** Bug 2068495 has been marked as a duplicate of this bug. ***
Comment 5 Renaud Métrich 2022-03-25 15:33:27 UTC 
Full analysis in BZ #2068495.
Comment 6 David Tardon 2022-04-12 14:45:19 UTC 
I cannot reproduce this, but I am pretty sure we need https://github.com/systemd/systemd/pull/21030 .
Comment 7 David Tardon 2022-04-28 11:13:11 UTC 
*** Bug 2076860 has been marked as a duplicate of this bug. ***
Comment 8 David Tardon 2022-05-05 08:35:15 UTC 
*** Bug 2081739 has been marked as a duplicate of this bug. ***
Comment 10 Renaud Métrich 2022-05-05 13:52:05 UTC 
The root cause analysis was somehow done in BZ #2068495 (along with a reproducer).
Comment 11 David Tardon 2022-05-10 17:09:10 UTC 
Test rpms are available at https://people.redhat.com/dtardon/systemd/bz2065322-start-limit-hit/ .
Comment 12 GV 2022-05-11 07:14:11 UTC 
(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!
Comment 16 Plumber Bot 2022-06-09 09:22:15 UTC 
fix merged to github master branch -> https://github.com/redhat-plumbers/systemd-rhel8/pull/270
Comment 22 David Tardon 2022-08-08 09:25:11 UTC 
*** Bug 2108529 has been marked as a duplicate of this bug. ***
Comment 23 David Tardon 2022-08-10 14:29:24 UTC 
*** Bug 2117158 has been marked as a duplicate of this bug. ***
Comment 24 Mateusz Kusiak 2022-08-11 09:11:04 UTC 
Hello,
will this change affect RHEL8.6?
Comment 25 David Tardon 2022-08-15 08:47:51 UTC 
(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.
Comment 28 errata-xmlrpc 2022-11-08 10:49:54 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.