Is there any reason why /etc/hosts would be missing the line, 127.0.0.1 localhost?
I just spent an hour trying to figure out why I could not connect to postgresql using ``psql -h ...'', finally figuring out that the /etc/hosts file was the problem.
Bill
On Mon, Jul 21, 2008 at 9:20 PM, Bill Campbell centos@celestial.com wrote:
Is there any reason why /etc/hosts would be missing the line, 127.0.0.1 localhost?
Nope. It's there by default in some form or another.
By default, it usually looks like this ->
127.0.0.1 installname localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6
If you don't have anything like this in your /etc/hosts, you either need to find a mirror and begin yelling at responsible parties, or stalk whomever else has root on this particular machine.
On Mon, Jul 21, 2008, Jim Perrin wrote:
On Mon, Jul 21, 2008 at 9:20 PM, Bill Campbell centos@celestial.com wrote:
Is there any reason why /etc/hosts would be missing the line, 127.0.0.1 localhost?
Nope. It's there by default in some form or another.
By default, it usually looks like this ->
127.0.0.1 installname localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6
If you don't have anything like this in your /etc/hosts, you either need to find a mirror and begin yelling at responsible parties, or stalk whomever else has root on this particular machine.
I guess I could yell at myself as I'm doing kickstart installs from a local mirror.
I found the same thing on two CentOS 5.1 installs here, one on a VMware VM, the other on real iron. The wierd thing is that the base VMware VM I have that I copy to create new VMs looks OK. Now I'm going to have to poke around to see what's causing this line to be deleted.
Bill
Bill Campbell wrote:
On Mon, Jul 21, 2008, Jim Perrin wrote:
On Mon, Jul 21, 2008 at 9:20 PM, Bill Campbell centos@celestial.com wrote:
Is there any reason why /etc/hosts would be missing the line, 127.0.0.1 localhost?
Nope. It's there by default in some form or another.
By default, it usually looks like this ->
127.0.0.1 installname localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6
If you don't have anything like this in your /etc/hosts, you either need to find a mirror and begin yelling at responsible parties, or stalk whomever else has root on this particular machine.
I guess I could yell at myself as I'm doing kickstart installs from a local mirror.
I found the same thing on two CentOS 5.1 installs here, one on a VMware VM, the other on real iron. The wierd thing is that the base VMware VM I have that I copy to create new VMs looks OK. Now I'm going to have to poke around to see what's causing this line to be deleted.
Bill
I had a similar problem using OpenVZ images, installed from kickstart - almost like it's leaving some stuff out by default. So I ended up creating the file manually and adding it to the kickstart file to be copied over.
On Tue, Jul 22, 2008, Rudi Ahlers wrote:
Bill Campbell wrote:
On Mon, Jul 21, 2008, Jim Perrin wrote:
On Mon, Jul 21, 2008 at 9:20 PM, Bill Campbell centos@celestial.com wrote:
Is there any reason why /etc/hosts would be missing the line, 127.0.0.1 localhost?
Nope. It's there by default in some form or another.
By default, it usually looks like this ->
127.0.0.1 installname localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6
If you don't have anything like this in your /etc/hosts, you either need to find a mirror and begin yelling at responsible parties, or stalk whomever else has root on this particular machine.
I guess I could yell at myself as I'm doing kickstart installs from a local mirror.
I found the same thing on two CentOS 5.1 installs here, one on a VMware VM, the other on real iron. The wierd thing is that the base VMware VM I have that I copy to create new VMs looks OK. Now I'm going to have to poke around to see what's causing this line to be deleted.
Bill
I had a similar problem using OpenVZ images, installed from kickstart - almost like it's leaving some stuff out by default. So I ended up creating the file manually and adding it to the kickstart file to be copied over.
The file was OK after the kickstart install, and after a ``yum update''. We install about 240 packages under the OpenPKG portable package management system which may have caused this, but I have not seen this problem prior to CentOS 5.2.
I did not check to see the status of the /etc/hosts file after configuring the network with system-config-network, and before installing OpenPKG and its packages. I may create a new VM, and run through the network configuration etc. to see where this is happening (VMware snapshots and revert sure simplify things like this :-).
Bill
Following up, info below.
On Tue, Jul 22, 2008, Bill Campbell wrote:
On Tue, Jul 22, 2008, Rudi Ahlers wrote:
Bill Campbell wrote:
On Mon, Jul 21, 2008, Jim Perrin wrote:
On Mon, Jul 21, 2008 at 9:20 PM, Bill Campbell centos@celestial.com wrote:
Is there any reason why /etc/hosts would be missing the line, 127.0.0.1 localhost?
Nope. It's there by default in some form or another.
By default, it usually looks like this ->
127.0.0.1 installname localhost.localdomain localhost ::1 localhost6.localdomain6 localhost6
If you don't have anything like this in your /etc/hosts, you either need to find a mirror and begin yelling at responsible parties, or stalk whomever else has root on this particular machine.
I guess I could yell at myself as I'm doing kickstart installs from a local mirror.
I found the same thing on two CentOS 5.1 installs here, one on a VMware VM, the other on real iron. The wierd thing is that the base VMware VM I have that I copy to create new VMs looks OK. Now I'm going to have to poke around to see what's causing this line to be deleted.
Bill
I had a similar problem using OpenVZ images, installed from kickstart - almost like it's leaving some stuff out by default. So I ended up creating the file manually and adding it to the kickstart file to be copied over.
The file was OK after the kickstart install, and after a ``yum update''. We install about 240 packages under the OpenPKG portable package management system which may have caused this, but I have not seen this problem prior to CentOS 5.2.
I did not check to see the status of the /etc/hosts file after configuring the network with system-config-network, and before installing OpenPKG and its packages. I may create a new VM, and run through the network configuration etc. to see where this is happening (VMware snapshots and revert sure simplify things like this :-).
I just did a fresh kickstart install of CentOS 5.2 as a VMware virtual machine, and the 127.0.0.1 localhost line is missing after doing ``yum update'' when I run ``system-config-network'' to assign a static IP address to the new VM.
Bill
Hello, what about your postgresql settings ? are you creating a role for connecting to postgres ? if not creat role:
# /etc/init.d/postgresql restart #su - postgres
(try to connecting here using your command psql -h, if it connects) now, (run command for creating role and setting up priviledges for other users.)
#creatuser -U postgres -P .... ... ... edit the file /var/lib/pgsql/data/pg_hba.conf
and at the last lines it looks like: # TYPE DATABASE USER CIDR-ADDRESS METHOD
# "local" is for Unix domain socket connections only local all all trust # IPv4 local connections: host all all 127.0.0.1/32 trust # IPv6 local connections: host all all ::1/128 ident sameuser
Good Luck
On Tue, Jul 29, 2008, kapil singh wrote:
Hello, what about your postgresql settings ?
There were no problems with the postgresql settings, only that when trying to connect to ``localhost'' it could not resolve that to 127.0.0.1. ``psql -h 127.0.0.1 ...'' worked. After updating the /etc/hosts file to create the ``127.0.0.1 localhost'' line, things work fine.
Bill
-
Bill Campbell -
Jim Perrin -
kapil singh -
nate -
Rudi Ahlers