Forums

Subscribe via email Subscribe via email
Subscribe via rss
Guest
or Ask a Question
Add a reply View Replies (5) →
lunzet
lunzet
Offline

clearos 5.1: nss_ldap: failed to bind to LDAP

Resolved
0 votes
Hi all,
just upgraded from cc 5.0 to clearos 5.1 using yum without any errors.
user authentication is working as far as I can tell but the following errors do appear in my log e.g. when i set the ldap options again on the admin webpage.

Anything related to clearos or just something I have installed earlier and just forgot about?

Any help is appreciated.
Thanks,
Thomas


Feb 3 22:12:00 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:00 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:00 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:00 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:00 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:00 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:00 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:00 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser sudo: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser sudo: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser runuser: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser runuser: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser runuser: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser runuser: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser runuser: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser runuser: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser runuser: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:01 turbolooser runuser: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:01 turbolooser runuser: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:02 turbolooser runuser: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:02 turbolooser runuser: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:02 turbolooser runuser: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:02 turbolooser runuser: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:02 turbolooser runuser: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:02 turbolooser runuser: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:02 turbolooser runuser: nss_ldap: could not search LDAP server - Server is unavailable
Feb 3 22:12:02 turbolooser w: nss_ldap: failed to bind to LDAP server ldap://localhost: Can't contact LDAP server
Feb 3 22:12:02 turbolooser w: nss_ldap: could not search LDAP server - Server is unavailable
In Directory / LDAP
Wednesday, February 03 2010, 09:17 PM
Subscribe via email
Share this post:
Responses (5)

  • Accepted Answer

    igor
    igor
    Offline
    Tuesday, May 24 2011, 02:28 AM - #Permalink
    Resolved
    0 votes
    As you showed us, the ldap server really start, but it keep running?, could you post your /etc/ldap.conf?
    The reply is currently minimized Show

  • Accepted Answer

    Kevin
    Kevin
    Offline
    Monday, May 23 2011, 11:19 PM - #Permalink
    Resolved
    0 votes
    Hi Dave,

    We are fighting this to on our two servers.

    Can you point us to a place to look fro what servers are being quiried and how to test for DNS errors?

    Thanks,

    Kevin
    The reply is currently minimized Show

  • Accepted Answer

    Dave Loper
    Dave Loper
    Offline
    Friday, September 10 2010, 10:25 PM - #Permalink
    Resolved
    0 votes
    It has been our experience that these issues are often the result of naming issues. Check that you can get to all the DNS server provided or that you have name services running and your server references them.

    Don't be alarmed if you webconfig runs slow while name services are not available.
    The reply is currently minimized Show

  • Accepted Answer

    lunzet
    lunzet
    Offline
    Thursday, February 04 2010, 09:06 AM - #Permalink
    Resolved
    0 votes
    both commands are running fine. I am not sure what is wrong here.....

    [root@turbolooser ~]# service ldap restart
    
slapd beenden:                                             [  OK  ]
    
slapd starten:                                             [  OK  ]
    




    
[root@turbolooser ~]# ldapsync
    
running full LDAP synchronization
    
restarting LDAP server
    
slapd beenden: [  OK  ]
    
slapd starten: [  OK  ]
    
restarting authentication server
    
saslauthd beenden: [  OK  ]
    
saslauthd starten: [  OK  ]
    
synchronizing configuration
    
synchronizing daemons with domain turbolooser.dyndns.org
    
synchronizing Samba file and print services
    
SMB-Dienste beenden: [  OK  ]
    
SMB-Dienste starten: [  OK  ]
    
synchronizing Samba netbios services
    
NMB-Dienste beenden: [  OK  ]
    
NMB-Dienste starten: [  OK  ]
    
synchronizing POP/IMAP mail
    
cyrus-imapd beenden: [  OK  ]
    
cyrus-imapd Datenbanken werden exportiert: [  OK  ]
    
cyrus-imapd Datenbanken importieren: [  OK  ]
    
cyrus-imapd starten: [  OK  ]
    
synchronizing SMTP mail
    
Postfix neu laden: [  OK  ]
    
synchronizing webmail
    
synchronizing web proxy
    
synchronizing FTP
    
Reloading proftpd: [  OK  ]
    
synchronizing antivirus
    The reply is currently minimized Show

  • Accepted Answer

    Tim Burgess
    Tim Burgess
    Offline
    Wednesday, February 03 2010, 11:20 PM - #Permalink
    Resolved
    0 votes
    What happens if you run 'service ldap restart'?

    You can also try ldapsync, which should ensure everything is singing of the same song sheet for LDAP
    The reply is currently minimized Show
Your Reply