However the one group that the user needs to be a member to log in is On the non-working server, 'id username' returns *mostly* the same list. On a working server, I can do 'id username' and get back the proper list of All our auth is done through AD and not a thing has So we are having issues with a couple servers where users suddenly won't beĪble to log in. Is this expected behaviour? I would have though that only if an account actually makes a login attempt or uses a service then the information would be collected from AD/IPA/LDAP I may be wrong and I am sure I will learn something here. We have several hundred locally defined users in the passwd file at the moment. I increased the nss stanza to have enum_cache_timeout = 1200Ĭlearly this will not help with the first enumeration - but it does keep the data for longer in the cache.Īlso when sssd first starts up it seems to look at every account in the local /etc/passwd file and request information about it. This says to me that the OS is very busy doing things,Īnd does not have time to service interrupts from the keyboard/mouse. Ie there is no mouse pointer and the keyboard does not respond. However I see that when I am using the windowing system the mouse 'goes away' and sometimes the keyboard too, When the sssd service starts the sssd_be process is taking 100% CPU. I have set up sssd authentication on a Ubuntu Xenial workstation, with the Lightdm windowing manager.
0 kommentar(er)
