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 1sCK4x-004nyi-Kg for pgsql-general@arkaria.postgresql.org; Wed, 29 May 2024 14:15:01 +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 1sCK4x-00FP9P-7i for pgsql-general@arkaria.postgresql.org; Wed, 29 May 2024 14:14:59 +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 1sCK4w-00FP9H-9e for pgsql-general@lists.postgresql.org; Wed, 29 May 2024 14:14:58 +0000 Received: from wfout5-smtp.messagingengine.com ([64.147.123.148]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sCK4s-001MSL-AV for pgsql-general@lists.postgresql.org; Wed, 29 May 2024 14:14:57 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfout.west.internal (Postfix) with ESMTP id 643251C000E1; Wed, 29 May 2024 10:14:51 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Wed, 29 May 2024 10:14:51 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc: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=1716992091; x=1717078491; bh=AaBnIBdjJFPx+eJpvBWlSbSQWR3JU7rGwVV1hoklcrM=; b= RlSgUlsr/ROpBo8zsxFxm1Fhku6azbyIxgkMDoPy3/msv/9DE3nf4LsF1vrItf/7 UHsg4vy93l8f84pREI9qhFRiPqRqJ2d2zgRIXrJ5DSDm2iswbSrbCvysYJ56+WeA qxbjWph0EEZZPsFK/JrCeNR+zPWkAf2Idk0jqs5HxmNMfuhMOc+Jt0N0b3r2t11e CkGWvs+KNWZBTlxc/oBQaPzKTMnwBOEthlP9i8rDmle9K76lmY0OTcmOz5Kn1EHY 2A4aMZn2D5Poi9/4mFx7KZA+KgQoAWAYotgiOKPDmiWd4sx+6yeRBQzzurc9Us4x 3MCBz9IgHpq7urW4vjeRJQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc: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=1716992091; x= 1717078491; bh=AaBnIBdjJFPx+eJpvBWlSbSQWR3JU7rGwVV1hoklcrM=; b=h LjhEuSvvOYBUdVygcWEnU6PJcrQqHRQXQ9dHFGf/Ftl2SiRbz4e3I5HeWF4mjdZO WsMOGUw9W79ImRYlxtYjLdnDkCzV6deZKpZRYQW5m0vJyParUgZHxVafS3POS5g/ SP8wMSaMXLmP54bYMBi7Iyfeb4TAySuwVg9VV7JMWZ9JeRpoD14VX5z4VA/DmuCa S/u0G/SM8KmNY3yGWl9kA6c/WZGxul7N8r2vE/kdHp4/SCAUE2hFeLnh3i19Uwyx qzOmC8C7pDh+IUGYCmVNqMh8ul2411r0hPqyJyOr2G0lKbhSI10yO0kvYYkKSmy1 zKsfYNJLjlCBiH9nGI1dg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdekuddgjeefucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfevfhfhjggtgfesth ekredttddvjeenucfhrhhomheptegurhhirghnucfmlhgrvhgvrhcuoegrughrihgrnhdr khhlrghvvghrsegrkhhlrghvvghrrdgtohhmqeenucggtffrrghtthgvrhhnpeefgeefie eutdfggfetgefgheekjeehteeileeigfetieekjedvieeviefgheevtdenucevlhhushht vghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrg hvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 29 May 2024 10:14:50 -0400 (EDT) Message-ID: Date: Wed, 29 May 2024 07:14:49 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Pgpool with high availability To: vijay patil Cc: pgsql-general@lists.postgresql.org References: <22b7b0b8-c348-44df-a9a4-ceba94f379b2@aklaver.com> Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/28/24 22:15, vijay patil wrote: > Hi Adrian, > > After modifying the pgpool.conf configuration to correct a subnet > mistake,  Previously, the wrong subnet was specified as /26, and it has > now been corrected to /24. The configuration changes were as follows: This seems to be a networking issue: [root@staging-ha0001 ~]# ping 10.127.1.18 PING 10.127.1.18 (10.127.1.18) 56(84) bytes of data. From 10.127.1.10 icmp_seq=1 Destination Host Unreachable <...> Where are ha0001 and ha0003 on the network relative to ha0002? Also are they reachable for other services? -- Adrian Klaver adrian.klaver@aklaver.com