[ale] total server wierdness

[JD]

I suppose NetworkManager has some use and some day I hope to discover it.
Until then, purging that package is the 2nd thing I do (after purging nano).

Manual control of wifi with wicd-curses is easier than trying to troubleshoot
NM, IMHO. For wired connections - edit the interfaces file and be done.

On 11/16/2014 09:39 AM, Vernard Martin wrote:
> 
> On 11/15/2014 05:36 PM, Jim Kinney wrote:
>> A CentOS 6.6 system decided that the network setup was to be ignored. A single
>> nic that was configured for static IP went bozo and switched itself into DHCP
>> mode. The configuration was still static IP. It even showed it was checking
>> for the static IP being in use before it finalized the setup and reported it
>> was all OK. Then it goes and gets an IP address from itself since it's the
>> DHCP server.
>>
>> There are 2 other nic and they had no problems. The problem nic is a 10G card
>> and the other 2 are motherboard 1G.
>>
>> It was working without any issues for a year in this configuration. The last
>> change was to add an Ubuntu 14.04 TFTP bootable kernel to the TFT server and
>> menu for PXE booting new server configs.
>>
>> Anyone seen anything like this before?
>>
> Yup. Had almost that exact situation happen to me a few days ago. Someone
> installed a software package that had NetworkManager in its dependency chain. 
> After the install and subsequent reboot, NetworkManager tried to take control
> over everything and horked everything up.
>