From: John Scalia <jayknowsunix@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Shreeyansh dba <shreeyansh2014@gmail.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: A local replication entry
Date: Wed, 29 Oct 2014 13:42:08 -0400
Message-ID: <545126F0.2090704@gmail.com> (raw)
In-Reply-To: <25754.1414599609@sss.pgh.pa.us>
References: <5450E937.2070408@gmail.com>
<CAGDYbUP3OewxxUNAf5DBBZPEwOWyEGbSBp3eKqq3F2+r6y-+Gw@mail.gmail.com>
<5450FB3D.7030008@gmail.com>
<23872.1414595142@sss.pgh.pa.us>
<54510950.90100@gmail.com>
<25754.1414599609@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Well, it is using the pg_hba.conf I thought. I edited the pg_hba.conf file and changed the line I thought pg_basebackup should be using from "trust" to "fake_it" and issued a
reload. I saw an "invalid authentication method 'fake_it'" reported in the pg_log/postgresql-Wed.log file. To confirm that it really was using the correct pg_hba.conf file and I
stopped the database and tried to start it again. That start did fail with:
<timestamp> % LOG: invalid authentication method "fake_it"
<timestamp> % CONTEXT: line 101 of configuration file "/var/lib/pgsql/9.3/data/pg_hba.conf"
<timestamp> % FATAL: could not load pg_hba.conf
So, it really is using the correct pg_hba.conf.
Allow me to note, in closing, that this particular VM: csgha2 has been a problem child since it was built, and many things have been broken on it. I don't know if this is another
one of the very hard-to-solve problems or not. I may try this on another of my sandbox systems. Still I need to know why this is failing.
On 10/29/2014 12:20 PM, Tom Lane wrote:
> John Scalia <jayknowsunix@gmail.com> writes:
>> 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.
> Everything that you've said looks fine, so the problem is somewhere you're
> not looking :-(. At this point, I'd wonder if the pg_hba.conf file you're
> changing is the same one the postmaster is reading. You might try
> confirming that directly by inserting a syntactically-incorrect entry and
> seeing if the postmaster bleats about it to the postmaster log when you
> issue a reload.
>
> regards, tom lane
>
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: jayknowsunix@gmail.com, tgl@sss.pgh.pa.us, shreeyansh2014@gmail.com
Subject: Re: A local replication entry
In-Reply-To: <545126F0.2090704@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox