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 1sCX43-006Cg1-9E for pgsql-general@arkaria.postgresql.org; Thu, 30 May 2024 04:06:56 +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 1sCX43-0013xr-3y for pgsql-general@arkaria.postgresql.org; Thu, 30 May 2024 04:06:55 +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 1sCX42-0013xj-Nb for pgsql-general@lists.postgresql.org; Thu, 30 May 2024 04:06:54 +0000 Received: from mail-lf1-x12f.google.com ([2a00:1450:4864:20::12f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sCX40-001S7a-64 for pgsql-general@lists.postgresql.org; Thu, 30 May 2024 04:06:54 +0000 Received: by mail-lf1-x12f.google.com with SMTP id 2adb3069b0e04-52b27afe214so332887e87.1 for ; Wed, 29 May 2024 21:06:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717042012; x=1717646812; 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=oSiYgTnMG1aPWaAAKqqgIMxH8OuNcjF+LsrU62DyLxc=; b=S4BKAhluQ+HiF1QSi7XCJaVsLXbbsUfQMRgzDOXjXZrefqm0LY+7nW9Eo3FDLzur/v mXzZahv5rfchSRI35NjLTlKr22XX29HznuFEMWCjmi19VpgGxyewuPCWYQwRlH2TAZ3q 7/YFUd7tbnointDBJ5j1rnw7Pjj5RUExDFKaIA1AG9zgNCT3vrNkpxgQj03vN4hCBktM YUGXvtK/Vk0vVgcf80+ifzsMCtTkdL2MJjHU6mgIKu4PLdN/BnxXw62i1+8attYFR8MI 3vy3A2siU6ylvLptf2fZcIoJlBWwj66VBAfUORWFdXiSbG8po1pIjposq41YVICraJmK OdOg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717042012; x=1717646812; 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=oSiYgTnMG1aPWaAAKqqgIMxH8OuNcjF+LsrU62DyLxc=; b=YDK0XDaO1RCU/29mC3ji7IXB3dbNuCrbQ3nbDzdSlAR3MYZaZAd8niEL7gh5BHQQgU 1T+oZn+vzpa/aAphmYIKZDmF7SeqMxWuPV63HIe2BjwmiyYG91WHbHMuyQWOa1Re1a4Z 8z3+qtsVWpAOtdWUMaJotHbgv0IDF4T4Ym9UqYRYOQZRkoo8G9zTtOS9BMe7dG25nIuJ Ms8glKM5+0usyhGpcoJNhzMhNZVUBIIAE+eHJjAConJ3N7AItTVcg/VgxLVaw4+ajfVv TShhtwaFDej8biUf5uSG8UaLpoHFRWbQ1d0lKmMlSkmuM+w6AeO4QBJYGY42vGZ7Fj1a KWSQ== X-Forwarded-Encrypted: i=1; AJvYcCU0skO/cgnEKmXKTnUBpiPEWC7/bTDRD09IfLfJ+Z1Yzqm0rHJ19gPROPwc6Lze3i4p2fAj+gMRKBiRheZ612xbBazN6BxpKb8FSKdBb4SaJfwC X-Gm-Message-State: AOJu0Yx2Jpbo0hZRwEBDTmsY6c7W3IZJCmVLYUqIQUmU4rX7lHOiUDW/ RIm9FpGQ4rb7uqhQdtc14lMQ0fFknno+rD2/14cxIOFUH2rt+rOEdveKHNGT9AuSoykmsTFPIk2 ku5pZra+JgpbHJie608LCUdq1d/M4ICSQ X-Google-Smtp-Source: AGHT+IHH3bYObr7hbwwTehxTd0APc8WBnGMJkku2Cn5U1kbS5V0GqBNUj5Zz0DiXBOqJ+UMwefYnNTC/1hrnEW6UtAc= X-Received: by 2002:a05:6512:61:b0:523:7680:d07 with SMTP id 2adb3069b0e04-52b7e0f0768mr160573e87.6.1717042011515; Wed, 29 May 2024 21:06:51 -0700 (PDT) MIME-Version: 1.0 References: <22b7b0b8-c348-44df-a9a4-ceba94f379b2@aklaver.com> In-Reply-To: From: vijay patil Date: Thu, 30 May 2024 09:36:39 +0530 Message-ID: Subject: Re: Pgpool with high availability To: Kashif Zeeshan Cc: Muhammad Imtiaz , Adrian Klaver , pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000002933e30619a3ff91" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002933e30619a3ff91 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable HI Kashif, The VIP 10.127.1.18 is accessible from the leader node (ha0002) only but not from the standby nodes (ha0001 and ha0003). Thanks Vijay On Thu, May 30, 2024 at 9:17=E2=80=AFAM Kashif Zeeshan wrote: > Hi Vijay > > The log shows that all the nodes are able to communicate now (master, > standby and standby1) and now what are the issue you are facing? > > Regards > Kashif Zeeshan > > On Thu, May 30, 2024 at 2:00=E2=80=AFAM vijay patil > wrote: > >> Thanks Muhammad ! >> >> Here i uploaded details. >> >> Thanks >> Vijay >> >> On Wed, May 29, 2024 at 10:58=E2=80=AFAM Muhammad Imtiaz >> wrote: >> >>> Hi, >>> >>> Can you please provide the Pgpool logs? Additionally, in a distributed >>> environment, ensure that Pgpool is properly configured. You can follow >>> these documented steps to set up the Pgpool configurations >>> pgpool.conf,pcp.conf and pool_hba.conf . >>> >>> Regards, >>> Muhammad Imtiaz >>> >>> On Tue, 28 May 2024 at 23:01, Adrian Klaver >>> wrote: >>> >>>> >>>> >>>> On 5/28/24 1:31 AM, vijay patil wrote: >>>> > >>>> > HI Team, >>>> > >>>> > "I'm encountering challenges while configuring Pgpool with high >>>> > availability. The initial setup is completed, and Pgpool is >>>> operational >>>> > on a single node, functioning without issues. However, upon >>>> attempting >>>> > to start Pgpool on any additional nodes, particularly node 2, it >>>> becomes >>>> > immediately unreachable. >>>> >>>> And how we are supposed to arrive at an answer with essentially no >>>> information provided? >>>> >>>> Need: >>>> >>>> 1) Configuration for initial setup. >>>> >>>> 2) A more detailed explanation of what "... upon attempting >>>> to start Pgpool on any additional nodes" means? Include configuration >>>> changes. >>>> >>>> 3) The error messages. >>>> >>>> 4) Where the nodes are located? >>>> >>>> >>>> > >>>> > I'm seeking assistance to address this issue. My setup consists of >>>> three >>>> > nodes, each hosting both PostgreSQL and Pgpool services." >>>> > >>>> > >>>> > Thanks >>>> > >>>> > Vijay >>>> > >>>> >>>> -- >>>> Adrian Klaver >>>> adrian.klaver@aklaver.com >>>> >>>> >>>> --0000000000002933e30619a3ff91 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
HI Kashif,

The VIP=C2=A010.127.1.18=C2=A0is accessible from the leader node (<= span style=3D"font-size:10pt;font-family:"Courier New"">ha0002) only=C2=A0 but not from the standby nodes (ha0001=C2=A0and=C2=A0ha0003)= .

Thanks
Vijay

On T= hu, May 30, 2024 at 9:17=E2=80=AFAM Kashif Zeeshan <kashi.zeeshan@gmail.com> wrote:
Hi=C2=A0Vija= y

The log shows that all the nodes are able to communica= te now (master, standby and standby1) and now what are the issue you=C2=A0a= re facing?

Regards
Kashif Zeeshan
<= /div>
O= n Thu, May 30, 2024 at 2:00=E2=80=AFAM vijay patil <vijay.postgres@gmail.com> = wrote:
Thanks Muhammad !

Here i uploaded details.

Thanks
Vijay

On Wed, May 29, 2024 at 10= :58=E2=80=AFAM Muhammad Imtiaz <imtiaz.m@bitnine.net> wrote:
Hi,

Can you please provide the Pgpool logs? Additionally, in a distributed envi= ronment, ensure that Pgpool is properly configured. You can follow these do= cumented steps to set up the Pgpool configurations=20 pgpool.conf,pcp.conf and=20 pool_hba.conf .

Regards,
Muhammad Imtiaz

On Tue, 28 May 2024 at 23:01, Adrian Kla= ver <adri= an.klaver@aklaver.com> wrote:


On 5/28/24 1:31 AM, vijay patil wrote:
>
> HI Team,
>
> "I'm encountering challenges while configuring Pgpool with hi= gh
> availability. The initial setup is completed, and Pgpool is operationa= l
> on a single node, functioning without issues. However, upon attempting=
> to start Pgpool on any additional nodes, particularly node 2, it becom= es
> immediately unreachable.

And how we are supposed to arrive at an answer with essentially no
information provided?

Need:

1) Configuration for initial setup.

2) A more detailed explanation of what "... upon attempting
to start Pgpool on any additional nodes" means? Include configuration =
changes.

3) The error messages.

4) Where the nodes are located?


>
> I'm seeking assistance to address this issue. My setup consists of= three
> nodes, each hosting both PostgreSQL and Pgpool services."
>
>
> Thanks
>
> Vijay
>

--
Adrian Klaver
adrian.klave= r@aklaver.com


--0000000000002933e30619a3ff91--