eth0 init failed because dhcbdb not running
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| network-manager (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
Since I upgrade to gutsy I see these messages in syslog in a boot phase:
Dec 13 20:57:09 home NetworkManager: <info> SWITCH: no current connection, found better connection 'eth0'.
Dec 13 20:57:09 home NetworkManager: <WARN> nm_dhcp_
Dec 13 20:57:09 home NetworkManager: <info> Will activate connection 'eth0'.
Dec 13 20:57:09 home NetworkManager: <info> Device eth0 activation scheduled...
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) started...
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled...
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) started...
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) scheduled...
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare) complete.
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) starting...
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) successful.
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled.
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 2 of 5 (Device Configure) complete.
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) started...
Dec 13 20:57:09 home NetworkManager: <WARN> nm_dhcp_
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) failure scheduled...
Dec 13 20:57:09 home NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP Configure Start) complete.
Dec 13 20:57:10 home NetworkManager: <info> Activation (eth0) failed.
Dec 13 20:57:10 home NetworkManager: <info> Deactivating device eth0.
I get plenty of these until rc2.d/S24dhcbdb is started. Then it manages to get the host network information with dhcp.
I noticed that amavis doesn't get started with the consequence that all incoming mails get blocked in queues by postfix.
Although it is there as rc2.d/S19amavis
Checking the logs, I saw these series of messages. I get 100 of them in one boot. Restarting amavis by hand resolves the amavis problem.
Is this dependency to dhcbdb normal ? Is this the reason amavis is not running when the boot completes ?
| description: | updated |
| ChM (christophe-meessen) wrote | #1 |
| ChM (christophe-meessen) wrote | #2 |
| Alexander Sack (asac) wrote | #3 |
| Changed in network-manager: | |
| status: | New → Invalid |
Changing dhcbdb daemon startup order solved the amavis-
It changed it to rc2.d/S24dhcbdb.
I have another ubuntu computer but it doesn't use dhcp, so no problem.
It also has rc2.d/S24dhcbdb