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 1sC18j-002eoy-TW for pgsql-general@arkaria.postgresql.org; Tue, 28 May 2024 18:01:39 +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 1sC18h-00B3NB-SG for pgsql-general@arkaria.postgresql.org; Tue, 28 May 2024 18:01:35 +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 1sC18g-00B3N2-Hm for pgsql-general@lists.postgresql.org; Tue, 28 May 2024 18:01:35 +0000 Received: from fout4-smtp.messagingengine.com ([103.168.172.147]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sC18Y-001D7B-37 for pgsql-general@lists.postgresql.org; Tue, 28 May 2024 18:01:33 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfout.nyi.internal (Postfix) with ESMTP id 27EDC13800E6; Tue, 28 May 2024 14:01:24 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 28 May 2024 14:01:24 -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:subject:subject:to:to; s=fm3; t=1716919284; x=1717005684; bh=rrE+OjZp1437A9GhfwMsem88cGNA3uyV+nsZgDt11D0=; b= lD3vkVfJ/4y7ISyzHEAHnKiVHkSWtq5r7vnDXIDOBx2AJzf1UKOItSeiOUB6kosT Sb/ID6n3oAer4OtMyqtAg1zwy+f5kba/+I/qERIlNNRixWuckwKVI4p6aq+ExJO2 hqK37xkFFbaRhLHftx/jU8jEjaAmUJk1HjolSra/Evfq501NtrtqWq6B3E2mNCuK 2KM/V9wnhidYmkDPoTmgadmFpOvJ7bi8zLc6z6XRFc0tGfm8fF2JIWGLwrNqZmV9 ivX7/aMPlsAxdsRqnEocP6RYAqFCApK/oKJTZAOgAj+oi9ACyaZDXqjrOjdxuK3J KYcaV2pEPtz1rbZZzOA3Mw== 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:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1716919284; x= 1717005684; bh=rrE+OjZp1437A9GhfwMsem88cGNA3uyV+nsZgDt11D0=; b=o kN2SqWoK+fcfPWxsySHtal6bjCtXBzdnfgAreA4E8zYiirSS9yb/2EowBlTRpmpa 2b4GVcD2iG2uH55FLmxbV8C8wkjZaOOErJtZhoDb+SB2HEgehcPAD8WeBnnrZvk0 Cpickpydd/7oTM/mDlISK6FseiRbcZrwVJS0R3LuRO0GW/GSKGCFBNbC7h8TcLYV WgDvr0OnLUF3ceOlDqF2+7cuV+VOuSOSLoRRuNN9HGkv455FNSqjuluDxqzGrAFz XVpFJayMaS2YOex1fi10YLHFQM6ZYkDryUCDBNjeaUp1XppKxtNVyoKqU2dWwkuq C0YyHPj79E2j1Y7NFgSQQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdejkedgledvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtje ertddtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhk lhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepiedvhfeihe ehgeeuieeljeeitedtjeehudegfeelkedvleekhedtgfeiffefkedunecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprggurhhirghnrdhklhgrvh gvrhesrghklhgrvhgvrhdrtghomh X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 28 May 2024 14:01:22 -0400 (EDT) Message-ID: <22b7b0b8-c348-44df-a9a4-ceba94f379b2@aklaver.com> Date: Tue, 28 May 2024 11:01:20 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Pgpool with high availability To: vijay patil , pgsql-general@lists.postgresql.org References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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