An added twist to this bug... I've been running LDAP servers on Feisty and Breezy and Hoary for a long time, without this problem. The latest couple I've set up have shown me this problem. This problem is very significant in this case because the LDAP servers themselves are unable to boot. Because slapd is started late in the boot-process by default (S41 in rc2.d), we find ourselves caught in the middle of a race condition, or rather deadlock. klogd can't boot because it is waiting for the LDAP server which will not initialize because it's waiting on klogd.
My initial work-around was simply moving SLAPD to start as S13 in rcS.d, right after networking. However, reading how much of a problem this is for Gutsy, I will be considering other tactics. I recently built a significant fraction of an infrastructure on Gutsy, and have been incorporating each machine into LDAP. Since they are all static- addressed and the network is available and fast, I've not seen this problem on non-LDAP servers to date... but each LDAP server I have built lately has been a headache (since it's been just enough time since the last one that I forget to modify the boot order). Best of luck to you guys. Keep up the great work! I'm looking forward to Hardy. Matt -- ldap config causes Ubuntu to hang at a reboot https://bugs.launchpad.net/bugs/155947 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
