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 1sC05v-002Y20-RT for pgsql-general@arkaria.postgresql.org; Tue, 28 May 2024 16:54:41 +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 1sC05u-00ArEK-Bq for pgsql-general@arkaria.postgresql.org; Tue, 28 May 2024 16:54:38 +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 1sC05t-00ArEC-VM for pgsql-general@lists.postgresql.org; Tue, 28 May 2024 16:54:38 +0000 Received: from mail-ua1-x92f.google.com ([2607:f8b0:4864:20::92f]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sC05r-002OU0-Jh for pgsql-general@lists.postgresql.org; Tue, 28 May 2024 16:54:36 +0000 Received: by mail-ua1-x92f.google.com with SMTP id a1e0cc1a2514c-804e3292412so317292241.0 for ; Tue, 28 May 2024 09:54:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716915274; x=1717520074; 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=lOBhH4I5uFKtiGIDmZPYwUJ7lMv60qgpY6/7gHg85r8=; b=GWMZj95hJoAb8FQb8+Woy8X5fwVIiQfoIYArsu/751sPkU6r3lN6J5uvr5MCDxubt8 qAyHgtdzvkMURoCawutQwx9B7IsXh/2wyD8HqUkUtytOFUxDnd4jS0t4rVFw+RIzJnZL C4nnasuZd2UxjJy8BdjZshe8owjn9REeWW4XJAlf1+GczlWfsXvH6KbmO8k7F740kMnx fWMMJJoEW4PvzkWiEATZrEI+ZlBDJGkyqOMG1Z1esp0WJhViwH39CP+cGve6CdPONAEX /Rm/iVGoDXD7eNUG5KcsaGVay/FWrlNV8zkGygT5mbTelOJSjrpNWFqNoLODPv1EvkOR 88UA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716915274; x=1717520074; 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=lOBhH4I5uFKtiGIDmZPYwUJ7lMv60qgpY6/7gHg85r8=; b=SECljKIsZn9u2iVO2tBLbpISl26XXLOlMp9cLtD9m/tyNCWHZZZGjVPUZyDtWPnHej iRo8Ys6S79MHW04ngjScEotJrPTqw0ld6CHju4lnJLSzZ4QYV/CvLL1qJvwa9ml5cg7b FARxmBIdwjxhUl1D5lscOcyoc7kn86wWtbGTPUVwsMUhAFBGcSEf8PTwCOLWcjsB3Hmr S0B4yEi8CipDWrBqqathxSLGMmUq5r9uaSd1WJZCtFVE4QW11VA3+9rBjxQRWj/eXOoR hLI09Cf1ffmzOGN5LloJ8w2k+MFo8nvBhqTmfWrJYqqswi1aOwagZBRHU3Ka5zLoyGpE 6RPg== X-Gm-Message-State: AOJu0Ywuoq8GpvYcTeLCd0EWqS4TXD7N3qssBoGzJxDb6z9Mt89OkS05 tddDGq8Ul0L4drMmNgsXefDd7PP6hcDu1lwAeoWLHrbnbu4AQ4rcVyTzf+XLslFsxNCy9Kc0Jz5 DzDc9Rq618f1IIfOwzWhYOP/oyNA= X-Google-Smtp-Source: AGHT+IEQMwff54A8kfskLUePMe7aPp4X5QxX4Q0GROWDqGLdjsYctcrFtDk//rSGKIod/sarGU1eADSMp7dK5c1Of/Y= X-Received: by 2002:a67:fc0c:0:b0:480:76a4:3394 with SMTP id ada2fe7eead31-48a38517db8mr11119976137.7.1716915273737; Tue, 28 May 2024 09:54:33 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Kashif Zeeshan Date: Tue, 28 May 2024 21:54:22 +0500 Message-ID: Subject: Re: Pgpool with high availability To: vijay patil Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000002f1c0619867d9d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000002f1c0619867d9d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Vijay Can you please share the error log, as from the description its hard to figure out the issue causing this problem. Regards Kashif Zeeshan Bitnine Global On Tue, May 28, 2024 at 9:42=E2=80=AFPM vijay patil wrote: > > HI Team, > > "I'm encountering challenges while configuring Pgpool with high > availability. The initial setup is completed, and Pgpool is operational o= n > a single node, functioning without issues. However, upon attempting to > start Pgpool on any additional nodes, particularly node 2, it becomes > immediately unreachable. > > I'm seeking assistance to address this issue. My setup consists of three > nodes, each hosting both PostgreSQL and Pgpool services." > > > Thanks > > Vijay > --000000000000002f1c0619867d9d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Vijay

Can you please= share the error log, as from the description its hard to figure out the is= sue causing this problem.

Regards
K= ashif Zeeshan
Bitnine Global

On Tue, May 28, 2024 at 9:4= 2=E2=80=AFPM vijay patil <vi= jay.postgres@gmail.com> wrote:


HI Team,

"I'm encountering challenges while configuring Pgp= ool with high availability. The initial setup is completed, and Pgpool is o= perational on a single node, functioning without issues. However, upon atte= mpting to start Pgpool on any additional nodes, particularly node 2, it bec= omes immediately unreachable.

I'm seeking assistance to address this issue. My setup con= sists of three nodes, each hosting both PostgreSQL and Pgpool services.&quo= t;


Thanks

Vijay

--000000000000002f1c0619867d9d--