Bug 808597
Summary: | sssd_nss crashes on request when no back end is running | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Jakub Hrozek <jhrozek> |
Component: | sssd | Assignee: | Stephen Gallagher <sgallagh> |
Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.3 | CC: | grajaiya, jgalipea, kbanerje, prc |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | sssd-1.8.0-22.el6 | Doc Type: | Bug Fix |
Doc Text: |
No documentation required
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 11:56:39 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: |
Description
Jakub Hrozek
2012-03-30 19:35:42 UTC
This bugzilla is tracking the sssd_nss problem. The sssd_be crash is being tracked separately in bug #808597. To reproduce: 1. kill sssd_be so that is stops definitely for x in $(seq 1 4); do kill -9 $(pidof sssd_be); done 2. make sure no sssd_be process is running now pidof sssd_be 3. getent passwd someuser With the current packages, the sssd_nss process crashes with SIGABRT. It should not crash, but rather revert to returning data from cache. # getent passwd puser1 puser1:*:1001:1001:Posix User1:/home/puser1: # for x in $(seq 1 4); do kill -9 $(pidof sssd_be); done # pidof sssd_be # getent passwd puser1 puser1:*:1001:1001:Posix User1:/home/puser1: Verified with sssd-1.8.0-23 Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: No documentation required 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. http://rhn.redhat.com/errata/RHBA-2012-0747.html |