Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1jGRta-0008Nb-8h for pgsql-admin@arkaria.postgresql.org; Mon, 23 Mar 2020 18:33:54 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jGRtZ-0002MJ-2O for pgsql-admin@arkaria.postgresql.org; Mon, 23 Mar 2020 18:33:53 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jGRtY-0002MC-PA for pgsql-admin@lists.postgresql.org; Mon, 23 Mar 2020 18:33:52 +0000 Received: from jakobs.com ([85.214.83.89] helo=rs.plausibolo.de) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jGRtV-0002Po-QQ for pgsql-admin@lists.postgresql.org; Mon, 23 Mar 2020 18:33:52 +0000 Received: from localhost (localhost [127.0.0.1]) by rs.plausibolo.de (Postfix) with ESMTP id 8BBAEBE142C for ; Mon, 23 Mar 2020 19:33:48 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at rs.plausibolo.de Received: from rs.plausibolo.de ([127.0.0.1]) by localhost (h2367442.stratoserver.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZFFANhlbxU6k; Mon, 23 Mar 2020 19:33:46 +0100 (CET) Received: from [192.168.178.85] (i5E86B0CA.versanet.de [94.134.176.202]) by rs.plausibolo.de (Postfix) with ESMTPSA id DBE2ABE101D; Mon, 23 Mar 2020 19:33:45 +0100 (CET) Subject: Re: Problem with replication To: pgsql-admin@lists.postgresql.org References: <36847976.780175.1584988236276.ref@mail.yahoo.com> <36847976.780175.1584988236276@mail.yahoo.com> From: Holger Jakobs Message-ID: Date: Mon, 23 Mar 2020 19:33:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.4.1 MIME-Version: 1.0 In-Reply-To: <36847976.780175.1584988236276@mail.yahoo.com> Content-Type: multipart/alternative; boundary="------------EA13E74A2B9DE7A09B012543" Content-Language: de-DE List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This is a multi-part message in MIME format. --------------EA13E74A2B9DE7A09B012543 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi Douglas, the connection attempt has obviously been started via a "local" connection, using a Unix socket instead of TCP/IP. Therefore, no IP address is involved. Is the slave db on the same machine? Regards, Holger Am 23.03.20 um 19:30 schrieb Douglas Reed: > Hi > > We are running Pg Version 9.6 > > On OS Centos 7 running on a VM (Nutanix) > > We are trying to build a slave server on this platform. The relevant > IP entry for replication has been placed in pg_hba.conf on the master. > We run pg_basebackup successfully and then set up recovery.conf etc > and re-start > the slave database. It seems to process the WALs and then enter the > read only state when it then generates the following errors; > > Mar 23 15:22:48 xds-data1-temp postgres[13072]: [2-1] > user=,db=,app=client= LOG:  database system is ready to accept read > only connections > Mar 23 15:22:49 xds-data1-temp postgres[13083]: [3-1] > user=[unknown],db=[unknown],app=[unknown]client=[local] LOG:  > connection received: host=[local] > Mar 23 15:22:49 xds-data1-temp postgres[13083]: [4-1] > user=postgres,db=[unknown],app=[unknown]client=[local] FATAL:  no > pg_hba.conf entry for replication connection from host "[local]", user > "postgres", SSL off > Mar 23 15:22:49 xds-data1-temp postgres[13082]: [3-1] > user=,db=,app=client= FATAL:  could not connect to the primary server: > FATAL:  no pg_hba.conf entry for replication connection from host > "[local]", user "postgres", SSL off > Mar 23 15:22:49 xds-data1-temp postgres[13082]: [3-2] > Mar 23 15:22:49 xds-data1-temp postgres[13085]: [3-1] > user=[unknown],db=[unknown],app=[unknown]client=[local] LOG:  > connection received: host=[local] > Mar 23 15:22:49 xds-data1-temp postgres[13085]: [4-1] > user=postgres,db=[unknown],app=[unknown]client=[local] FATAL:  no > pg_hba.conf entry for replication connection from host "[local]", user > "postgres", SSL off > Mar 23 15:22:49 xds-data1-temp postgres[13084]: [3-1] > user=,db=,app=client= FATAL:  could not connect to the primary server: > FATAL:  no pg_hba.conf entry for replication connection from host > "[local]", user "postgres", SSL off > > We know that the entry is in the hba and have checked for typos, but > one thing that does stick out with one line on the message is; > >     FATAL:  no pg_hba.conf entry for replication connection from host > "[local]" > > Other messages I have seen in the past would normally have an IP > address where is says "[local]" > > Any ideas as to where we might be going wrong? > > > Many thanks > > > > > > Doug Reed > dougreed765@yahoo.com > 07973-132664 > https://uk.linkedin.com/pub/douglas-reed/33/326/2b -- Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012 --------------EA13E74A2B9DE7A09B012543 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi Douglas,

the connection attempt has obviously been started via a "local" connection, using a Unix socket instead of TCP/IP. Therefore, no IP address is involved.

Is the slave db on the same machine?

Regards,

Holger

Am 23.03.20 um 19:30 schrieb Douglas Reed:
Hi

We are running Pg Version 9.6

On OS Centos 7 running on a VM (Nutanix)

We are trying to build a slave server on this platform. The relevant IP entry for replication has been placed in pg_hba.conf on the master. We run pg_basebackup successfully and then set up recovery.conf etc and re-start 
the slave database. It seems to process the WALs and then enter the read only state when it then generates the following errors;

Mar 23 15:22:48 xds-data1-temp postgres[13072]: [2-1] user=,db=,app=client= LOG:  database system is ready to accept read only connections
Mar 23 15:22:49 xds-data1-temp postgres[13083]: [3-1] user=[unknown],db=[unknown],app=[unknown]client=[local] LOG:  connection received: host=[local]
Mar 23 15:22:49 xds-data1-temp postgres[13083]: [4-1] user=postgres,db=[unknown],app=[unknown]client=[local] FATAL:  no pg_hba.conf entry for replication connection from host "[local]", user "postgres", SSL off
Mar 23 15:22:49 xds-data1-temp postgres[13082]: [3-1] user=,db=,app=client= FATAL:  could not connect to the primary server: FATAL:  no pg_hba.conf entry for replication connection from host "[local]", user "postgres", SSL off
Mar 23 15:22:49 xds-data1-temp postgres[13082]: [3-2]
Mar 23 15:22:49 xds-data1-temp postgres[13085]: [3-1] user=[unknown],db=[unknown],app=[unknown]client=[local] LOG:  connection received: host=[local]
Mar 23 15:22:49 xds-data1-temp postgres[13085]: [4-1] user=postgres,db=[unknown],app=[unknown]client=[local] FATAL:  no pg_hba.conf entry for replication connection from host "[local]", user "postgres", SSL off
Mar 23 15:22:49 xds-data1-temp postgres[13084]: [3-1] user=,db=,app=client= FATAL:  could not connect to the primary server: FATAL:  no pg_hba.conf entry for replication connection from host "[local]", user "postgres", SSL off

We know that the entry is in the hba and have checked for typos, but one thing that does stick out with one line on the message is; 

    FATAL:  no pg_hba.conf entry for replication connection from host "[local]" 

Other messages I have seen in the past would normally have an IP address where is says "[local]"

Any ideas as to where we might be going wrong?    


Many thanks





-- 
Holger Jakobs, Bergisch Gladbach, Tel. +49-178-9759012
--------------EA13E74A2B9DE7A09B012543--