https://bugzilla.redhat.com/show_bug.cgi?id=1884912
Bug ID: 1884912 Summary: [abrt] sssd-common: __strcmp_avx2(): sssd_be killed by SIGSEGV Product: Fedora Version: 32 Hardware: x86_64 Status: NEW Whiteboard: abrt_hash:a07038fd78acc47fd66b266203cafebd50509e00;VAR IANT_ID=workstation; Component: sssd Assignee: sssd-maintainers@lists.fedoraproject.org Reporter: rbrattai@redhat.com QA Contact: extras-qa@fedoraproject.org CC: abokovoy@redhat.com, atikhono@redhat.com, jhrozek@redhat.com, lslebodn@redhat.com, mzidek@redhat.com, pbrezina@redhat.com, rharwood@redhat.com, sbose@redhat.com, ssorce@redhat.com Target Milestone: --- Group: fedora_contrib_private Classification: Fedora
Description of problem: Always happens when the Kerberos tickets expire after letting the system sit overnight.
Log in to Redhat krbtgt/REDHAT.COM@REDHAT.COM let the system sit overnight, or until ticket expires try to login via gdm or vt login fails
Version-Release number of selected component: sssd-common-2.3.1-2.fc32
Additional info: reporter: libreport-2.13.1 backtrace_rating: 4 cgroup: 0::/system.slice/sssd.service cmdline: /usr/libexec/sssd/sssd_be --domain redhat.com --uid 0 --gid 0 --logger=files crash_function: __strcmp_avx2 executable: /usr/libexec/sssd/sssd_be journald_cursor: s=a7dff00ea3904bcf94e9c47f3af11249;i=99168;b=d69fa027bac74e0c82bae802fce15dc2;m=8e9b12f6b4;t=5b0c43dd4cdcb;x=5af4a1ece75efc5a kernel: 5.7.17-200.fc32.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 0
Truncated backtrace: Thread no. 1 (10 frames) #0 __strcmp_avx2 at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101 #1 be_resolve_server_process at src/providers/data_provider_fo.c:671 #2 be_resolve_server_done at src/providers/data_provider_fo.c:555 #3 fo_resolve_service_server at src/providers/fail_over.c:1165 #4 _tevent_req_error at ../../tevent_req.c:211 #5 resolve_srv_done at src/providers/fail_over.c:1466 #6 fo_discover_srv_done at src/providers/fail_over_srv.c:141 #7 resolv_discover_srv_done at src/resolv/async_resolv_utils.c:302 #8 resolv_getsrv_done at src/resolv/async_resolv.c:1762 #9 qcallback at /usr/src/debug/c-ares-1.15.0-5.fc32.x86_64/ares_query.c:183
Potential duplicate: bug 1773488
https://bugzilla.redhat.com/show_bug.cgi?id=1884912
--- Comment #13 from Ross Brattain rbrattai@redhat.com --- Looks like dup of https://bugzilla.redhat.com/show_bug.cgi?id=1773488
I can reproduce at will, just let the system sit overnight.
https://bugzilla.redhat.com/show_bug.cgi?id=1884912
Ross Brattain rbrattai@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Severity|unspecified |high
--- Comment #16 from Ross Brattain rbrattai@redhat.com --- severity High because it locks me out as my user and I have to login as `root` then `su` to fix.
https://bugzilla.redhat.com/show_bug.cgi?id=1884912
Alexey Tikhonov atikhono@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEW Assignee|atikhono@redhat.com |sssd-maintainers@lists.fedo | |raproject.org
Product: Fedora Version: 33 Component: sssd
Alexey Tikhonov atikhono@redhat.com has asked sssd-maintainers sssd-maintainers@lists.fedoraproject.org for needinfo: Bug 1884912: [abrt] sssd-common: __strcmp_avx2(): sssd_be killed by SIGSEGV https://bugzilla.redhat.com/show_bug.cgi?id=1884912
https://bugzilla.redhat.com/show_bug.cgi?id=1884912
Alexey Tikhonov atikhono@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Assignee|sssd-maintainers@lists.fedo |pbrezina@redhat.com |raproject.org | Flags|needinfo?(sssd-maintainers@ | |lists.fedoraproject.org) |
https://bugzilla.redhat.com/show_bug.cgi?id=1884912
--- Comment #41 from Pavel Březina pbrezina@redhat.com --- Hi, Ross. Does the issue still persist? If yes, can you please provide fresh logs?
Always happens when the Kerberos tickets expire after letting the system sit overnight.
I don't think we should focus on Kerberos here, rather on the "letting the system sit overnight" part. Is it possible that VPN connection fails during this time? Because I see in the logs prior the crash that SSSD can not resolve the DNS SRV record.
My best guess at this moment is that SSSD is online, then VPN fails and SSSD fails recover by going correctly offline and crash instead on something unexpected.
https://bugzilla.redhat.com/show_bug.cgi?id=1884912
--- Comment #42 from Ross Brattain rbrattai@redhat.com --- Has not reproduced on Fedora 33 so far. sssd-client-2.4.2-2.fc33.x86_64
https://bugzilla.redhat.com/show_bug.cgi?id=1884912
Pavel Březina pbrezina@redhat.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED Resolution|--- |INSUFFICIENT_DATA Last Closed| |2021-04-08 13:19:48
--- Comment #43 from Pavel Březina pbrezina@redhat.com --- Thank you for the information. I'm going to close this BZ since I was not able to reproduce it locally and we have no new lead. Please, reopen it if the issue occurs again.
sssd-maintainers@lists.fedoraproject.org