On 4/25/2010 3:09 PM, Hans Witvliet wrote:
On Sun, 2010-04-25 at 13:47 -0700, Marc Chamberlin wrote:
I have a system acting as a gateway for my SOHO network, running openSuSE11.2 x86_64 which as two different NICs installed. eth0 is my external network interface and eth1 is my internal network interface. Both are configured to initialize during boot up and I use the traditional ifup/ifdown method of controlling my network. eth0 will set up just fine during boot up and be fully functional by the time the KDE desktop is up an running. But eth1 is taking several minutes (from after the KDE desktop is up and running) before it comes online. This temporarily breaks several services such as Named, DHCP, James (my email server), though when eth1 finally gets up an running these services do start up automatically as well. BUT this also causes problems on other computers on my internal network... What is worse however is that I mount several remote disk directories from fstab and these mounts do NOT automatically establish themselves until I manually do a mount -a as superuser on this gateway/server. And that breaks other services such as vsftp and bacula. This is a serious problem for me, as this system MUST be able to reboot and come up ok with all these services running without my attendance. (I run this system remotely and use a crude means of keeping the system working, i.e. I use a device called iBoot which will power cycle any computer which stops responding to pings from it... hence the reason it must be able to reboot without my attendance...)
So how do I debug and fix this slow startup of eth1? I would really prefer to fix this issue and not find/use workarounds.. Any help offered sure will be appreciated, I am stuck and have ran out of ideas myself...
Marc...
Hi Marc,
You should have a look at the file: /etc/sysconfig/network/config
here are two fields you must change: MANDATORY_DEVICES="" and WAIT_FOR_INTERFACES="30"
By default, the system iniializes, but waits no longer for any device more than 30 seconds. For several systems i had to raise it to 90 seconds or even higher.... (ymmv) And as shown, the field for mandatory devices is empty.
In case your system acts as nfs/dhcp/ldap/what-ever-server, the startup of those services could happen before your network is up, with all kinds of unpredictable concequences.
So make it both eth0 and eth1 mandatory, and increase the timeout.
hw
Thanks Hans for your reply and thoughts... I tried to do as you suggested, but no joy! The eth1 interface remains slow to initialize... So do you or anyone else have any suggestions I might try? Thanks again in advance... Marc..