We have millions of entries in the OU and our clients don't see all the entries since we do filter them on our side (and we don't manage the server side). It would be nice to be able to find out which users/groups are affected on our side so we can take that to the admins of the servers. How would you review the data files in memory cache to see the content? All I get back is "data" when I run 'file *_corrupted' which isn't exactly useful. I'm assuming it's used in sssd somehow. Does sssctl have any functionality to help here? Trying to learn how to fish (so you guys don't have to keep feeding me :-)).
thanks =G= ________________________________________ From: Lukas Slebodnik <[email protected]> Sent: Wednesday, October 4, 2017 9:08 AM To: End-user discussions about the System Security Services Daemon Subject: [SSSD-users] Re: sssd email login performance EXTERNAL On (04/10/17 12:46), Galen Johnson wrote: >It's possible as we've had that happen in the past (and complained loudly to >the team that keeps doing it). Is there any way to read those files to see >which users/groups are contained in them so we can verify? ldbsearch doesn't >seem to read them or I'm giving it the wrong args. If this is already in the >troubleshooting/debug docs, I've missed it. > Memory cache is in binary format. If you renamed group the it is a known bug https://fedorahosted.org/sssd/ticket/3282 If it is a colliding UID/GID then preffered way is to fix it on server side. LS _______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected] _______________________________________________ sssd-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
