Please run the following command using one of the IPs your machine keeps losing as the IP# in the command:
Code:
egrep IP# /var/log/messages
If you have avahi improperly configured and running on your machine, it will withdraw the IPs on running either a) a reboot, or b) a network restart, so you'll see lines like the following in /var/log/messages for that IP:
Code:
Jul 4 02:45:41 server avahi-daemon[415]: Registering new address record for IP# on eth0.
Jul 4 02:45:42 server avahi-daemon[415]: Withdrawing address record for IP# on eth0.
Jul 4 02:54:45 server avahi-daemon[415]: Registering new address record for IP# on eth0.
Jul 4 02:56:14 server named[486]: no longer listening on IP#53
Jul 4 02:56:14 server named[644]: listening on IPv4 interface eth0:1, IP#53
Next, when you ps aux|grep for it, you'll see these type of processes:
Code:
# ps aux|grep avahi
avahi 415 0.0 0.0 2172 1412 ? Ss 02:45 0:00 avahi-daemon: running
avahi 417 0.0 0.0 2148 336 ? Ss 02:45 0:00 avahi-daemon: chroot helper
If you do see this type of information, then please contact your datacenter to have them either stop avahi or properly register your IPs in avahi for these to be recognized. That service is what is causing the issue to occur.
Until the issue is fixed by your datacenter, service provider or NOC, you can run
/etc/init.d/ipaliases restart to get the IPs back in the list. An ipaliases restart will bring back any missing IPs without removing and re-adding them. Unfortunately, avahi will withdraw them again on network restart (/etc/init.d/network restart) or server reboot.
