After upgrading my server to Gutsy booting hangs at "Starting kernel log daemon"

[Alexander Nofftz]

After upgrading my server to Gutsy booting hangs at "Starting kernel log daemon". No [ OK ] is displayed, but login prompt appears. I'm however not able to log in. A password prompt is displayed, but after typing in nothing happens. I've tried to disable klogd, but now the booting hangs at starting the MySQL server, other listening daemons like syslogd or dhcp3-server however worked. Switching back to an older kernel also doesn't work. I'm using LDAP (slapd), but not for local accounts (uid<1000). When booting in runlevel S (recovery mode), I'm able to log in, but trying to start those daemons also locks up the system. SysRq-T shows nothing.

[Alexander Nofftz (alexnofftz)]

Got it. After moving slapd from S19slapd to S10slapd, so it's started immediately before klogd, everythings works again.

Maybe there is some lockup on LDAP queries when no server is present? As noted before, all local accounts are in /etc/passwd, not LDAP.

[darren.headrick (darren-13827)]

I am seeing this behavior too, although After approx 5 minutes, it continues booting. I dont have the slapd package installed on my system. Should I file a seperate bug?

[Sarazar (rcrook)]

I have the same issue. It is related to LDAP. I run an ldap server and have configured the system to use LDAP. If you disable ldap in the nsswitch.conf the laptop boot fine. If it is enabled the klogd startup srcipt seems to pause for a long time. My guess is when the script changes the ownership of the klogd fifo/socket it sits and waits for an ldap response. I am not sure why the ldap is taking so long as I think the network is up at the time but I am not sure. This has only showed since the upgrade, feisty worked fine.

I am attching a copy of the nsswitch.conf and my ldap.conf (sanitized)..

[John Affleck (jraffleck)]

Same thing. Simple setup with a Dapper LDAP server and a Gutsy LDAP client. Hangs at 'Starting kernel log daemon', although haven't had the patience to wait to see if it'll continue after waiting 5 minutes. Also works fine with Feisty.

[John Affleck (jraffleck)]

Definitely won't continue after 5 minutes. Many hours passed with it still 'starting kernel log daemon'

[Sarazar (rcrook)]

After some messing around I found that an issue related to the network configuration was not starting the eth0 interface and thus causing the LDAP problem. It still does not bode well as now I need to reconfigure both the network and LDAP so as to prevent the issue from occurring when my laptop is not connected to any network.

Randall.

[John Affleck (jraffleck)]

So after messing around with this some more, I've given up. I cannot boot without going through single-user mode and removing the ldap references in nsswitch.conf. After doing that, I need to add them back in to be able to access the accounts. Note that 'id <userid>' works fine after adding the ldap entries back in to nsswitch.conf at multi-user time, so it's not an obvious ldap config issue (I did move the server URI to ip as opposed to hostname and fixed up the ldap.conf file, which I've attached)

Is there any way to debug this further ? Should I open another bug ?

[Tony Gambone (tonygambone)]

I had this issue, but realized that the network was not coming up automatically. In /etc/network/interfaces, there was a line erroneously commented out, like this:

auto eth0
# iface eth0 inet dhcp

Not sure why, or how, it ended up that way, since it worked fine before the Gutsy upgrade; but uncommenting that line fixed the problem.

Note: had to do Alt+SysRq+E to be allowed to log in.

[John Affleck (jraffleck)]

Ah. So what confused me was that what used to be eth0 is now eth1. After fixing interfaces to refer to eth1, I can now boot and log in. Thanks!

[Alexander Nofftz (alexnofftz)]

I few days ago the problem occurs again, now at starting Samba daemons. I changed in /etc/nsswitch.conf the lines from "files ldap" to "compat" and everything works fine. So I still think that this is a timeout problem on LDAP.

[Ashley Hooper (ash-hooper)]

I have the same problem here, on a server install of Hardy alpha. I don't run LDAP. I have commented out my ethernet interface in /etc/network/interfaces, as I typically only use my wireless card.

[Pierre Wielders (pierre-wielders)]

I have the same problem but if I move the slapd server before the kernel logger, as Alexander Nofftz suggests in his first response, the problem is solved.

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in openldap2.

[Brian Murray (brian-murray)]

Reviewing this bug report and its comments it seems that multiple people are experiencing this problem. Subsequently, I am confirming this bug report. For future reference you can manage the status of bug reports by clicking on the current status in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/Bugs/Status .

[Jamie Strandboge (jdstrand)]

This is likely a duplicate of https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/155947.