Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qw43T-009LX0-Uz for pgsql-general@arkaria.postgresql.org; Thu, 26 Oct 2023 17:22:00 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qw43S-002oAa-GX for pgsql-general@arkaria.postgresql.org; Thu, 26 Oct 2023 17:21:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qw43Q-002o4d-OQ for pgsql-general@lists.postgresql.org; Thu, 26 Oct 2023 17:21:58 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qw43M-002RE2-UO for pgsql-general@lists.postgresql.org; Thu, 26 Oct 2023 17:21:55 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id BB0DC5C0124; Thu, 26 Oct 2023 13:21:50 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Thu, 26 Oct 2023 13:21:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm2; t= 1698340910; x=1698427310; bh=buSux3yt+qL/Gv5KvNvj/sX8hUqhwyuXWTm fL2DAU1w=; b=XoGTcdvwpN8XhqD4ad3sndKZdpk6RNPag3gbyoO6KTad5UYMM7u ZKrX8GRG4lFeyGcU3dyZ/13csGNq3a78GZW/oTmGM9lLqSwgmUAs6whPk0Fp9l2F mVBxM5tYXxB/fIXZIpqjmoTGUty5P4uVz0voxGeRTw2EagiOw1zAFeCqjMa7y0Ve PvmIG2J3e428y//IGKnyUQLyWVdsjO0d2wVykuNJ9MrD6TyZ03RTyFXPLGkgoYC6 5N6XxVmCj9hmpiNkTdMyAEQGCDNclhIDYeF4j1FDarHwEQXip/IU+3Pv0o3ubMes yybcvdyqop0bXadsO7DQtQ3LB5vcTy8TUcg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1698340910; x= 1698427310; bh=buSux3yt+qL/Gv5KvNvj/sX8hUqhwyuXWTmfL2DAU1w=; b=v QP3uXjO5h3r00O+v+6kqAS5XQkiC3wv6zs9tSeCwYBU0452Y1D4s/4AhYFR8QPAe ovrCtKoZMye3g4PDBnD7BNjncwIOw2u7OENEHr1eHvhqfC/tt0CIWK+UXjUOrbIf MZxWCJuPqKD85sv8Cp31kPjxQNO/uflAMDFH7G0SWF+3SEZCarbUH20UCIyHP39K Svd87PXESBXbYn7Jxw/MmV+pUUNHFCi/hwCEtc+z/yqciYsYZWywwOaVbQyjPXOJ +YbTnceuOgLnIkRCoq/vGaUgsGnH0IvBgfaXY7n5EcGyZ8kGb8OIa0hqaGcPb6y3 J++nBiVcrgdPmGXLNUfXQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrledvgdduuddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvfhfhjggtgfesthekredttddvjeenucfhrhhomheptegurhhi rghnucfmlhgrvhgvrhcuoegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtoh hmqeenucggtffrrghtthgvrhhnpeelgeevkeekkeeuiefgtdevieeluefhfedufeetkeej ffekjeeujeehgeehgeektdenucffohhmrghinhepphhoshhtghhrvghsqhhlrdhorhhgne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhi rghnrdhklhgrvhgvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 26 Oct 2023 13:21:50 -0400 (EDT) Message-ID: <8ab137e5-8dc4-4444-93bb-802cf37ae948@aklaver.com> Date: Thu, 26 Oct 2023 10:21:49 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: issue with remote backup Content-Language: en-US To: Atul Kumar , pgsql-general References: From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 10/26/23 09:51, Atul Kumar wrote: > Hi, > > I have the postgres12 version running on centos7. > > In pg_hba.conf file I have an entry like below: > > host    all             all             /32            md5 > > So from the above entry, I understand that all users can connect to all > databases from the remote ip. > > > But when I use pg_basebackup from remote server using below command I > get the below error: > > pg_basebackup -h DB_server_hostname -p 5444 -U postgres -D > /var/lib/edb/backups/10262023_1 -Fp -Xs -c fast -P > > Error that I got: > > pg_basebackup: error: FATAL:  no pg_hba.conf entry for replication > connection from host "remote_ip", user "postgres", SSL off > > So please help me understand why I am getting this error even after > having a related entry in the pg_hba.conf file. https://www.postgresql.org/docs/current/auth-pg-hba-conf.html " database Specifies which database name(s) this record matches. The value all specifies that it matches all databases. The value sameuser specifies that the record matches if the requested database has the same name as the requested user. The value samerole specifies that the requested user must be a member of the role with the same name as the requested database. (samegroup is an obsolete but still accepted spelling of samerole.) Superusers are not considered to be members of a role for the purposes of samerole unless they are explicitly members of the role, directly or indirectly, and not just by virtue of being a superuser. The value replication specifies that the record matches if a physical replication connection is requested, however, it doesn't match with logical replication connections. Note that physical replication connections do not specify any particular database whereas logical replication connections do specify it. Otherwise, this is the name of a specific PostgreSQL database or a regular expression. Multiple database names and/or regular expressions can be supplied by separating them with commas. If the database name starts with a slash (/), the remainder of the name is treated as a regular expression. (See Section 9.7.3.1 for details of PostgreSQL's regular expression syntax.) A separate file containing database names and/or regular expressions can be specified by preceding the file name with @. " > > > > >  Regards. -- Adrian Klaver adrian.klaver@aklaver.com