rootninja

I found this posted at some complicated site where it was hard to find the login button. Everything was so cluttered on the site I gave up and decided to post the question here, and answer it here, and maybe this guy (and anyone else having this problem) will find my solution. This may not be the answer to his exact problem, but it worked for me when I ran into this issue.

I am hopping someone had similar issue with ldap, so LDAP server up and running ( debin stable ), all works super, client ( debian testing ) all ok.
When is server up and running I can without problem reboot clinet and it works, but if is server down, the client hangs at stage :

Starting system message bus :dbus

and that is the end I have to reset it. I found what is root cause. In /etc/libnss-ldap.conf just comment out
#uri ldap://192.168.1.100 —the address of ldap server
but I am looking for some workaround not to change that conf file and be able to reboot client.
When the server is shutdown client hangs at boot stage with above message, and I have to reset it use soem livecd mount sysstem and shange as stated before, otherwise it does not works.
I am just wondering if someone can help, and make able to reboot client and not to hang at this stage.
Any hint is welcome and thank you all in advance

Check iptables or other firewall applications running on that machine. If ldap traffic is being blocked, this could be causing it to hang. That’s what happened to me. I changed the firewall rules and forgot to add the ldaps rule and it broke. I could work around it by hitting “i” while booting and it would go into Interactive mode and allow me to say No to the MessageBus service. Everything else came up fine in runlevels 3 and 5, but it would always hang when loading the dbus app.

A work around for this could be to swap out your authconfig files. I ran authconfig-tui to temporarily disable ldap, and then ran it again once it was up and running. But there’s no reason you couldnt just have 2 configs and swap them out after booting up and before shutting down. But if my problem is the same as yours, the real answer is to fix the firewall rules!!!