[Freeipa-users] Trying to trace why a user cannot login to a client
Jakub Hrozek
jhrozek at redhat.com
Thu May 10 10:58:31 UTC 2012
On Tue, May 08, 2012 at 09:47:41PM +0000, Steven Jones wrote:
> Hi,
>
> Attached is a munin graph of what looks like a memory leak.....I suspect (if you look at the munin monthly month graph) we had no issue until I think we patched......I need to ask my admins if they did patch .......(they are not in yet).....
>
> Looking at the CPU and memory graphs in VMware the change in stability and leak is also most noticable, yet apart from uping the nsslapd-cachememsize: 10485760 to 18900000 I know of no changes to the system......attached is a vmware graph.....
>
> It now looks like I have to set a cronjob to reboot the IPA servers nightly........
>
> So since ipa2 crashed (or rather the memory-killer killed slapd), this isnt why 1/2 the users could login....that workstation points at ipa2 while others point at ipa1....is my best guess.
>
These are all real issues, but server side issues, which is outside my
domain of expertise, sorry. I also believe they are being discussed in a
separate thread?
If you happen to reproduce the System Error again, please attach
sssd_pam.log and sssd_domain.log. Thank you!
More information about the Freeipa-users
mailing list