Bug 754114
| Summary: | [abrt] sssd-1.6.3-1.fc16: ping_check: Process /usr/sbin/sssd was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas Lake <tom+f> | ||||||
| Component: | sssd | Assignee: | Stephen Gallagher <sgallagh> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 16 | CC: | jhrozek, sbose, sgallagh, ssorce | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:2c86b854d5d91946c8b59b5c1a5f36d5fa59f9c3 | ||||||||
| Fixed In Version: | sssd-1.8.1-7.fc16 | Doc Type: | Bug Fix | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 759186 (view as bug list) | Environment: | |||||||
| Last Closed: | 2012-03-02 01:17:23 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 759186 | ||||||||
| Attachments: |
|
||||||||
|
Description
Thomas Lake
2011-11-15 12:50:22 UTC
Created attachment 533759 [details]
File: backtrace
Upstream ticket: https://fedorahosted.org/sssd/ticket/1090 Apart from us safeguarding against the segfault, can you check or attach SSSD logs if there are any error messages? sssd_be seems to be starting way too often, maybe there's some kind of startup error. Created attachment 533775 [details]
Tarball of /var/log/sssd on one of the affected machines
(In reply to comment #4) > Created attachment 533775 [details] > Tarball of /var/log/sssd on one of the affected machines From the logs it seems that back end has trouble connecting to the monitor socket. Is SELinux Enforcing or Permissive on your machines? If it's Enforcing can you check for AVC denials? Unfortunately the logs are not verbose enough to allow more analysis. Can you put debug_level = 7 into the [sssd] and [domain/default] of your sssd.conf, restart SSSD and attach the logs once the issue hits again? SELinux is in enforcing mode, but the only denial I can see is related to system-config-firewall - which seems unlikely to be related to this problem. The issue hasn't recurred yet, will post logs if/when it does sssd-1.8.0-6.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/FEDORA-2012-2196/sssd-1.8.0-6.fc17 sssd-1.8.0-6.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/sssd-1.8.0-6.fc16 Package sssd-1.8.0-6.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing sssd-1.8.0-6.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-2725/sssd-1.8.0-6.fc16 then log in and leave karma (feedback). sssd-1.8.0-6.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report. sssd-1.8.1-7.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report. |