eth0 not coming up after reboot

[Bissig]

Hi there,

apparently our server rebooted itself tonight, and upon reboot the network interfaces did not come up again.

This is the config file /etc/network/interfaces:

Code Select Expand


# The loopback network interface
auto lo                         
iface lo inet loopback         

# The primary network interface
auto eth0                     
iface eth0 inet static         
        address 66.197.220.238
        netmask 255.255.255.192
        network 66.197.220.192
        broadcast 66.197.220.255
        gateway 66.197.220.193 
        # dns-* options are implemented by the resolvconf package, if installed
        dns-nameservers 4.2.2.1                                               
        dns-search volumedrive.com


Is something wrong here? Strangely enough the localhost interface doesn't come up either.

[Archangel]

check /etc/init.d/networking, perhaps it lost execution bit?

[Bissig]

Thanks for the suggestion, execute bit is set though:

Code Select Expand


-rwxr-xr-x 1 root root 1.7K 2006-11-27 08:32 /etc/init.d/networking


[blowFish]

Is it comming up at init lvl 3?

if you switch to init 3 ( #telinit 3 ) does the interface come up?

[Syntac]

This happened to my Arch installation a few months ago. It fixed itself after I did a few reboots. (Probably not going to work here, but what the hell.)

[gimhael]

I'd try to start the interfaces manually with ifup lo && ifup eth0, to verify that the /etc/network/interfaces file is correct.
If that works I'd check that the /etc/init.d/networking is executable and symlinked from the /etc/rc?.d directories.

[Caveman]

Wasn't /etc/network/interfaces declared deprecated in favor of (not sure, can't look it up atm) /etc/default/config?
Nothing really is known as there are too many linux flavor out there .)

[Urcscumug]

Depends on the distribution.

The first place I'd look is in the output of `dmesg`. There's bound to be some related error message somewhere around there. Redirect it to a file (dmesg > dmesg.txt) or examine it with less (dmesg|less).

[Bissig]

Real problem is I do not have a remote kvm or similar. So everytime I would attempt to reboot I have to bother the DCs support to jump in and use SSH to restart netconfig manually. Also, of course, rebooting a server that is used 24/7 isn't fun either.

[Archangel]

KVM-Over-IP rent is typically cheap for an hour or so -- maybe even free. LayeredTech gave me one for ~6 hours for free once.