Forums

Leon
Leon
Offline
Resolved
0 votes
His morning i was unable to access any of my windows shares, looking thru the log file - /var/log/messages - i saw this:

nslcd[1178]: [7b23c6] failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
nslcd[1178]: [7b23c6] no available LDAP server found, sleeping 1 seconds
nslcd[1178]: [7b23c6] failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
.
nslcd[1178]: [334873] no available LDAP server found

Now i don't have a LDAP server as i use Windows networking as:
Mode Simple Server
Windows Domain WORKGROUP

It seems that there was sone samba update and after my server re-start last night, i am unable to see the server on the windows network.

A pointer or 2 in the right direction will be helpful, thanks

Leon
Sunday, March 15 2015, 10:49 AM
Share this post:
Responses (9)
  • Accepted Answer

    Wednesday, October 09 2019, 07:16 AM - #Permalink
    Resolved
    0 votes
    DNS and LDAP issues are probably not not related.
    So ClearOS is running behind a router/firewall. When you changed your router, did your router LAN IP or subnet change. If you access the router from a Windows PC, that is the output of "ipconfig /all"? In ClearOS what is the result of:
    ifconfig
    ip r
    cat /etc/clearos/network.conf
    cat /etc/resolv.conf
    cat /etc/resolv-peerdns.conf


    For LDAP, did you make any manual tweaks to allow you to bind to the LDAP port 389? Also for LDAP, is the problem continual or just on boot?
    I have a VM which sometimes starts and shows "The accounts system is offline". Sometimes I can solve it by stopping both nslcd and slapd then restarting them. Other times it requires a reboot. I have not yet tried to investigate more.

    [edit]
    Can you try restarting LDAP and nslcd:
    systemctl stop slapd nslcd
    systemctl start slapd nslcd
    [/edit]
    The reply is currently minimized Show
  • Accepted Answer

    Kevin
    Kevin
    Offline
    Wednesday, October 09 2019, 04:57 AM - #Permalink
    Resolved
    0 votes
    Hi Nick,

    Yes it is running and I can query it.

    This happened once before when we replaced the external (upstream) router. DNS is not working correctly. Very strange. It's been solid for years.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, October 08 2019, 01:39 PM - #Permalink
    Resolved
    0 votes
    Since the thread is two and a half years old, it probably got resolved. Is LDAP running?
    systemctl status slapd
    The reply is currently minimized Show
  • Accepted Answer

    Kevin
    Kevin
    Offline
    Tuesday, October 08 2019, 01:21 PM - #Permalink
    Resolved
    0 votes
    Did anyone get this resolved?

    We replaced our external router and now the messages log is full of:

    Oct 8 06:14:09 dc nslcd[2381]: [6e31f4] <passwd="ldap.ldap"> no available LDAP server found, sleeping 1 seconds
    Oct 8 06:14:10 dc nslcd[2381]: [6e31f4] <passwd="ldap.ldap"> failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected
    Oct 8 06:14:10 dc nslcd[2381]: [6e31f4] <passwd="ldap.ldap"> no available LDAP server found: Can't contact LDAP server: Transport endpoint is not connected

    Any thoughts?

    Thanks
    The reply is currently minimized Show
  • Accepted Answer

    Hans
    Hans
    Offline
    Monday, February 22 2016, 07:50 PM - #Permalink
    Resolved
    0 votes
    I've got the same issue. It's driving me nuts. I disconnected my main Windows client from the "HOME" PDC domain and now I can't rejoin it.
    My main PDC server is ClearOS 6.7 Final. With all updates.
    Seems this issue presented itself when my new router was connected. It's setup pretty basic. DHCP and all. Every machine pointing to the same nameserver. All machines can ping each other.
    Some logging:
    nslcd[11543]: [ef0119] no available LDAP server found, sleeping 1 seconds
    nslcd[11543]: [ef0119] failed to bind to LDAP server ldap://127.0.0.1/: Can't contact LDAP server: Transport endpoint is not connected

    else:
    # service slapd status
    slapd (pid 25488) is running...

    # ps afxw | grep ldap
    28028 pts/1 S+ 0:00 \_ grep ldap
    25488 ? Ssl 0:00 /usr/sbin/slapd -h ldap://127.0.0.1/ ldaps://127.0.0.1 ldaps://192.168.1.100/ -u ldap

    When another Windows 7 client logs in, this message is logged:
    rpc.mountd[1905]: refused mount request from 192.168.1.182 for /username (/):not exported
    rpc.mountd[1905]: can't get hostname of 192.168.1.182


    Any ideas?
    The reply is currently minimized Show
  • Accepted Answer

    Leon
    Leon
    Offline
    Monday, March 16 2015, 03:43 PM - #Permalink
    Resolved
    0 votes
    Just an update on this, last night at 23:00 i still had the issue.
    This afternoon... it is working....

    Still no idea why it happened and what "Fixed" it....
    The reply is currently minimized Show
  • Accepted Answer

    Leon
    Leon
    Offline
    Sunday, March 15 2015, 04:25 PM - #Permalink
    Resolved
    0 votes
    Hi Ben

    There are no updates pending, check it there are any PID's open, stop and start LDAP, still the same.
    In /var/log/messages - nslcd[1178]: [fc4fbb] no available LDAP server found.

    Also did a restore to 2015/03/13 when all was working, still no access to my windows share on the network.
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, March 15 2015, 03:50 PM - #Permalink
    Resolved
    0 votes
    Leon,

    First, make sure you have all updates applied:
    yum upgrade


    If you have any dependencies issues, solve those first before you go on to the suggestions below. There was an update to the 6.6 upgrade that contained a patch where LDAP permissions were wrong.

    Sometimes it's as simple as stopping slapd a few times and then starting it up.
    service slapd stop
    service slapd stop
    service slapd start


    Also, make sure there are no hanging PID's around that relate to LDAP:

    ps afxw | grep ldap


    If you see any, you can 'kill -9 xxx' where xxx is the PID of the process related to LDAP/SLAPD.

    There's also a help page here.

    Finally, if nothing is working for you, you could reload from your latest config backup, provided you have one.

    B
    The reply is currently minimized Show
  • Accepted Answer

    Sunday, March 15 2015, 03:44 PM - #Permalink
    Resolved
    0 votes
    Is the LDAP service running ("service slapd status")? If not, can you start it?
    The reply is currently minimized Show
Your Reply