CentOS

Hello all,
This is my first post on this forum, I am doing it as I could not find a similar issue already discussed.

Here is the problem :
My system is running Centos 5.7
First, the network configuration configuration works fine with a static IP adress
The server is then moved to a new environment (without changing the configuration) and after one day, the ethernet interface goes down

After investigation, the following changes occured :
The network configuration changes (BOOTPROTO from static to none)

When I change back the BOOTPROTO to static and restart the network (service network restart), I am overwhemed by the following error :
cannot open font file latarcyrheb-sun16
I looked for the /lib/kbd/consolefonts directory (containing the fonts), and it is simply not there...

Many questions :
How is the system font related to restarting the network configuration ?
Why does the /lib/kbd/consolefonts directory disappear ?
Why does the server network configuration change when the server is installed in a new network ?

Thank you in advance

Moussafir

Config files don't change themselves.
Here are two possibilities.
1. You have duplicate IP addresses in your network, and you aren't looking at the machine you think you are looking at.
2. Since you are running an old, insecure version of CentOS 5 with manny open attack vectors, you have been hacked and need to install from scratch.
This time use 5.10 or 6.5.

Thank you for your response.
Unfortunately, I don't think either of the two options are valid.
1. I connected physically (screen and keyboard) to the server, so there is no possible doubt
2. The server is completely immune to any outside attack since it is only accessible from the private LAN only with no internet connection

I did however find out that the network could be automatically modified by the system.
In the discussion below, ifcfg-ethN files were created automatically
viewtopic.php?f=22&t=46066

I am searching what script/daemon created/modifies these files

Regards

Err, that link is your own thread...

Oops, sorry, this is the link to the right thread :
viewtopic.php?t=27165

That's for CentOS 5 which had a service called kudzu which used to detect hardware changes. It no longer exists in CentOS 6 and would not be responsible for making the changes.