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 1sBzxB-002X5X-4X for pgsql-general@arkaria.postgresql.org; Tue, 28 May 2024 16:45:38 +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 1sBzxB-00AqPn-6n for pgsql-general@arkaria.postgresql.org; Tue, 28 May 2024 16:45: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 1sBsFa-0097Yq-Po for pgsql-general@lists.postgresql.org; Tue, 28 May 2024 08:32:06 +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 1sBsFY-0019G6-5a for pgsql-general@lists.postgresql.org; Tue, 28 May 2024 08:32:06 +0000 Received: by mail-lf1-x12f.google.com with SMTP id 2adb3069b0e04-529648cd69dso649266e87.2 for ; Tue, 28 May 2024 01:32:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716885123; x=1717489923; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=n9Xw3IDjynUFzXWZpKmDXx0d8VbLZsio0dKRZEgiBxI=; b=T7DxCiOyHNvzvnRAeBviss1BLv+M3pR3qEWWGS7xoMFEnTRfeE+VE5Hn/nNaaJQiYJ F//++0L6/5QoRpj/4964jKJwqAF4xJekjC8IG8QQBiGJGtVjd6cziwLAI6sEeEb1DsAk gkNMGHWrsBGzQ3oLn1dY+ohO+VaIGZDzt4vzGWKPrRfWu6pQ5rZiXLMLyAQSBy/x8cCa uDqjmrUuMCSVIs5NxmUH3asfMMnbgxA8NEPmHlSxxNeoYAQ2wYUFCjs7N7AQMCrkp3eu XyVG4sQJ4sc8eg3B+Xfd4HyktgDhkExZgrWgNmxUF5t6ZvuT5Is9G14hDl9kAH4h+Uzm aB+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716885123; x=1717489923; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=n9Xw3IDjynUFzXWZpKmDXx0d8VbLZsio0dKRZEgiBxI=; b=tDSnrjvmJ1hfJhMeEn9xz6EDubNfOzepkkTy2IJfdc0C/ixhXlddnn+A/+AA1Tf60/ R2f4sQbmQlEbGVM4kcGMIRhNkPaUCcXbyNre+l/56NKNKa43DY9IkBFUM5uqMvJJTsY6 wnxR8QP52T9gkTFQymq/hFKlvw03iSqyXAQTa+BrGEarOXz2Wv221ptdKTKI1QXZTTNX OGwXME8QZq0L1BYNLBM0++1PYg438FdKUFpjJMaaZeylpRphTCfxHRQw8Pu+f1EeXMus 3BHWOnNSFLGKX2fMROfwyMRmLHZdA1MroXTXGRbZ1Q3hjOlGVDjD5uATH9JiDbTSvLR7 Pomw== X-Gm-Message-State: AOJu0YznCMdVb81KIjns1ETq07fFuzMEwsBh8GaJ8NjpZdUTWBrqM9/h cW/A8cVbmSpcZ3InsIJRVdTII1SmcLPzULDZJcUEWKwkYafHRaGI762cjYiGTImAI3PULP5eHc1 Tx8vt7wSohs2mFuh/1v0bgM1WLNxu87RJhl0= X-Google-Smtp-Source: AGHT+IHHcgakG6DfukZ4CdyhCKxh2+NHCpWJLuPZQe7NCpdF8ri4mS/ALjWxOmnq266dwOBFgVGGoc5zUHYnNOw2U3M= X-Received: by 2002:a05:6512:3c6:b0:523:8723:32de with SMTP id 2adb3069b0e04-52966f8f472mr10439331e87.53.1716885123166; Tue, 28 May 2024 01:32:03 -0700 (PDT) MIME-Version: 1.0 From: vijay patil Date: Tue, 28 May 2024 14:01:51 +0530 Message-ID: Subject: Pgpool with high availability To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000e2f77306197f771f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e2f77306197f771f Content-Type: text/plain; charset="UTF-8" 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. I'm seeking assistance to address this issue. My setup consists of three nodes, each hosting both PostgreSQL and Pgpool services." Thanks Vijay --000000000000e2f77306197f771f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


"= I'm encountering challenges while configuring Pgpool with high availabi= lity. 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 unrea= chable.

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


Thanks

Vijay

--000000000000e2f77306197f771f--