Bug 748818 - SSSD not functional after "self" reboot
Summary: SSSD not functional after "self" reboot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sssd
Version: 5.8
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: rc
: ---
Assignee: Stephen Gallagher
QA Contact: IDM QE LIST
URL:
Whiteboard:
Depends On: 740501 784707
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-25 13:11 UTC by Jakub Hrozek
Modified: 2020-05-04 10:24 UTC (History)
7 users (show)

Fixed In Version: sssd-1.5.1-38.el5
Doc Type: Bug Fix
Doc Text:
Clone Of: 740501
Environment:
Last Closed: 2012-02-21 06:23:05 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 1974 0 None closed sssd_nss segfaults when reconnecting to sssd_be 2020-05-04 10:24:26 UTC
Red Hat Product Errata RHBA-2012:0164 0 normal SHIPPED_LIVE sssd bug fix and enhancement update 2012-02-20 15:06:51 UTC

Comment 1 Kaushik Banerjee 2011-12-30 19:42:08 UTC 
Verified with timeout = 1 that user lookup and auth works even after the backend is restarted.


Verified in version:
# rpm -qi sssd | head
Name        : sssd                         Relocations: (not relocatable)
Version     : 1.5.1                             Vendor: Red Hat, Inc.
Release     : 47.el5                        Build Date: Tue 13 Dec 2011 08:49:14 AM EST
Install Date: Wed 28 Dec 2011 02:47:40 AM EST      Build Host: x86-002.build.bos.redhat.com
Group       : Applications/System           Source RPM: sssd-1.5.1-47.el5.src.rpm
Size        : 3651336                          License: GPLv3+
Signature   : DSA/SHA1, Wed 14 Dec 2011 12:17:11 PM EST, Key ID fd372689897da07a
Packager    : Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>
URL         : http://fedorahosted.org/sssd/
Summary     : System Security Services Daemon
Comment 2 errata-xmlrpc 2012-02-21 06:23:05 UTC 
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-0164.html
Note You need to log in before you can comment on or make changes to this bug.