Bug 967004
| Summary: | [abrt] sssd-1.10.0-4.fc19.beta1: get_server_status: Process /usr/libexec/sssd/sssd_be was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | William Brown <william> | ||||||||||||||||||||||||||
| Component: | sssd | Assignee: | Jakub Hrozek <jhrozek> | ||||||||||||||||||||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||||
| Version: | 19 | CC: | c.schmitt, jhrozek, lslebodn, okos, pbrezina, sbose, sgallagh, ssorce, stefw, william | ||||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:00e402a8e8ca224c5643dd885c7468396acc53fc | ||||||||||||||||||||||||||||
| Fixed In Version: | sssd-1.10.1-1.fc19 | Doc Type: | Bug Fix | ||||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||||
| Last Closed: | 2013-07-09 15:31:13 UTC | Type: | --- | ||||||||||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||||||||||
| Embargoed: | |||||||||||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||||||||||
|
Description
William Brown
2013-05-24 13:51:37 UTC
Created attachment 752631 [details]
File: backtrace
Created attachment 752632 [details]
File: cgroup
Created attachment 752633 [details]
File: core_backtrace
Created attachment 752634 [details]
File: dso_list
Created attachment 752635 [details]
File: environ
Created attachment 752636 [details]
File: limits
Created attachment 752637 [details]
File: maps
Created attachment 752638 [details]
File: open_fds
Created attachment 752639 [details]
File: proc_pid_status
Created attachment 752640 [details]
File: var_log_messages
Thank you for the bug report, according to the backtrace this is not a known problem. I will clone the bug report upstream. Upstream ticket: https://fedorahosted.org/sssd/ticket/1947 Hello William, I tried to reproduce the issue, but haven't succeeded. Are you able to reproduce this? Could you please provide us a corefile and sanitized sssd.conf and sssd logs? I am able to intermittently reproduce this. It depends on networking state and other factors I think. When it next happens I will send the core and log from that time to you. It would be helpful to summarize what exactly happened in the environment, when this issue occurs next time, but the corefile and logs will suffice, thanks! Setting needinfo to make it clear we're waiting on steps to reproduce and/or coredump with logs. (In reply to Ondrej Kos from comment #16) > Setting needinfo to make it clear we're waiting on steps to reproduce and/or > coredump with logs. I have the coredump. Will attach now. It appears to correlate to my wireless dropping out overnight. Created attachment 756149 [details]
Coredump of SSSD
Created attachment 756150 [details]
Logs from time of crash
Crash occured at 21:49 or slightly before according to ABRT.
Hello, patch was submitted upstream and are awaiting review. Fixed upstream. Ran 'sudo make install' on an unrelated task. Have not changed sssd configuration for last couple weeks. Was rather out of the blue. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/sssd/sssd_be --domain security.baseos.qe --debug-to-files crash_function: get_server_status executable: /usr/libexec/sssd/sssd_be kernel: 3.9.4-301.fc19.x86_64 package: sssd-common-1.10.0-12.fc19.beta2 reason: Process /usr/libexec/sssd/sssd_be was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 0 sssd-1.10.0-13.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/sssd-1.10.0-13.fc19 Package sssd-1.10.0-13.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sssd-1.10.0-13.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-11899/sssd-1.10.0-13.fc19 then log in and leave karma (feedback). client setup from scratch as a freeipa-client i logged in and started my vpn. reporter: libreport-2.1.5 backtrace_rating: 4 cmdline: /usr/libexec/sssd/sssd_be --domain envisia.de --debug-to-files crash_function: get_server_status executable: /usr/libexec/sssd/sssd_be kernel: 3.9.8-300.fc19.x86_64 package: sssd-common-1.10.0-12.fc19.beta2 reason: Process /usr/libexec/sssd/sssd_be was killed by signal 11 (SIGSEGV) runlevel: N 5 uid: 0 Sorry about that, Christian. There is a patch on the upstream mailing list for an unrelated (yet similar) issue. Feel free to open another bugzilla. Oh, ty i've seen that already. I'm really new to fedora and just automatically posted that via the desktop tool. Currently i dont have many problems yet. Just playing around with some stuff. Maybe when i'm confident enough i could patch some things aswell. But since everytime something crashes on my side, the things are fixed already.. Btw mate-desktop is really stable. But thanks for the info, ive got the patched package already ;) Fixed in sssd-1.10.0-16 which is in stable updates already. sssd-1.10.1-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/sssd-1.10.1-1.fc19 sssd-1.10.1-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. |