8.0 Client can't connect to 7.3 server?

Started by Jussi Saarinenabout 20 years ago4 messagesgeneral
Jump to latest

I have following environment:

Server1, rh9, ip:192.168.1.10:
postgresql-7.3.4-3.rhl9
postgresql-libs-7.3.4-3.rhl9
postgresql-server-7.3.4-3.rhl9
postgresql-jdbc-7.3.4-3.rhl9

Server2, fc4, ip:192.168.1.11:
postgresql-libs-8.0.7-1.FC4.1
postgresql-8.0.7-1.FC4.1
postgresql-server-8.0.7-1.FC4.1
postgresql-jdbc-8.0.7-1.FC4.1
postgresql-contrib-8.0.7-1.FC4.1

I can't connect to server1 (7.3.4) using client (8.0.7) at server2.
I just get error:
psql: FATAL: No pg_hba.conf entry for host 192.168.1.11, user joe,
database template1

Uncommented lines at server1's pg_hba.conf (postgresql service is
restarted after every change):
local all all trust trust
host all all 192.168.1.11 255.255.255.255 trust

Server1 also have line:
tcpip_socket = true
in postgresql.conf

Any ideas what's wrong?

--
-jussi

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

#2Louis Gonzales
louis.gonzales@linuxlouis.net
In reply to: Jussi Saarinen (#1)
Re: 8.0 Client can't connect to 7.3 server?

Jussi Saarinen wrote:

I have following environment:

Server1, rh9, ip:192.168.1.10:
postgresql-7.3.4-3.rhl9
postgresql-libs-7.3.4-3.rhl9
postgresql-server-7.3.4-3.rhl9
postgresql-jdbc-7.3.4-3.rhl9

Server2, fc4, ip:192.168.1.11:
postgresql-libs-8.0.7-1.FC4.1
postgresql-8.0.7-1.FC4.1
postgresql-server-8.0.7-1.FC4.1
postgresql-jdbc-8.0.7-1.FC4.1
postgresql-contrib-8.0.7-1.FC4.1

I can't connect to server1 (7.3.4) using client (8.0.7) at server2.
I just get error:
psql: FATAL: No pg_hba.conf entry for host 192.168.1.11, user joe,
database template1

Uncommented lines at server1's pg_hba.conf (postgresql service is
restarted after every change):
local all all trust trust
host all all 192.168.1.11 255.255.255.255 trust

Server1 also have line:
tcpip_socket = true
in postgresql.conf

Any ideas what's wrong?

Two things come to mind:
1) do you have a defined postgresql user "joe" ?
2) 192.168.1.11/32 (without looking it up, I'm not sure if you can
specify the subnetmask, as an alternative to the /DecimalNumber notation)
This is certainly only an issue with the entry in pg_hba.conf, on the
server to be contacted, just missing the correct configuration.

Remember OS user "joe" != postgresql user "joe"
postgresql user "joe" must have been granted access to the database
instance you're attempting to connect to, then you can have an entry like:

host all all 192.168.1.1/32 trust ( where postgresql user "joe"
would be implied )

#3Tom Lane
tgl@sss.pgh.pa.us
In reply to: Jussi Saarinen (#1)
Re: 8.0 Client can't connect to 7.3 server?

Jussi Saarinen <jms@iki.fi> writes:

I can't connect to server1 (7.3.4) using client (8.0.7) at server2.
I just get error:
psql: FATAL: No pg_hba.conf entry for host 192.168.1.11, user joe,
database template1

Uncommented lines at server1's pg_hba.conf (postgresql service is
restarted after every change):
local all all trust trust
host all all 192.168.1.11 255.255.255.255 trust

That error is not possible with this pg_hba.conf file. You're probably
editing the wrong conf file, or possibly restarting the wrong server.

regards, tom lane

In reply to: Louis Gonzales (#2)
Re: 8.0 Client can't connect to 7.3 server?

On Wed, Mar 08, 2006 at 03:03:22PM -0500, Louis Gonzales wrote:

Two things come to mind:
1) do you have a defined postgresql user "joe" ?
2) 192.168.1.11/32 (without looking it up, I'm not sure if you can
specify the subnetmask, as an alternative to the /DecimalNumber notation)
This is certainly only an issue with the entry in pg_hba.conf, on the
server to be contacted, just missing the correct configuration.

Remember OS user "joe" != postgresql user "joe"
postgresql user "joe" must have been granted access to the database
instance you're attempting to connect to, then you can have an entry like:

host all all 192.168.1.1/32 trust ( where postgresql user "joe"
would be implied )

Thanks Louis!

Problem was in pg_hba.conf as error message suggested ;)
Servers are now in different subnets and my configuration was
out of date. Sorry.

--
-jussi

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.