* Sjoerd Simons ([EMAIL PROTECTED]) wrote: > I've rebooted one of the systems with the ipv6 module blacklisted. After that > it still shows exactly the same behaviour (identicaly trace, just the ipv6 > addresses replaced by ipv4 addresses)...
Hmm, ok.
> > Can you check if there's a file in /var/lib/libnss-ldap ? I doubt that
> > has anything to do with this but who knows.
>
> Nope, completely empty.
Good, that's how it should be.
> I'm not sure what info would be helpfull. But fwiw, it happens on both amd64
> and x86 machines. We've got two ldap servers (both accessible via ipv4 and
> ipv6), one runs sarge the other one runs etch.
Huh, alright.
> Downgrading the package to the testing version solves the problem. I can't
> pinpoint it closer as i've only noticed it quite recently when nscd was not
> running for some reason.
Are your config files world-readable? Maybe nscd can see them since
it's running as root but a regular user can't and that causes the
problem... Do you see anything interesting in your logs? What if you
enable 'debug' in your libnss-ldap.conf?
Thanks,
Stephen
signature.asc
Description: Digital signature
