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.
Looks like https://github.com/SSSD/sssd/issues/5947 ?
Could you please attach entire /var/log/sssd/sssd_cockpit.lan.log and sssd.log?
Btw, why do you think it "crashes"?
Jan 12 11:38:18 sssd_nss[861]: Shutting down (status = 0)
Jan 12 11:38:18 sssd_be[859]: Shutting down (status = 0)
Jan 12 11:38:18 systemd[1]: sssd.service: Succeeded.
Jan 12 11:38:18 systemd[1]: Stopped System Security Services Daemon.
Jan 12 11:38:18 systemd[1]: Starting System Security Services Daemon...
Jan 12 11:38:18 sssd[1930]: Starting up
-- looks like graceful service restart.
> Looks like https://github.com/SSSD/sssd/issues/5947 ?
Could be -- we had two other test cases which did not fail functionally, but triggered a new SELinux violation:
avc: denied { name_connect } for comm="cockpit-session" dest=389 scontext=system_u:system_r:cockpit_session_t:s0 tcontext=system_u:object_r:ldap_port_t:s0 tclass=tcp_socket
This sounds related then? We can open our SELinux policy to allow that, but it didn't seem obvious to me why cockpit-session would need to talk to the LDAP port. It only talks to sssd-ifp over D-Bus, and contexts shouldn't transition that way.
> Could you please attach entire /var/log/sssd/sssd_cockpit.lan.log and sssd.log
I did, see the "/var/log/sssd" attachment
> why do you think it "crashes"?
Because it keeps stopping itself with each request. It's certainly not a "crash" in the "segfault" sense, just that it seems unusual, and the log keeps complaining about "sssd is offline".
Thanks!
Hi,
I agree, it is most probably https://github.com/SSSD/sssd/issues/5947. Martin, can you set 'debug_level = 9' in the [domain/...] section and then check ldap_child.log if there is ':389' at the end of the KDC IP address? Alternatively you can check '/var/lib/sss/pubconf/kdcinfo.*' is the addresses end in ':389'.
Btw, Iker is already working on a fix.
bye,
Sumit
(In reply to Martin Pitt from comment #3)
>
> avc: denied { name_connect } for comm="cockpit-session" dest=389
> scontext=system_u:system_r:cockpit_session_t:s0
> tcontext=system_u:object_r:ldap_port_t:s0 tclass=tcp_socket
>
> This sounds related then? We can open our SELinux policy to allow that, but
> it didn't seem obvious to me why cockpit-session would need to talk to the
> LDAP port. It only talks to sssd-ifp over D-Bus, and contexts shouldn't
> transition that way.
Probably 'cockpit-session' uses libkrb5 that talks to port (wrongly) specified by SSSD in '/var/lib/sss/pubconf/kdcinfo.*'?
> Probably 'cockpit-session' uses libkrb5 that talks to port (wrongly) specified by SSSD
Right, it does use libkrb5. Thanks Alexey -- so this is just a different kind of fallout, and we don't change the SELinux policy for now.
> set 'debug_level = 9' in the [domain/...] section and then check ldap_child.log if there is ':389' at the end of the KDC IP address
Yes, I see lots of
(2022-01-13 1:43:44): [be[cockpit.lan]] [sdap_ldap_connect_callback_add] (0x4000): New connection to [ldap://f0.cockpit.lan:389/??base] with fd [21]
(2022-01-13 1:43:44): [be[cockpit.lan]] [sdap_get_rootdse_send] (0x4000): Getting rootdse
(2022-01-13 1:43:44): [be[cockpit.lan]] [sdap_print_server] (0x2000): Searching 10.111.112.100:389
> Alternatively you can check '/var/lib/sss/pubconf/kdcinfo.*' is the addresses end in ':389'.
# cat /var/lib/sss/pubconf/kdcinfo.COCKPIT.LAN
10.111.112.100:389
Thanks!
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-2022:2070