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 1915319 - SSSD: SBUS: failures during servers startup
Summary: SSSD: SBUS: failures during servers startup
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: sssd
Version: 8.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Alexey Tikhonov
QA Contact: Madhuri
URL:
Whiteboard: review, sync-to-jira
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-01-12 12:38 UTC by Alexey Tikhonov
Modified: 2021-12-20 08:10 UTC (History)
7 users (show)

Fixed In Version: sssd-2.4.0-6.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-05-18 15:04:21 UTC
Type: Bug
Target Upstream Version:
Embargoed:
pm-rhel: mirror+

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 5425 0 None closed SBUS: failures during servers startup 2021-01-18 11:30:00 UTC

Description Alexey Tikhonov 2021-01-12 12:38:15 UTC 
SBUS code triggers following failures during modules startup:

```
[sssd] [sbus_method_handler] (0x2000): Received D-Bus method org.freedesktop.DBus.Hello on /org/freedesktop/DBus
[sssd] [sbus_server_bus_hello] (0x4000): Assigning unique name :1.2 to connection 0xd29790
[sssd] [sbus_issue_request_done] (0x0400): org.freedesktop.DBus.Hello: Success
[sssd] [sbus_dispatch] (0x4000): Dispatching.
[sssd] [sbus_signal_handler] (0x2000): Received D-Bus signal org.freedesktop.DBus.NameOwnerChanged on /org/freedesktop/DBus
[sssd] [sbus_name_owner_changed] (0x4000): Name of owner :1.2 has changed from [] to [:1.2]
[sssd] [sbus_senders_delete] (0x2000): Removing identity of sender [:1.2]
[sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.2' from table     <-- this
```
  --  this is seen in the log of almost every module.

This error message is harmless, but since bz 1893159 changes default log level to 2, this would be seen by default in every setup and can make users worried.

Upstream PR https://github.com/SSSD/sssd/pull/5454 fixes this issues.
Comment 3 Pavel Březina 2021-01-15 11:52:15 UTC 
Pushed PR: https://github.com/SSSD/sssd/pull/5454

* `master`
    * bdf461c7577c458d7b2a785b2007c0ccae73e3f7 - SBUS: do not try to del non existing sender
Comment 7 Madhuri 2021-01-22 09:24:43 UTC 
Reproduce with:

[root@ci-vm-10-0-100-128 sssd]# rpm -qa sssd
sssd-2.4.0-5.el8.x86_64

Verification steps:

1. Remove debug_level parameter from sssd.conf

[root@ci-vm-10-0-100-128 sssd]# cat /etc/sssd/sssd.conf 
[sssd]
config_file_version = 2
services = nss, pam
domains = example1

[domain/example1]
ldap_search_base = dc=example,dc=test
id_provider = ldap
auth_provider = ldap
ldap_user_home_directory = /home/%u
ldap_uri = ldaps://server.example.com
ldap_tls_cacert = /etc/openldap/cacerts/cacert.pem
use_fully_qualified_names = True

2. delete logs and restart the sssd

[root@ci-vm-10-0-100-128 sssd]# systemctl stop sssd; rm -rf /var/log/sssd/*; systemctl start sssd


3. Check error message in logs

[root@ci-vm-10-0-100-128 sssd]# grep 'sss_ptr_hash_delete' . -ir
./sssd.log:(2021-01-14  6:02:38): [sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.2' from table
./sssd.log:(2021-01-14  6:02:38): [sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.3' from table
./sssd.log:(2021-01-14  6:02:38): [sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.domain_example1' from table
./sssd.log:(2021-01-14  6:02:38): [sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.domain_implicit_5ffiles' from table
./sssd.log:(2021-01-14  6:02:39): [sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.4' from table
./sssd.log:(2021-01-14  6:02:39): [sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.pam' from table
./sssd.log:(2021-01-14  6:02:39): [sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.5' from table
./sssd.log:(2021-01-14  6:02:39): [sssd] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.nss' from table
./sssd_implicit_files.log:(2021-01-14  6:02:39): [be[implicit_files]] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.2' from table
./sssd_implicit_files.log:(2021-01-14  6:02:39): [be[implicit_files]] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.3' from table
./sssd_implicit_files.log:(2021-01-14  6:02:39): [be[implicit_files]] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.pam' from table
./sssd_implicit_files.log:(2021-01-14  6:02:39): [be[implicit_files]] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.nss' from table
./sssd_implicit_files.log:(2021-01-14  6:02:39): [be[implicit_files]] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.4' from table
./sssd_implicit_files.log:(2021-01-14  6:02:39): [be[implicit_files]] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.pam' from table
./sssd_implicit_files.log:(2021-01-14  6:02:39): [be[implicit_files]] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.5' from table
./sssd_implicit_files.log:(2021-01-14  6:02:39): [be[implicit_files]] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.nss' from table
./sssd_example1.log:(2021-01-14  6:02:39): [be[example1]] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.2' from table
./sssd_example1.log:(2021-01-14  6:02:39): [be[example1]] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.3' from table
./sssd_example1.log:(2021-01-14  6:02:39): [be[example1]] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.nss' from table
./sssd_example1.log:(2021-01-14  6:02:39): [be[example1]] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.pam' from table
./sssd_example1.log:(2021-01-14  6:02:39): [be[example1]] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.4' from table
./sssd_example1.log:(2021-01-14  6:02:39): [be[example1]] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.pam' from table
./sssd_example1.log:(2021-01-14  6:02:39): [be[example1]] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.5' from table
./sssd_example1.log:(2021-01-14  6:02:39): [be[example1]] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.nss' from table
./sssd_pam.log:(2021-01-14  6:02:39): [pam] [sss_ptr_hash_delete] (0x0020): Unable to remove key ':1.5' from table
./sssd_pam.log:(2021-01-14  6:02:39): [pam] [sss_ptr_hash_delete] (0x0020): Unable to remove key 'sssd.nss' from table

Verified with:
[root@ci-vm-10-0-107-156 ~]# rpm -qa sssd
sssd-2.4.0-6.el8.x86_64

[root@ci-vm-10-0-107-156 sssd]# grep 'Unable to remove key' . -ir
[root@ci-vm-10-0-107-156 sssd]# echo $?
1

[root@ci-vm-10-0-107-156 sssd]# grep 'sss_ptr_hash_delete' . -ir
[root@ci-vm-10-0-107-156 sssd]# echo $?
1

Thus from above marking, this verified.
Comment 9 errata-xmlrpc 2021-05-18 15:04:21 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 (sssd 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-2021:1666
Note You need to log in before you can comment on or make changes to this bug.