From: | Aaron Steele <asteele(at)berkeley(dot)edu> |
---|---|
To: | Richard Huxton <dev(at)archonet(dot)com> |
Cc: | Michael Korotun <michael(at)softasap(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: remote tcp connection problem PG 8.0.1 |
Date: | 2005-05-04 21:06:44 |
Message-ID: | 42793964.5050306@berkeley.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
i'm having the same problem running pg8.0.1 on redhat enterprise linux
AS 3 (2.4.21-27.0.4.ELsmp).
shutting off my firewall via 'service iptables stop' solves the
problem... what needs to be modified in the iptables to allow remote pg
connections?
Richard Huxton wrote:
> Michael Korotun wrote:
>
>> Hi Guys,
>>
>> I can't get working remote tcp connections on default port 5432.
>> Environment is as follows
>>
>> OS: Fedora Core 3
>> DB: Postgresql 8.0.1
>>
>> 1) The listen_addresses is set to '*' in postgresql.conf
>> 2) pg_hba.conf is edited with client host ip, (the one which tries to
>> eastablish connection)
>
>
> 1. Turn connection logging on in your postgresql.conf and restart
> postgresql.
> 2. From the database server, try "telnet localhost 5432" - it should
> connect (and display nothing). Type "A" and hit return twice - you
> should be disconnected. Check your logs and there should be a message
> about an invalid startup packet.
> 3. Do the same from your client, "telnet DB-SERVER-IP-ADDRESS 5432"
> and repeat the test.
>
> If step 3 works, then there's no problem with the server. If you can't
> connect at step 3 and PG doesn't log anything then you probably have a
> firewall in the way.
>
> --
> Richard Huxton
> Archonet Ltd
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-05-04 21:17:31 | Re: remote tcp connection problem PG 8.0.1 |
Previous Message | Peter Wilson | 2005-05-04 20:40:29 | Re: Postgres vs Firebird? |