ONBOOT=yes but eth0 doesn't stay up after reboot

anon091 · 11-21-2013, 05:25 AM

Hi guys. Have a RHEL server 2.6.18-164.9.1.el5xen that in /etc/sysconfig/network-scripts it has ONBOOT=yes. If I run a constant ping to the server while it's restarting, the interface comes up briefly (assuming when it initially up's eth0), then dies about the time the login prompt appears.
If I do a ifup eth0 that brings it up, but I'm not sure how to tell why the onboot isn't working/staying up.
Any ideas where I should start?

SAbhi · 11-21-2013, 10:21 PM

not sure but is your network manager running ?

sachin.davra · 11-22-2013, 12:36 AM

Post your /etc/sysconfig/network-scripts/ifconfig-eth0. content

anon091 · 11-22-2013, 08:12 AM

How do I tell if that's running at startup?

Here's the contents of ifcfg-eth0, with the personal info changed. does ONBOOT need to be higher in the file or something? or is there a command to run to have the system verify it's reading the file correctly?

# Broadcom Corporation NetXtreme II BCM5708 Gigabit Ethernet
DEVICE=eth0
BOOTPROTO=static
BROADCAST=1.2.3.4
HWADDR=00:00:00:00:00:00
IPADDR=1.2.3.5
IPV6ADDR=
IPV6PREFIX=
NETMASK=255.255.254.0
NETWORK=1.2.3.0
ONBOOT=yes

lleb · 11-22-2013, 09:06 AM

Quote:

NM_CONTROLLED=answer
where answer is one of the following:
yes — NetworkManager is permitted to configure this device. This is the default behavior and can be omitted.
no — NetworkManager is not permitted to configure this device.

add the

Code:

NM_CONTROLLED=no

in there. that way even if the network manager is running, it will be ignored for this device.

https://access.redhat.com/site/docum...nterfaces.html

anon091 · 11-22-2013, 09:17 AM

OK, I won't be able to reboot and test the server for a while, but I will try this next time I get a chance. is there like a chkconfig or something I should also look at to see if network manager runs or not?

r41d3n · 11-22-2013, 10:05 AM

If you don't use network-manager, just remove it.

anon091 · 11-22-2013, 11:25 AM

I can't say I've ever used it on this server, but this server has been in operation since before my time here.

lleb · 11-22-2013, 06:22 PM

to be blunt the network manager is horrid when dealing with static IPs. id remove it.

SAbhi · 11-24-2013, 08:24 PM

Thats correct if you dont use NM then remove it... or say a "no" to it in config.

anon091 · 11-25-2013, 09:32 AM

next time I get an opportunity to restart it, I will try this. but how do I actually tell if it's installed or if it's even running?

r41d3n · 11-25-2013, 01:55 PM

Post the output of:

Code:

rpm -qa | grep -i manager

This will tell if the package is installed on the system.

I think the package name is NetworkManager. You can use the following commands to see if it's running:

Code:

pstree

or

Code:

ps aux | grep -i network

If NetworkManager shows in these command's output, then it is running.

SAbhi · 11-25-2013, 07:54 PM

Code:

rpm -qa | grep NetworkManager or grep -i networkmanager

will give you the installed details of this package. you can then remove it by "rpm -e [package name]". Before removing make sure no other program on your box depends on NM services.
EDIT:
you can check its status by

Code:

"service NetworkManager status"

anon091 · 11-26-2013, 10:13 AM

rpm -qa | grep NetworkManager says that I have:

NetworkManager-gnome-0.7.0-9.el5
NetworkManager-glib-0.7.0-9.el5
NetworkManager-0.7.0-9.el5

service NetworkManager status says: "NetworkManager is stopped"

ps aux | grep -i network only shows me my grep command.

but how do I tell if anything would ever need/use NetworkManager.

SAbhi · 11-26-2013, 08:38 PM

hmm no issue:
It is possible that because NM is Disabled no service is taking control of network.
can you just fetch me these:

Code:

chkconfig --list | grep network

if it wasnt on at required runlevels :

Code:

chkconfig network on
service network start

hope above should be good to fix it, if not we will see other options.

Code:

cat /etc/sysconfig/network

EDT:

dmesg | grep eth0