Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
When using sudo -iu <user> as root to drop privileges the logs are filled with the following:
Oct 22 11:14:48 [...] systemd[1]: Started Session c403 of user XXX.
Oct 22 11:14:48 [...] sudo[34535]: pam_unix(sudo-i:session): session opened for user XXX by (uid=0)
Oct 22 11:14:48 [...] systemd[1]: Starting User Manager for UID XXXUID...
Oct 22 11:14:48 [...] systemd[34548]: pam_unix(systemd-user:session): session opened for user XXX by (uid=0)
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Started Mark boot as successful after the user session has run 2 minutes.
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Reached target Timers.
Oct 22 11:14:48 [...] systemd[34548]: Failed to connect to API bus: Connection refused
Oct 22 11:14:48 [...] systemd[34548]: Starting D-Bus User Message Bus Socket.
Oct 22 11:14:48 [...] systemd[34548]: Reached target Paths.
Oct 22 11:14:48 [...] systemd[34548]: Listening on D-Bus User Message Bus Socket.
Oct 22 11:14:48 [...] systemd[34548]: Reached target Sockets.
Oct 22 11:14:48 [...] systemd[34548]: Reached target Basic System.
Oct 22 11:14:48 [...] systemd[1]: Started User Manager for UID XXXUID.
It looks like dbus is initalized too late and that several request to dbus are being made.
Version-Release number of selected component (if applicable):
systemd-239-13.el8_0.5.x86_64
How reproducible:
Always
Steps to Reproduce:
Check desription
Actual results:
Contains error messages
Expected results:
Should not contain error messages
Additional info:
I have this same problem with systemd-239-31.el8_2.2.x86_64 - RHEL 8.2
Sep 12 00:00:52 systemd[1]: Started update of the root trust anchor for DNSSEC validation in unbound.
Sep 12 00:07:01 systemd[1]: Starting Generate a daily summary of process accounting...
Sep 12 00:07:01 systemd[1]: Started Generate a daily summary of process accounting.
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Failed to connect to API bus: Connection refused
Sep 12 00:16:01 systemd[947836]: Started D-Bus User Message Bus.
Sep 12 00:17:01 systemd[947836]: Stopping D-Bus User Message Bus...
Sep 12 00:17:01 systemd[947836]: Stopped D-Bus User Message Bus.
Sep 12 00:31:01 systemd[951579]: Failed to connect to API bus: Connection refused
Sep 12 00:31:01 systemd[951579]: Failed to connect to API bus: Connection refused
Sep 12 00:31:01 systemd[951579]: Failed to connect to API bus: Connection refused
Sep 12 00:31:01 systemd[951579]: Failed to connect to API bus: Connection refused
Sep 12 00:31:01 systemd[951579]: Failed to connect to API bus: Connection refused
......
......
(In reply to fcosio from comment #12)
> I have this same problem with systemd-239-31.el8_2.2.x86_64 - RHEL 8.2
That's not surprising. It's not been fixed yet. The fix is scheduled for 8.4.
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 (Moderate: systemd security, 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/RHSA-2021:1611