Bug 1224682 - SSSD cache should be cleared after ipa-restore
Summary: SSSD cache should be cleared after ipa-restore
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Linux_Domain_Identity_Management_Guide
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Marc Muehlfeld
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-25 10:34 UTC by Martin Kosek
Modified: 2019-03-06 01:09 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-10 11:54:56 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Kosek 2015-05-25 10:34:33 UTC
Description of problem:
When IPA master is backed up and then restored, authentication does not work until SSSD caches are clear and restarted. Guide should have a note about it.

Related freeipa-users thread with more information:
https://www.redhat.com/archives/freeipa-users/2015-May/msg00493.html

Version-Release number of selected component (if applicable):
ipa-client-4.1.0-18.el7_1.3

Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Linux_Domain_Identity_Authentication_and_Policy_Guide/restore.html

Comment 1 Martin Kosek 2015-05-25 10:36:48 UTC
Jakub, I would welcome your advice what is the recommended procedure for restoring SSSD/clearing the caches causing FAST CCACHE issues in the referred thread.

Right now, the user simply used:

    systemctl stop sssd
    rm -f /var/lib/sss/db/*
    systemctl start sssd

Comment 2 Jakub Hrozek 2015-05-25 11:28:51 UTC
Also rm /var/lib/sss/pubconf/* and /var/lib/sss/mc/*

You could go as far as:
# find /var/lib/sss/ ! -type d | xargs rm -f
As everything except the directories can be recreated, but that's probably an overkill.

Comment 4 Aneta Šteflová Petrová 2016-06-10 11:54:56 UTC
Published in an asynchronous update.


Note You need to log in before you can comment on or make changes to this bug.