I thought you might be correct, Tom, but I double-checked the postgresql.conf file and listen_addresses = "*". I had forgotten to look to see if netstat reported:
tcp 0 0 0.0.0.0:5432 0.0.0.0:* LISTEN
But even with that established, the pg_basebackup using:
/usr/pgsql-9.3/bin/pg_basebackup -D - -h 127.0.0.1 -Ft -z -c fast -l hourly.backup > backup_file.gz or
/usr/pgsql-9.3/bin/pg_basebackup -D - -h 127.0.0.1 -U postgres -Ft -z -c fast -l hourly.backup > backup_file.gz
are still failing with:
pg_basebackup: could not connect to server: FATAL: no pg_hba.conf entry for replication connection from host "127.0.0.1", user "postgres", SSL off
The line from the pg_hba.conf file currently reads:
host replication postgres 127.0.0.1/32 trust
I really don't see where the problem is, and I know I've done a reload after every change in the pg-hba.conf.
On 10/29/2014 11:05 AM, Tom Lane wrote:
John Scalia <jayknowsunix@xxxxxxxxx> writes:
And I performed a "service postgresql-9.3 reload", and it still failed with the same error. Then, I tried again using a "-h 127.0.0.1" option for the pg_basebackup. That complained
"pg_basebackup: could not connect to server: connection refused." So, I did a "netstat -an | grep 5432" and I see that postgresql is not listening on that port for 127.0.0.1.
Hm, that suggests your problem is with the setting of listen_addresses,
not just what's in pg_hba.conf.
regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
