[BlueOnyx:18432] Re: Hosts changing to localhost.localdomain

Michael Stauber mstauber at blueonyx.it
Sun Sep 27 17:15:23 -05 2015


Hi Colin,

> Yum update has sorted it all out nicely, although one 5106R server has only one 127.0.0.1 entry:
> 
> # Entries for localhost and primary IP address:
> 127.0.0.1               	localhost               	localhost.localdomain
> 192.168.10.130 server5 server5.mainline.co.uk
> 
> All the others have two lines:
> 
> # Entries for localhost and primary IP address:
> 127.0.0.1               	localhost               	localhost.localdomain
> 127.0.0.1               	server6                 	server6.mainline.co.uk
> 192.168.10.135          	server6                 	server6.mainline.co.uk
> 
> Also these are all Aventurin{e} VPS and previously had entries for the vnet:
> 
> 
> # Auto-generated file.  Keep your customizations at the bottom of this file.
> 127.0.0.1		server7.mainline.co.uk server7-venet0.mainline.co.uk server7-venet0
> 127.0.0.9		server7.mainline.co.uk server7-venet0:0.mainline.co.uk server7-venet0:0
> 
> I presume this is not required?

You see the entries below "# Auto-generated file.  Keep your
customizations at the bottom of this file."? You can remove them.

The general format is this:

Under ...
# Entries for localhost and primary IP address:

.. you will always have the 127.0.0.1. Additionally the public IP if one
of the Network interfaces has the "real" flag set to "1". That is
usually the case for eth0, eth1, eth2 (and so on) or venet0:0 in case of
a VPS.

If you only see 127.0.0.1 there, then apparently none of your CODB
Network entries has the "real" flag set to "1". As long as the primary
IP shows up somewhere else in another entry that should still be fine.

-- 
With best regards

Michael Stauber



More information about the Blueonyx mailing list