Bug 1794016
| Summary: | sssd_be frequent crash | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Sumit Bose <sbose> |
| Component: | sssd | Assignee: | SSSD Maintainers <sssd-maint> |
| Status: | CLOSED ERRATA | QA Contact: | sssd-qe <sssd-qe> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 8.2 | CC: | abokovoy, extras-qa, grajaiya, jhrozek, lslebodn, mniranja, mzidek, olivier.sallou, pbrezina, rharwood, sbose, sgoveas, ssorce, tscherf |
| Target Milestone: | rc | Flags: | pm-rhel:
mirror+
|
| Target Release: | 8.0 | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | sync-to-jira | ||
| Fixed In Version: | sssd-2.2.3-12.el8 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1792184 | Environment: | |
| Last Closed: | 2020-04-28 16:56:29 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: | |||
|
Description
Sumit Bose
2020-01-22 14:01:15 UTC
Hi, I would suggest to include commit 007d5b79b7aef67dd843ed9a3b65095faaeb580f to RHEL-8.2 because it fixes an issue in the background refresh if multiple domains are configured in sssd.conf. Since on RHEL-8.2 the files provider is activated by default this might happen quite often. Steeve, if you agree, please give qa_ack+. bye, Sumit Version:
Reproducing the issue:
sssd-ldap-2.2.2-1.el8.x86_64
sssd-2.2.2-1.el8.x86_64
sssd-dbus-2.2.2-1.el8.x86_64
sssd-tools-2.2.2-1.el8.x86_64
sssd-client-2.2.2-1.el8.x86_64
sssd-common-2.2.2-1.el8.x86_64
sssd-ad-2.2.2-1.el8.x86_64
sssd-proxy-2.2.2-1.el8.x86_64
sssd-winbind-idmap-2.2.2-1.el8.x86_64
sssd-krb5-common-2.2.2-1.el8.x86_64
sssd-krb5-2.2.2-1.el8.x86_64
sssd-kcm-2.2.2-1.el8.x86_64
1. Join the system to Windows AD using realm
3. Enable files provider and add refresh_expired_interval parameter as given below:
[sssd]
domains = SARABHAI.TEST, files
config_file_version = 2
services = nss, pam
[domain/files]
id_provider = files
[domain/SARABHAI.TEST]
ad_domain = SARABHAI.TEST
krb5_realm = SARABHAI.TEST
realmd_tags = manages-system joined-with-adcli
cache_credentials = True
id_provider = ad
krb5_store_password_if_offline = True
default_shell = /bin/bash
ldap_id_mapping = True
use_fully_qualified_names = True
fallback_homedir = /home/%u@%d
access_provider = ad
entry_cache_timeout = 5400
refresh_expired_interval = 4000
4. Restart sssd
5. sssd crashes:
Feb 26 12:09:12 vm-10-0-154-49.hosted.upshift.rdu2.redhat.com systemd-coredump[10352]: Process 10329 (sssd_be) of user 0 dumped core.
Stack trace of thread 10329:
#0 0x00007ff432c38206 sysdb_user_base_dn (libsss_util.so)
#1 0x00005592fd1543b3 be_refresh_step (sssd_be)
#2 0x00005592fd1547a3 be_refresh_send (sssd_be)
#3 0x00005592fd153bff be_ptask_execute (sssd_be)
#4 0x00007ff42fcd7279 tevent_common_invoke_timer_handler (libtevent.so.0)
#5 0x00007ff42fcd741e tevent_common_loop_timer_delay (libtevent.so.0)
#6 0x00007ff42fcd8959 epoll_event_loop (libtevent.so.0)
#7 0x00007ff42fcd685b std_event_loop_once (libtevent.so.0)
#8 0x00007ff42fcd1a55 _tevent_loop_once (libtevent.so.0)
#9 0x00007ff42fcd1cfb tevent_common_loop_wait (libtevent.so.0)
#10 0x00007ff42fcd67eb std_event_loop_wait (libtevent.so.0)
#11 0x00007ff432c67dc7 server_loop (libsss_util.so)
#12 0x00005592fd14b36b main (sssd_be)
#13 0x00007ff42f1a9873 __libc_start_main (libc.so.6)
#14 0x00005592fd14b52e _start (sssd_be)
-- Subject: Process 10329 (sssd_be) dumped core
6. Update sssd to sssd-2.2.3-17.el8.x86_64
Restart sssd and no crashes seen.
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, 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-2020:1863 |