Unable to resolve localhost

Shawn Kovalchick bamapookie at gmail.com
Tue Nov 2 03:16:01 UTC 2004


The thing is, I can ping localhost.  Nothing else has a problem
talking to localhost, it's just postgresql.  It has the same setup
files as a separate installation on my home Gentoo box, which works
fine.


On Mon, 01 Nov 2004 20:44:08 -0600, Micheal <sundance at sundanceloki.com> wrote:
> On Mon, 2004-11-01 at 20:29, Shawn Kovalchick wrote:
> 
> 
> > ifconfig lo
> > lo        Link encap:Local Loopback
> >           inet addr:127.0.0.1  Mask:255.0.0.0
> >           inet6 addr: ::1/128 Scope:Host
> >           UP LOOPBACK RUNNING  MTU:16436  Metric:1
> >           RX packets:2503 errors:0 dropped:0 overruns:0 frame:0
> >           TX packets:2503 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:0
> >           RX bytes:2402682 (2.2 Mb)  TX bytes:2402682 (2.2 Mb)
> >
> > On Mon, 01 Nov 2004 20:23:30 -0600, Micheal <sundance at sundanceloki.com> wrote:
> > > On Mon, 2004-11-01 at 20:17, Shawn Kovalchick wrote:
> > >
> > >
> > > > I'm trying to set up a postgresql server on FC2, and it seems that the server
> > > > is unable to look up 127.0.0.1.  Further investigation shows that dig
> > > > is unable to return anything for localhost or a reverse lookup for
> > > > 127.0.0.1.  /etc/hosts has an entry for 127.0.0.1 pointing to
> > > > localhost and localhost.localdomain.  Am I missing something?
> > > >
> > > > Relevant sections of configuration files follow:
> > > >
> > > > /etc/nsswitch.conf contains this line:
> > > > hosts:      files dns
> > > >
> > > > /etc/hosts contains:
> > > > 127.0.0.1  localhost  localhost.localdomain
> > > >
> > > > I apologize if this has been double posted, it appears that the
> > > > initial post didn't take, as I was not yet signed up on the list.
> > >
> > > What does the out put of
> > >
> > > /sbin/ifconfig lo
> > >
> > > give?
> > >
> > > MC
> > >
> > >
> >
> 
> Thats tough. Nothing wrong with hosts or nsswitch.conf. If you can't
> ping localhost. I would check your iptables and/or your postrgresql
> configuration.  Other than that, thats all I can suggest for now.
> 
> MC
> 
>




More information about the fedora-list mailing list