Thank you for reporting this bug and helping to make Ubuntu even better. I haven't looked at this very closely yet, but think this may be network related, which is why 'bind_policy soft' would help (ldap will fail immediately, rather than waiting for a *long* time with 'bind_policy hard'). If the network is starting after LDAP lookups are being made, you will have this problem.
Until this issue is properly fixed, workarounds are the same as for sometimes disconnected users (eg laptops): 1. use 'bind_policy soft' in /etc/ldap.conf 2. use libnss-db 3. use libpam-ccreds A desktop system may be able to get away with just the first, whereas laptops will need all three. Though bug 51315 is unrelated, the workarounds people used there may also be helpful. Note that assuming it is indeed just a networking issue, the machine will *eventually* come up with 'bind_policy hard', but it will be several minutes (it would be helpful if you confirmed this). BTW: the fsck error should be unrelated and is probably just that /dev/sda1 is mounted read/write when fsck is trying to run. -- 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
