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
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
Share this post:
Responses (9)
-
Accepted Answer
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:
[/edit]systemctl stop slapd nslcd
systemctl start slapd nslcd -
Accepted Answer
-
Accepted Answer
-
Accepted Answer
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 -
Accepted Answer
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? -
Accepted Answer
-
Accepted Answer
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. -
Accepted Answer
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 -
Accepted Answer
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here.
Register Here »