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 1teWzv-00E7Pl-QB for pgsql-admin@arkaria.postgresql.org; Sun, 02 Feb 2025 10:14:40 +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 1teWzt-006pdU-KE for pgsql-admin@arkaria.postgresql.org; Sun, 02 Feb 2025 10:14:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1teKvi-0069yp-1F; Sat, 01 Feb 2025 21:21:30 +0000 Received: from mail-wm1-x32e.google.com ([2a00:1450:4864:20::32e]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1teKvf-002kxl-04; Sat, 01 Feb 2025 21:21:29 +0000 Received: by mail-wm1-x32e.google.com with SMTP id 5b1f17b1804b1-436281c8a38so22656215e9.3; Sat, 01 Feb 2025 13:21:27 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1738444885; x=1739049685; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Mg0bzxeK5PfiULYKhbsbLdTnao6Obp3NzoH4IrShYxQ=; b=FN06KXhQmbHlQw7CUgcKMq8D57vsjBJ6Aqgl6vr/6QyJH2W/NE7eXNI6S4g48Rq5I/ 17D/tNBp7Rhzy3RJl/v5UC7qjWQsS4xOD8JghlQJvqeUY1lZ7RsxwDXIXXfabEuW52cd VXIRpxx85jNtswkjscqICSWy6nUE2/wBw3zUnFvytRzCv6skQJuUPUSXyxfBCB1oXOEc zeDelKBJyUDY8qrKJjVoYfdgl0Iee8MQaOHN2XFO59aiNb1+81znYuyK0+WWZmlIDcEi PJVvvt+AUJCnp+qJ4R0YpFdif6xEk9CYfwXfOmPwQS6j21BP4M29MHXQyBcgr8lE/bIw E5zA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1738444885; x=1739049685; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Mg0bzxeK5PfiULYKhbsbLdTnao6Obp3NzoH4IrShYxQ=; b=XjT3nXQlDORQ9BevscHpCsF8a9s++Bv5D7fSaIvt8ZijHX39DtOtxwQZ7OGAwrdVhG bVfuzWrqX79383l+uj2qIydE5gld6BM1ygLb9LjybY9Zxhr6ZUUsxM1j8q8fMIlQdPrZ xJ8wJWRSFzIdOJzxpyaZYNUTU0inWN0l+2wWFzKLXNLbnvMaPl0NoV/44I+54jXLIaYl H/2Gq07zq+XMhoZJQmprAWf39FPuJ3rQN6+zqKh2eLl8S1+tmFbbMcEC5MNI7hBFjx4A 8zSX09Hp1vnOv2Bd5iwwSVIdHNtD33tXyIHWuWQB/iRDx/hb2mjwmFPhwIMWQVlRdEZk V/wg== X-Forwarded-Encrypted: i=1; AJvYcCXoLQ20RG8nu4OyrjuHQNNBFne5pbYCwUvwmWcTkky7BIh/uvNR8Wzehlkld3xTISTqPO2gyvgthrz+rg==@lists.postgresql.org X-Gm-Message-State: AOJu0YxLblkVk/JfdhtsbiBF9eZlD2VbGngYRMCmpNxipffiEoj8b3up vPz7Bcl+A+YtMWVoW+cPmeaJhZXmjdOiHnCzlMjQsm7kMJ1Pa8FMVtcGtLCMQ6zFEDP1H+/f8iZ pS+WD0MU5+MGRNE9uZj2ebhFStJs= X-Gm-Gg: ASbGnctL2kJ5y3vPt/FkJiSJCQyUm5RSXMvh3/vqEbIv2+xpZ6K1eVcYN0JjNEz82Qy bW9j/pVBUt5buvYIIuf2vXWF1uYKILsbxoOLbf4/nu8HtaDGQeKbM63e+I7KRCS/Etgyz7eVb X-Google-Smtp-Source: AGHT+IEMqWYiV328O+eigL9dqpj/AKYIRNeaHiinXgGdcTcRENZ0utiel6lWFGRtj7hzjs/nkqUCnRY2+hPab3FA2TU= X-Received: by 2002:a05:600c:1c1a:b0:435:b064:7dce with SMTP id 5b1f17b1804b1-438dc3c4694mr143447725e9.18.1738444884799; Sat, 01 Feb 2025 13:21:24 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: SOzcn Date: Sun, 2 Feb 2025 00:21:12 +0300 X-Gm-Features: AWEUYZn5OJ0oybrDFm2gdAOBTBgrhnepIJvRLkxA8ew5MtyxUD0M679JnZy25ds Message-ID: Subject: Re: Backup Issue for pg_basebackup To: Somnath Som Cc: pgadmin-support@lists.postgresql.org, Pgsql-admin Content-Type: multipart/alternative; boundary="000000000000d1fb1f062d1b3d44" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d1fb1f062d1b3d44 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello, This is a specific error. You need to specify the IP information of the server where you are providing the replica and the user that will perform the replication in pg_hba.conf on the main cluster. You can find examples of this in many sources. Have a nice day. Somnath Som , 1 =C5=9Eub 2025 Cmt, 19:26 tarihinde= =C5=9Funu yazd=C4=B1: > We are getting below error when running pg_basebackup for a database. > > pg_basebackup: error: FATAL: no pg_hba.conf entry for replication > connection from host "127.0.0.1", user "postgres", SSL on > > FATAL: no pg_hba.conf entry for replication connection from host > "127.0.0.1", user "postgres", SSL off -e > > --000000000000d1fb1f062d1b3d44 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Hello,

This is a specific error. You need to specify the IP information of the = server where you are providing the replica and the user that will perform t= he replication in pg_hba.conf on the main cluster. You can fin= d examples of this in many sources.

Have a nice day.


Somnath Som <somnath.spice@gmail.com>, 1 =C5=9Eub 20= 25 Cmt, 19:26 tarihinde =C5=9Funu yazd=C4=B1:
We are getting below er= ror when running pg_basebackup for a database.

pg_ba= sebackup: error: FATAL:=C2=A0 no pg_hba.conf entry for replica= tion connection from host "127.0.0.1", user "postgres", SSL = on

FATAL= :=C2=A0 no pg_hba.conf entry for replication connection from host "127.0.0.1"= ;, user "postgres", SSL off -e


--000000000000d1fb1f062d1b3d44--