[BlueOnyx:17757] Re: new server setup

[Michael Stauber]

Hi Matthew,

> I'm having the exact same experience as described in this thread.

Ok, here is what I did:

Original situation:

An unwanted IP was assigned to eth0 (for simplicity lets say it was
10.0.0.2). All Vsites were supposed to be running on 10.0.0.1 and
ideally 10.0.0.1 was supposed to be the only IP of the box.

/sbin/ifconfig reported:

eth0 		10.0.0.2
eth0:0		10.0.0.1

Tries to change this in the GUI under "System Settings" / "TCP/IP"
raised the error message that the IP wasn't unique or similar and
10.0.0.2 couldn't be changed to 10.0.0.1.

Fix:

Edit /etc/sysconfig/network-scripts/ifcfg-eth0 and
/etc/sysconfig/network-scripts/ifcfg-eth0:0 and change the IPs.

In /etc/sysconfig/network-scripts/ifcfg-eth0:

Change 10.0.0.2 to 10.0.0.1

In /etc/sysconfig/network-scripts/ifcfg-eth0:0:

Change 10.0.0.1 to 10.0.0.2

If you really want to free up the IP bound to eth0:0 right away, then
you can safely delete /etc/sysconfig/network-scripts/ifcfg-eth0:0: -
provided no more Vsites are using it.

Then reboot. It's possible to shake this loose without reboot, but
especially if the box is remotely hosted the reboot is the safer
alternative.

Once rebooted ifconfig will report:

eth0 		10.0.0.1
eth0:0		10.0.0.2 (if you didn't delete the file)

That will allow you to disable and remove 10.0.0.2 via the Aliases in
the GUI, provided no more Vsites are using it.

-- 
With best regards

Michael Stauber