From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ivan Uemlianin <ivan(at)llaisdy(dot)com> |
Cc: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: connecting from trac: "no route to host" error |
Date: | 2010-05-13 14:47:13 |
Message-ID: | 29490.1273762033@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
Ivan Uemlianin <ivan(at)llaisdy(dot)com> writes:
> could not connect to server: No route to host
> Is the server running on host "locahost" and accepting
> TCP/IP connections on port 5432?
This is a networking setup problem, not a Postgres problem.
"ifconfig lo" might show something useful. On a functioning
Fedora box I get
$ 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:1326801 errors:0 dropped:0 overruns:0 frame:0
TX packets:1326801 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:392324376 (374.1 MiB) TX bytes:392324376 (374.1 MiB)
If no joy there, try checking just what "localhost" is resolving as.
regards, tom lane
PS: I trust "locahost" above is a copy and paste error, else that's
probably your problem.
From | Date | Subject | |
---|---|---|---|
Next Message | Ivan Uemlianin | 2010-05-13 15:03:28 | Re: connecting from trac: "no route to host" error |
Previous Message | Devrim GÜNDÜZ | 2010-05-13 14:46:48 | Re: connecting from trac: "no route to host" error |