On 06/03/13 16:26, Rodney Simioni wrote:
It’s not fixed, it’s a mystery. I just created new accounts this morning
and I tried to login and it was unsuccessful, but these accounts may
work later today.
It’s just taking a very long time for the accounts to be enabled through
ssh login with ldap authentication.
Hi
Are you using nscd on the clients?
if so, there will be a delay before the cache gets refreshed.
A test, if you create a new LDAP user wibble is does:
getent passwd wibble
work on the client?
If not, try (as root on the client)
nscd -i passwd
nscd -i group
to invalidate both caches.
In short, if this were the reason, it would be because ssh cannot locate
the account info via PAM because pam_ldap is using nscd.
Cheers
Tim
--
Tim Watts
Personal Blog: http://squiddy.blog.dionic.net/
http://www.sensorly.com/ Crowd mapping of 2G/3G/4G mobile signal coverage
