On Wed, 5 Mar 2008, Buchan Milne wrote:
On Wednesday 05 March 2008 19:54:03 Guennadi Liakhovetski wrote:
So far my main problem is not delays in the bootup but failing services. like avahi-daemon, NetworkManager, gpm, etc.
I've never seen this, although my laptop has no real local user accounts (system accounts are local, but my user is not), and runs its only ldap server locally (which starts after all the usual problematic services such as udev, haldaemon etc.).
Are you running nscd ? Does nscd start before LDAP is accessible?
No, no nscd. And the LDAP server is accessible from the start.
Do you have an error message that occurs in this case?
Here are some:
avahi-daemon[2220]: dbus_bus_get(): Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. avahi-daemon[2220]: WARNING: Failed to contact D-Bus daemon. NetworkManager: <information>^IDevice 'eth0' DHCP transaction took too long (>45s), stopping it. NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) scheduled... NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) started... NetworkManager: <information>^INo DHCP reply received. Automatically obtaining IP via Zeroconf. NetworkManager: <information>^Iautoip: Sending probe #0 for IP address 169.254.240.235. NetworkManager: <information>^Iautoip: Waiting for reply... NetworkManager: <information>^Iautoip: Sending probe #1 for IP address 169.254.240.235. NetworkManager: <information>^Iautoip: Waiting for reply... NetworkManager: <information>^Iautoip: Sending probe #2 for IP address 169.254.240.235. NetworkManager: <information>^Iautoip: Waiting for reply... NetworkManager: <information>^Iautoip: Sending announce #0 for IP address 169.254.240.235. NetworkManager: <information>^Iautoip: Waiting for reply... NetworkManager: <information>^Iautoip: Sending announce #1 for IP address 169.254.240.235. NetworkManager: <information>^Iautoip: Waiting for reply... NetworkManager: <information>^Iautoip: Sending announce #2 for IP address 169.254.240.235. NetworkManager: <information>^Iautoip: Waiting for reply... NetworkManager: <information>^IActivation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... NetworkManager: <information>^IActivation (eth0) Stage 4 of 5 (IP Configure Timeout) complete.
Are they failing because SASL is not configured?
This has nothing to do with SASL.
Good to know!
How should it work? Should all those services indeed contact the LDAP server? and get replies from it? Like what - user avahi unknown or what?
Thanks for the help so far! Guennadi --- Guennadi Liakhovetski