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 1vG6qb-0082sE-Pw for pgpool-general@arkaria.postgresql.org; Tue, 04 Nov 2025 02:32:37 +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 1vG6qZ-00AdNY-OR for pgpool-general@arkaria.postgresql.org; Tue, 04 Nov 2025 02:32:34 +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 1vG6qZ-00AdNR-HG for pgpool-general@lists.postgresql.org; Tue, 04 Nov 2025 02:32:34 +0000 Received: from meldrar.postgresql.org ([2a02:c0:301:0:ffff::31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vG6qW-005r07-07 for pgpool-general@lists.postgresql.org; Tue, 04 Nov 2025 02:32:34 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Content-Transfer-Encoding:Content-Type: Mime-Version:References:In-Reply-To:From:Subject:Cc:To:Message-Id:Date:Sender :Reply-To:Content-ID:Content-Description; bh=0epGS+Hs8gZG8xVN4uEilLPJ5IIP0ifJhGgPrODrrwo=; b=koJq4vx+U9jho8ykuJT1h/8ORo i1SMA7jB9AwHagA6vKZKBcHhX1ILk+MZERhqiwufmc9PzBE9eemY2l2uyMyvJDSvMU9SWxIzuu//r uA0Z99JJSFJLo+ei+KJoExeJx7coSZ+mer6ITs8B283e/vTXYAZdObljB+SN6fhWEfWyU9DDGnFgH Ta3yBmzSinKV8hf5heYpWm36uuEffFw03j9UDQz6n+t0e2S7OYJM4rAy1Ao0PzfLhauD66xVz8yDW KvOqNtEYiNWrZ0hpGCANsPCpEt4d1pgAH2h5unq4v1upd0hAP6PJkpuooGeJn6CetKr2vdwdimU8M ousOxZnQ==; Received: from [2409:11:4120:300:a81e:2ce3:7210:2a85] (helo=localhost) by meldrar.postgresql.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vG6qT-00E5Gu-1x; Tue, 04 Nov 2025 02:32:31 +0000 Date: Tue, 04 Nov 2025 11:32:19 +0900 (JST) Message-Id: <20251104.113219.411936663096048386.ishii@postgresql.org> To: fluca1978@gmail.com Cc: pgpool-general@lists.postgresql.org Subject: Re: rebooting a standby causes it go down on pgpool side From: Tatsuo Ishii In-Reply-To: References: X-Mailer: Mew version 6.8 on Emacs 29.3 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Host-Lookup-Failed: Reverse DNS lookup failed for 2409:11:4120:300:a81e:2ce3:7210:2a85 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > Hi all, > I've three identical machines, running pgpool 4.6.2, postgres 17, one > primary (pg1) and two standby pg2 and pg3. > > The initial situation is: > > % ssh pg1 'sudo -u postgres pcp_node_info -U pgpool' > pg1 5432 1 0.166667 waiting up primary primary 0 none none 2025-10-30 11:01:05 > pg2 5432 1 0.333333 waiting up standby standby 0 streaming async > 2025-10-30 11:01:05 > pg3 5432 1 0.500000 waiting up standby standby 0 streaming async > 2025-10-30 11:01:05 > > > % ssh pg2 'sudo -u postgres pcp_node_info -U pgpool' > pg1 5432 1 0.166667 waiting up primary primary 0 none none 2025-10-30 11:01:10 > pg2 5432 1 0.333333 waiting up standby standby 0 streaming async > 2025-10-30 11:01:10 > pg3 5432 1 0.500000 waiting up standby standby 0 streaming async > 2025-10-30 11:01:10 > > % ssh pg3 'sudo -u postgres pcp_node_info -U pgpool' > pg1 5432 1 0.166667 waiting up primary primary 0 none none 2025-10-30 11:01:10 > pg2 5432 1 0.333333 waiting up standby standby 0 streaming async > 2025-10-30 11:01:10 > pg3 5432 1 0.500000 waiting up standby standby 0 streaming async > 2025-10-30 11:01:10 > > > I don't know why, the machines are reported as "waiting up" even if > eveything is working fine and I've waited several minutes without > having any change in the status.