user release.debian....@packages.debian.org
usertag 609242 squeeze-can-defer
tag 609242 squeeze-ignore
kthxbye

On Fri, Jan  7, 2011 at 18:39:53 +0100, Eric Belhomme wrote:

> As said in the subject, ifupdown exits before the bond interface is active. I 
> tried to raise the updelay to get the slaves active but it has no effect :
> 
> [   11.426497] bnx2: eth0 NIC Copper Link is Up, 1000 Mbps full duplex
> [   11.478596] bonding: bond0: link status up for interface eth0, enabling it 
> in 0 ms.
> [   11.486325] bonding: bond0: link status definitely up for interface eth0.
> [   11.493738] ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
> [   11.515333] bnx2: eth1 NIC Copper Link is Up, 1000 Mbps full duplex
> [   11.590403] bonding: bond0: link status up for interface eth1, enabling it 
> in 10000 ms.
> Starting LDAP connection daemon: nslcd[   21.581245] bonding: bond0: link 
> status definitely up for interface eth1.
> nslcd: failed to bind to LDAP server ldaps://ldap.eve/: Can't contact LDAP 
> server: Connection timed out
> nslcd: no available LDAP server found
> nslcd: no base defined in config and couldn't get one from server
>  failed!
> 
> You can see on this log that sysv-rc tries to start nslcd daemon *before* 
> bonding module reports bond0 to be effectively up, causing nslcd to fail to 
> start... As everything on my setup relies on LDAP for auth, nothing is 
> working until I locally log as root to manually restart failed services...
> 
> I'm not sure id I should assign this bug to ifenslave or to ifupdown package, 
> so sorry for the noise if I'm wrong !
> 
Considering that this doesn't sound like a new bug, you have a
workaround (if hacky) and this hopefully won't affect too many people,
I'm tagging this as not a blocker for the squeeze release.  If a fix is
available later it can be applied in a point release.

Cheers,
Julien

Attachment: signature.asc
Description: Digital signature

Reply via email to