the file pg_hba.conf is not working on pgsql 9.1

Bug #910300 reported by Alain Toussaint
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postgresql-9.1 (Ubuntu)
New
Undecided
Unassigned

Bug Description

I am trying to work remotely with Postgresql 9.1 and modified the file:

/var/lib/postgresql/9.1/main/pg_hba.conf to contain these setting:

local all all md5
host all all 127.0.0.1/32 md5
host all all 192.168.0.0/24 md5
host all all 192.168.0.102/32 md5

on using pgadmin III on windows to access my server, I get these error messages in postgresql logs:

2011-12-30 22:45:21 EST FATAL: no pg_hba.conf entry for host "192.168.0.102", user "postgres", database "postgres", SSL on
2011-12-30 22:45:21 EST FATAL: no pg_hba.conf entry for host "192.168.0.102", user "postgres", database "postgres", SSL off
2011-12-30 22:46:00 EST FATAL: no pg_hba.conf entry for host "192.168.0.102", user "postgres", database "postgres", SSL on
2011-12-30 22:46:00 EST FATAL: no pg_hba.conf entry for host "192.168.0.102", user "postgres", database "postgres", SSL off
2011-12-30 22:46:24 EST FATAL: no pg_hba.conf entry for host "192.168.0.102", user "postgres", database "postgres", SSL on
2011-12-30 22:46:24 EST FATAL: no pg_hba.conf entry for host "192.168.0.102", user "postgres", database "postgres", SSL off

I have tried to tunnel the 5432 port from my server (ip address: 192.168.0.50) to the workstation (192.168.0.102) and it result in the same error:

2011-12-30 22:48:19 EST FATAL: no pg_hba.conf entry for host "192.168.0.50", user "postgres", database "postgres", SSL on
2011-12-30 22:48:19 EST FATAL: no pg_hba.conf entry for host "192.168.0.50", user "postgres", database "postgres", SSL off
2011-12-30 22:48:40 EST FATAL: no pg_hba.conf entry for host "192.168.0.50", user "postgres", database "postgres", SSL on
2011-12-30 22:48:40 EST FATAL: no pg_hba.conf entry for host "192.168.0.50", user "postgres", database "postgres", SSL off

on the other hands, using php pg admin on the server work fine. I did configure postgres so it listen to any address (localhost in this case and 192.168.0.50) but for one reason or another, postgresql doesn't tcp/ip connexions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.