Re: pam_ldap and nss_ldap can't connect to LDAP server(s)

I believe installing nscd resolves these messages.

On Thu, 2009-06-25 at 07:31 -0700, Karl O. Pinc wrote:

On 06/24/2009 11:35:22 PM, Aaron Hicks wrote:

> Binding ldapsearch with an appropriate username and password allows
> 'proper' searches, and gives meaningful responses.
> 

  /var/log/messages is full of:
> 
> Jun 25 15:24:46 vmcluster gdm[5986]: nss_ldap: could not search LDAP
> server - Se
> rver is unavailable

Well, this is just a guess after a long time not thinking of ldap....
I don't see a host in ldap.conf, so it's probably trying to connect
to the default  server (localhost?).  Hence the above message.


> My /etc/ldap.conf looks like (omitting sections left as default):
> 

> # The distinguished name to bind to the server with.
> # Optional: default is to bind anonymously.
> # Note: We have users with spaces in their cn!
> binddn "cn=User  
> Name,ou=internal,ou=users,ou=accounts,cn=,dc=our,dc=long,dc=domain,dc=co,dc=nz"
> 
> # The credentials to bind with.
> # Optional: default is no credential.
> bindpw secret

If you use these credentials (and the right host) with ldapsearch
you get a good answer?

Karl <kop@...>
Free Software:  "You don't pay back, you pay forward."
                  -- Robert A. Heinlein

_______________________________________________________ Bryan Payne Systems Administrator  |  SPEED FC   |  www.speedfc.com p. 214.258.0129  |   e. bpayne@... 10300 Sanden Drive, Suite 100   |   Dallas Texas 75238 _______________________________________________________