Your message dated Fri, 17 Jul 2015 19:31:21 +1000
with message-id <1587785.CcY8aTOP3K@deblab>
and subject line Done: ifupdown don't wait for bonding goes up before exiting,
causing other services depending on to fail starting
has caused the Debian Bug report #609242,
regarding ifupdown don't wait for bonding goes up before exiting, causing other
services depending on $network to fail starting
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
609242: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609242
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifenslave-2.6
Version: 1.1.0-17
Severity: grave
Tags: squeeze
Hi,
I encounter a serious issue on a Dell R310 server with its both NICs bonded the
Debian way :
* Hardware details for NICs :
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit
Ethernet (rev 20)
02:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 Gigabit
Ethernet (rev 20)
* Running Kernel :
ii linux-headers-2.6.32-5-amd64 2.6.32-29 Header
files for Linux 2.6.32-5-amd64
ii linux-headers-2.6.32-5-common 2.6.32-29 Common
header files for Linux 2.6.32-5
ii firmware-bnx2 0.27 Binary
firmware for Broadcom NetXtremeII
auto bond0
iface bond0 inet static
slaves eth0 eth1
bond_mode 802.3ad
bond_xmit_hash_policy layer2+3
bond_miimon 100
bond_downdelay 5000
bond_updelay 10000
address 192.168.1.10
netmask 255.255.255.0
gateway 192.168.1.254
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 !
Regards,
--
Eric
-- System Information:
Debian Release: squeeze/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-5-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages ifenslave-2.6 depends on:
ii iproute 20100519-3 networking and traffic control too
ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib
Versions of packages ifenslave-2.6 recommends:
ii net-tools 1.60-23 The NET-3 networking toolkit
ifenslave-2.6 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Package: ifenslave-2.6
Version: 2.7
I believe this old bug is no longer relevant so I'm closing it.
If this problem still exist please report it against current version of
"ifenslave".
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
--
Best wishes,
Dmitry Smirnov
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
