[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] total server wierdness
- Subject: [ale] total server wierdness
- From: vernard at gmail.com (Vernard Martin)
- Date: Sun, 16 Nov 2014 09:39:27 -0500
- In-reply-to: <CAEo=5Px6FMvi_Wa3o2mqNQk7v3r=F7Bm-Y91Bs4Z+JnHrBfgzA@mail.gmail.com>
- References: <CAEo=5Px6FMvi_Wa3o2mqNQk7v3r=F7Bm-Y91Bs4Z+JnHrBfgzA@mail.gmail.com>
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.
Vernard