IP Alias removed when Login Screen appears?

[Paul Andringa]

Hi,

I have added 2 Aliases to my eth0 and these are coming up fine till the server gets to the login screen for Default System Session.

After many hours of confusion why it did not activate I found that they do acticate by SSH on to the server but they get deactivated when the server gets to the Fedora Windows logon screen.

Any ideas will be much appreciated.

FYI I have created:

ifcfg-eth0:1

DEVICE=eth0:1
BOOTPROTO=static
ONBOOT=yes
NETMASK=255.255.255.0
IPADDR=192.168.100.100

ifcfg-eth0:2

DEVICE=eth0:2
BOOTPROTO=static
ONBOOT=yes
NETMASK=255.255.255.0
IPADDR=192.168.100.101

In the /etc/sysconfig/network-scripts directory

Please help as this is holding up the server from going to the Data Centre!

Thanks,

Paul

[AndyGreen]

What does ifconfig -a say after you reach the login screen? Both aliases are down at that point, or just :1? If they are both actually up according to ifconfig even after the login screen, maybe route would be interesting.

[Paul Andringa]

Thanks Andy, both are down, it does not show them at all.

However since I removed Xwindows from the startup (thank you :-)) it does not remove it anymore?

I can now login, start Xwindows and the aliases remain? I am stunned!

Paul

[AndyGreen]

Aha! Sounds like one of the services started in runlevel 5 (X), not started in runlevel 3 (text mode login) is to blame then!

chkconfig --list | grep 3:off | grep 5:on

will tell you the possibles for the evil service!

--edit

You can then

service nameofservice start

each listed service in turn by hand until your network blows up -- then you know which service causes the disaster and we can look further.

Actually.... maybe you accidentally configured it to turn something vital OFF in runlevel 5, like service network.

chkconfig --list | grep 3:on | grep 5:off

will list the things turned OFF in runlevel 5 that are on in runlevel 3.

[Paul Andringa]

Aha!

readahead 0:off 1:off 2:off 3:off 4:off 5:on 6:off
vsftpd 0:off 1:off 2:off 3:off 4:off 5:on 6:off
readahead_early 0:off 1:off 2:off 3:off 4:off 5:on 6:off
NetworkManager 0:off 1:off 2:off 3:off 4:off 5:on 6:off

Seems NetworkManager is to blame then?

Paul

[AndyGreen]

Aiee! Network Mangler is EVIL! Exorcise the demon!

chkconfig NetworkManager off
service NetworkManager stop
rpm -e NetworkManager

[Paul Andringa]

Shreek!!

Demon Exorcised! Machine has redeemed itself (and so have I)

Thanks for all the help Andy, I will drop you a line to discuss a 'Health Check' once in DC if you don't mind!

Paul

[AndyGreen]

Feel free, glad you're up.