After properly Bonding network interfaces on SUSe 9 Support Pack 2 errors are seen on boot up. On boot up these error messages are logged

(Last modified: 05Oct2005)

This document (10099181) is provided subject to the disclaimer at the end of this document.

fact

SUSE LINUX Enterprise Server 9 Support Pack 2

Bonding Network Interfaces

Something broke getting the master's IP address: Cannot assign requested address.

Something broke getting the master's destination address: Cannot assign requested address.

Something broke getting the master's broadcast address: Cannot assign requested address.

Something broke getting the master's netmask: Cannot assign requested address.

/bin/logger: invalid option -- e
usage: logger [-is] [-f file] [-p pri] [-t tag] [-u socket] [ message ... ]

failedSetting up service
network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .done

symptom

After properly Bonding network interfaces on SUSe 9 Support Pack 2 errors are seen on boot up.

On boot up these error messages are logged in the /var/log/messages file as well as being displayed on the screen.

Jul 15 18:45:32 bl10 ifup: Something broke getting the master's IP address: Cannot assign requested address.
Jul 15 18:45:32 bl10 ifup: Something broke getting the master's destination address: Cannot assign requested address.
Jul 15 18:45:32 bl10 ifup: Something broke getting the master's broadcast address: Cannot assign requested address.
Jul 15 18:45:32 bl10 ifup: Something broke getting the master's netmask: Cannot assign requested address.

Here is what is logged in the Boot.msg file:
bond0     enslaving interfaces:  eth2 eth4
/bin/logger: invalid option -- e
usage: logger [-is] [-f file] [-p pri] [-t tag] [-u socket] [ message ... ]
bond0     -e Bonding interface 'bond0' could not be set up correctly eth2 is already a slave failed   bond1   
bond1     enslaving interfaces:  eth3 eth5
/bin/logger: invalid option -- e
usage: logger [-is] [-f file] [-p pri] [-t tag] [-u socket] [ message ... ]
bond1     -e Bonding interface 'bond1' could not be set up correctly
Something broke getting the master's IP address: Cannot assign requested address.
Something broke getting the master's destination address: Cannot assign requested address.
Something broke getting the master's broadcast address: Cannot assign requested address.
Something broke getting the master's netmask: Cannot assign requested address.
eth3 is already a slave
failedSetting up service
network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .done
<notice>exit status of (network) is (0)

fix

While these error messages make it sound like Bonding did not work and the network will not be available, in fact Bonding did work the first time it is called and failed the second time.  The end result is that you see error messages that are disconcerting but everything still works.

Getting rid of the error messages required two modules to be changed because there are really two issues here.

1)  The logger -e  invalid option has been taken care of in sysconfig.rpm.

2) The "Somthing broke" error messages are caused by ifup being called twice at the same time.  One of those times was from the hotplug net.agent.  The code will now skip bonding interfaces in net.agent.  This defect was fixed in hotplug.rpm

Both of these fixes will be available in SP3.

document

Document Title: After properly Bonding network interfaces on SUSe 9 Support Pack 2 errors are seen on boot up.

On boot up these error messages are logged in the /var/log/messages file as well as being displayed on the screen.

Jul 15 18:45:32 bl10 ifup: Something broke getting the master's IP address: Cannot assign requested address.
Jul 15 18:45:32 bl10 ifup: Something broke getting the master's destination address: Cannot assign requested address.
Jul 15 18:45:32 bl10 ifup: Something broke getting the master's broadcast address: Cannot assign requested address.
Jul 15 18:45:32 bl10 ifup: Something broke getting the master's netmask: Cannot assign requested address.

Here is what is logged in the Boot.msg file:
bond0     enslaving interfaces:  eth2 eth4
/bin/logger: invalid option -- e
usage: logger [-is] [-f file] [-p pri] [-t tag] [-u socket] [ message ... ]
bond0     -e Bonding interface 'bond0' could not be set up correctly eth2 is already a slave failed   bond1   
bond1     enslaving interfaces:  eth3 eth5
/bin/logger: invalid option -- e
usage: logger [-is] [-f file] [-p pri] [-t tag] [-u socket] [ message ... ]
bond1     -e Bonding interface 'bond1' could not be set up correctly
Something broke getting the master's IP address: Cannot assign requested address.
Something broke getting the master's destination address: Cannot assign requested address.
Something broke getting the master's broadcast address: Cannot assign requested address.
Something broke getting the master's netmask: Cannot assign requested address.
eth3 is already a slave
failedSetting up service
network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .  .done
<notice>exit status of (network) is (0)

Document ID: 10099181
Solution ID: NOVL103732
Creation Date: 05Oct2005
Modified Date: 05Oct2005
Novell Product Class:COMM/NFS

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.