Re: [nssldap] nscd issue

[Prentice Bisbal <prentice [at] ias.edu>]

Then the problem is not with nscd. Most likely there is a configuration
problem on that one system, or bad cache data somewhere else.

I had similar problems recently. Some were nscd-related and went away as
soon as nscd was turned off.

Prentice


Lynn York wrote:
> I have the same issue with or without NSCD running.
> 
> This is only happening on 1 client, not multiple clients.
> 
> -----Original Message-----
> From: owner-nssldap@padl.com [owner-nssldap [at] padl.com] On Behalf Of
> Prentice Bisbal
> Sent: Friday, April 23, 2010 1:30 PM
> Cc: nssldap@padl.com
> Subject: Re: [nssldap] nscd issue
> 
> Have you tried turning nscd off completely and tested?
> 
> If the errors go away after shutting down nscd, the problem is with
> nscd. If the problems remain, the problem is NOT with nscd. When stop
> nscd, make sure it's really off using 'ps'. If daemon is hung, the
> shutdown script may not be able to kill it.
> 
> Are multiple ldap clients having the same problem, or is it just one?
> Can you reproduce this problem on another system
> 
> It really sounds like you nave a name service problem of some sort
> outside of nscd, but it's too difficult to for certain from this distance.
> 
> Prentice
> 
> Lynn York wrote:
>> I keep getting this error in /var/log/messages
>>
>> Apr 23 10:28:02 hlmon01 getent: nss_ldap: failed to bind to LDAP server
>> ldap://ldap01.mavenwire.com:389: Can't contact LDAP server
>> Apr 23 10:28:02 hlmon01 getent: nss_ldap: could not search LDAP server -
>> Server is unavailable
>>
>> -----Original Message-----
>> From: Prentice Bisbal [prentice [at] ias.edu]
>> Sent: Friday, April 23, 2010 11:59 AM
>> To: Lynn York
>> Subject: Re: [nssldap] nscd issue
>>
>> Lynn York wrote:
>>  >
>>>                 I am having an issue with NSCD caching an old host for
>>> ldap authentication.  I have already run the "nscd -i host" command
>>> multiple times and it doesn't correct the issue.  So I removed the DB
>>> files for nscd and turned off caching then restarted nscd and still
>>> having the same issue.  The issue only happens when I comment out the
>>> correct ldap servers in /etc/ldap.conf for testing purposes.  Can any
>>> shed any light on this?
>>>
>> Are you sure it's the NSCD caching? I had a similar problem recently,
>> and it was the DNS or ARP cache storing the wrong information for a
>> server, or something like that.
>>
>> Check your hosts file, nsswitch.conf, dns records (using host or dig),
>> and ARP tables. The problem may not be your name service cache.
>>
> MavenWire - We DELIVER
> http://www.mavenwire.com
> 
> This e-mail and any attached files may contain confidential and/or privileged 
> material for the sole use of the intended recipient.  Any review, use, 
> distribution or disclosure by others is strictly prohibited. If you are not 
> the intended recipient (or authorized to receive this e-mail for the 
> recipient), you may not review, copy or distribute this message.  Please 
> contact the sender by reply e-mail and delete all copies of this message.
>