From: | Adam H(dot)Pendleton <fmonkey(at)fmonkey(dot)net> |
---|---|
To: | Peter Bradley <apvx95(at)dsl(dot)pipex(dot)com> |
Cc: | pgadmin-support(at)postgresql(dot)org |
Subject: | Re: Cannot connect to postgresql |
Date: | 2004-07-19 10:25:12 |
Message-ID: | EB4F84EA-D96D-11D8-9DD7-000A95B4F45C@fmonkey.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
On Jul 18, 2004, at 4:03 PM, Peter Bradley wrote:
> netstat -l confirms that the server is listening on port 5432.
>
> If I try to telnet to port 5432 I get "Connection refused" both as my
> own user and as the postgres user.
If your postgresql server is indeed listening on TCP port 5432, and you
issue a telnet command to that port, and get connection refused, then
there are three probable reasons you cannot connect:
1) Postgresql is listening on a different interface than you are trying
to connect to. IOW, it might be listening on 1.2.3.4:5432, and you're
telnetting to 127.0.0.1:5432. Your netstat command should show what
interface it's listening on (ideally, it should be 0.0.0.0:5432, which
is all interfaces).
2) You've got a firewall installed, blocking port 5432. A lot of
firewalls return RST packets (which is what generates the connection
refused message) to incoming connections. Make sure iptables isn't
blocking 5432.
3) You made a typo. :-)
What is the result of looking at those three items?
ahp
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Bradley | 2004-07-19 17:17:54 | Re: Cannot connect to postgresql |
Previous Message | Andreas Pflug | 2004-07-18 21:50:29 | Re: Cannot connect to postgresql |