nslcd cannot connect to ldapserver on ports other than 389/636 when started through init script, but connects to ldap server when started manually in debug mode

Solution Verified - Updated -

Issue

  • nslcd cannot connect to ldapserver on ports other than 389/636 when started through init script, but connects to ldap server when started manually in debug mode.

Following errors are seen in /var/log/messages

nslcd[5205]: [495cff] no available LDAP server found
nslcd[5205]: [e8944a] no available LDAP server found
nslcd[5260]: [8b4567] failed to bind to LDAP server ldap://ldap.example.com:389/: Can't contact LDAP server: Transport endpoint is not connected
nslcd[5260]: [8b4567] no available LDAP server found, sleeping 1 seconds
nslcd[5260]: [8b4567] failed to bind to LDAP server ldap://ldap.example.com:389/: Can't contact LDAP server: Transport endpoint is not connected
nslcd[5260]: [8b4567] no available LDAP server found, sleeping 1 seconds

Environment

  • Red Hat Enteprise Linux 6
  • LDAP server running on ports other than 389 and 636

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content