Network Interface Configuration File Re-written

carlosinfl · 02-20-2011, 07:26 PM

This past Friday as I was performing regular maintenance on my RHEL / CentOS servers, I ran yum upgrades on them and when they rebooted, I realized there were network issues and I could not longer access them via Ping or SSH. When I jumped on the console, I realized that it created a new 'ifcfg-eth0' file with none of my static information & the old 'ifcfg-eth0' file with all my static info had been renamed to 'ifcfg-eth0.bak'.

It appears that the MAC address on the new file and the old .bak file are different and I have no idea why. I have no changed or altered anything on the server.

Anyone know what could have caused this?

corp769 · 02-20-2011, 07:36 PM

Do you remember what packages all got updated?

carlosinfl · 02-20-2011, 07:53 PM

Sadly I do not. I'm sure I can check /var/log for a list but I'm just wondering what would cause this...

corp769 · 02-20-2011, 08:07 PM

Honestly, that would actually depend on what packages got updated, so we could know what all got modified. Could you post your /var/log/messages output from the day you updated?

carlosinfl · 02-21-2011, 09:03 PM

Code:

Feb 18 16:05:40 mail yum: Updated: clamav-db-0.97-1.el5.rf.x86_64
Feb 18 16:05:42 mail yum: Updated: clamav-0.97-1.el5.rf.x86_64
Feb 18 16:05:44 mail yum: Updated: kernel-headers-2.6.18-194.32.1.el5.x86_64
Feb 18 16:05:45 mail yum: Updated: clamd-0.97-1.el5.rf.x86_64
Feb 18 16:05:45 mail yum: Updated: unrar-4.0.6-1.el5.rf.x86_64
Feb 18 16:05:45 mail yum: Updated: perl-version-0.88-1.el5.rf.x86_64
Feb 18 16:06:01 mail yum: Installed: kernel-2.6.18-194.32.1.el5.x86_64
Feb 18 16:06:01 mail yum: Updated: perl-Compress-Raw-Bzip2-2.033-1.el5.rf.x86_64
Feb 18 16:06:02 mail yum: Updated: clamav-devel-0.97-1.el5.rf.x86_64
Feb 18 16:06:02 mail yum: Updated: perl-Digest-SHA-5.50-1.el5.rf.x86_64
Feb 18 16:06:02 mail yum: Updated: perl-Compress-Raw-Zlib-2.033-1.el5.rf.x86_64

corp769 · 02-21-2011, 09:15 PM

Hmm, nothing looks odd enough to do that, except maybe the updated kernel... If I were you, I would copy ifcfg-eth0.bak to ifcfg-eth0. I think you would be safe to do so. Make sure to update that brand new ifcfg-eth0 file just incase....

And lastly, could you pastebin ifcfg-eth0 and ifcfg-eth0.bak?