Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M43008=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1XjXRp-0007Rh-Kn
 for pgsql-admin@arkaria.postgresql.org; Wed, 29 Oct 2014 17:54:17 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M43008=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1XjXRp-0000vG-0m
 for pgsql-admin@arkaria.postgresql.org; Wed, 29 Oct 2014 17:54:17 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
 by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1XjXRn-0000v9-OM
 for pgsql-admin@postgresql.org; Wed, 29 Oct 2014 17:54:15 +0000
Received: from mail-yk0-x22b.google.com ([2607:f8b0:4002:c07::22b])
 by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.80) (envelope-from <jayknowsunix@gmail.com>)
 id 1XjXRf-00030K-I6
 for pgsql-admin@postgresql.org; Wed, 29 Oct 2014 17:54:14 +0000
Received: by mail-yk0-f171.google.com with SMTP id 20so1527754yks.2
 for <pgsql-admin@postgresql.org>; Wed, 29 Oct 2014 10:54:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:cc:subject
 :references:in-reply-to:content-type:content-transfer-encoding;
 bh=5g2BgltTrtskMUQJboC3tIxCFYNCbTElE7VvSy3eGUw=;
 b=P9FdnnRyCMwL6q+fkZeUEzDB4JQ6HlnBYLvhxlcDMyPzgC0toV4Dwc9/0FLqu26Bij
 puQrnVBReGUO1s+i/sd6/FrnbaUkt4/XndywO6yLHEmypNr9aUtQ3zTFVoOsCBTl+EHC
 Pawdu00GAbLJ8Izj6m3etp8J8l/sMrV1xZ77Sbc8rm8kNV5mCnKds/IBNGDT/mIM75h6
 ZJGC0deMWDiEJSyGejgMYQUdXexAHq5mUDbA/U/HeW26gNBE4EUBb8SjDp21q31QZcg4
 FMCqWGfypCvoQonB6Lvf+fmNe702AakgvH7JJ0mEtGX7SYAOckLt2pfAaDaF4aDYSVUE
 jJgg==
X-Received: by 10.170.43.78 with SMTP id 75mr3082786ykl.123.1414605245308;
 Wed, 29 Oct 2014 10:54:05 -0700 (PDT)
Received: from [192.168.254.2] (h77.89.102.166.static.ip.windstream.net.
 [166.102.89.77])
 by mx.google.com with ESMTPSA id i70sm2226175yhq.7.2014.10.29.10.54.03
 for <multiple recipients>
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Wed, 29 Oct 2014 10:54:04 -0700 (PDT)
Message-ID: <5451297F.2080405@gmail.com>
Date: Wed, 29 Oct 2014 13:53:03 -0400
From: John Scalia <jayknowsunix@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Tom Lane <tgl@sss.pgh.pa.us>
CC: Shreeyansh dba <shreeyansh2014@gmail.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: A local replication entry
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>
In-Reply-To: <25754.1414599609@sss.pgh.pa.us>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Pg-Spam-Score: -2.0 (--)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

OK, weirder yet!!!!

After all this screwing around, and I think this was the first time that I did a "stop", removed the log file so I could easily see the result, and then I issued a "start" on the 
database, just for grins, I tried running the pg_basebackup command again. I pulled it from the shell's history and invoked it, and. It ran without a single problem. I'm guessing 
now that something was incorrect in memory somewhere, and just reloading the pg_hba.conf wasn't fixing it.

I apologize to all for not thinking to issue a restart before this moment, but now I am a little worried that this might bite us in production.

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