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 1uURWc-003MJJ-40 for pgsql-general@arkaria.postgresql.org; Wed, 25 Jun 2025 14:54:58 +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 1uURWa-004Ly5-6m for pgsql-general@arkaria.postgresql.org; Wed, 25 Jun 2025 14:54:56 +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 1uURWZ-004Lxv-RE for pgsql-general@lists.postgresql.org; Wed, 25 Jun 2025 14:54:56 +0000 Received: from mail-io1-xd2a.google.com ([2607:f8b0:4864:20::d2a]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uURWY-0043BX-08 for pgsql-general@postgresql.org; Wed, 25 Jun 2025 14:54:56 +0000 Received: by mail-io1-xd2a.google.com with SMTP id ca18e2360f4ac-87653e3adc6so94604239f.3 for ; Wed, 25 Jun 2025 07:54:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750863292; x=1751468092; darn=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=q/UfZZztLW89iglCW0xgHsuwwfCi7Xx0+eqJUcB0V74=; b=kqpu6HrB9DWBYBZ6MiX9CfFVEzuASi5kWLy58h8ownCNRi80xlQ+wfr9Y9ZuKPAQST LlyDi43GiGoV8dk7NAvTS7f9/c55dO2WJkmVKhwklfnqQGs4zZzslwyKKuBb/9fJJdwb 61bmC3159lQez/xLFuFiKehKGpEha9ax0O4L8amwijGnzHToGRnGOuK7MNnWC8ioG5sm NuVDl0UaxATGN5WDWp/xEvfD4A9SOKzf8CZ+DT51raBzr+WvXbe2l6M8hCuP95/coVga O7J1dFxsefCRKui0ywhCltW49io459EhmhlAmaWbIYhK/SKsIMUtdW8Lf/26SXmazZy7 H8uw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750863292; x=1751468092; 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=q/UfZZztLW89iglCW0xgHsuwwfCi7Xx0+eqJUcB0V74=; b=wygNPukTUPBPRae2dEmTWjC7JKOo2DNwxLp0aejB6O/oqCPtM0ftl+qcg2TeMeUBgA OR0CQarbgWtOSOvO8gdZi+0evDgEWGGMAynPZCjsqtz9VTQQkWaVohg4kIAcsK0w4+EL CR5wm/6NY/2KEbZiEQDL1ddyu10a1MndJVdqq70Q0C0hfJ5jbh0ZY3X8MSKdC9uPqE+S LkOLpzQEBwD8ANdz/6D6Qp0/FJCnKwZl6aJRuWIdyeE7hrwGLeH8Yrhnz2AqpDNWu3fH EARZO5I5vgK0RX91DNt3M0ciBBLHM/uOu0eNJ4Ggja40zEoAMdnWthIBDuodppDOZcXj hkYg== X-Gm-Message-State: AOJu0Yy/uMmLZiObGL1AUTnj4/RD825H0cCwW+TgFAd3UyQW1YbCCIDK Mlxd499jl2f9csNJaxBRmT857W9WWE7GkseqvxCiVdhD1V4UJ3IdTtbQPcaQeGF9US2SpyHtwn9 zT3xuEGsHICC3I5UfRz1k3XyhsdwX5VhDGLwqx5EFTQ== X-Gm-Gg: ASbGncvVI+KAF1/fX7s676WtA89cjbIUV12jQ9mdwn2zNQEKlOs+V5BQDh6v0/vbkzF MVhjcsS8cFC9Q+enj8gmPJxbdrPVdsfT/cW2JkG3sPnash1bC/JvpUmM/VhrS8dRGhGjTVRoUmu 175D9+VJ7WfmYCMoyHhYUss43djiemWx3/ppJKWGdDhEyE/nnLThiEacQqcyQIsfXlZVsDGdRz0 yubtR+U9AdMzaHa X-Google-Smtp-Source: AGHT+IHcXEg8wr/BJWiEJIVYQvMSyBbx3mgM5kjfNnXtD1vIflw1aaQdHa13hmGmnCUvjHA91wG/n2hCkh5yFvWMY8U= X-Received: by 2002:a05:6e02:23c5:b0:3df:3271:6aba with SMTP id e9e14a558f8ab-3df329c70d9mr43376235ab.15.1750863292004; Wed, 25 Jun 2025 07:54:52 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Wed, 25 Jun 2025 10:54:14 -0400 X-Gm-Features: Ac12FXzLCM3Slc-x9x6LTyr3Ecd21AVc6zViY5BczfwMujRzzM2p7Bz3uHVpx9g Message-ID: Subject: Re: PGPool II does not recognize backend_server0 To: Pablo Calientos Cc: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="00000000000091fda6063866a041" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000091fda6063866a041 Content-Type: text/plain; charset="UTF-8" Basic debugging: Try looking at each node more closely with pcp_node_info https://www.pgpool.net/docs/latest/en/html/pcp-node-info.html Also make sure you are always using health_check https://www.pgpool.net/docs/latest/en/html/runtime-config-health-check.html Specific debugging: 2025-06-19 16:44:31.934: main pid 6248: LOG: reading status file: 1 th > backend is set to up status This would seem to indicate it's reading cached info about the state of the node, so you may need to remove the pgpool_status file. You can also tell pgpool to ignore it on startup via the -D or --discard-status flag. Hope that helps, Greg -- Crunchy Data - https://www.crunchydata.com Enterprise Postgres Software Products & Tech Support --00000000000091fda6063866a041 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Basic debugging:

Try looking at each node more closely with pcp_node_info

https://www.pgpool.net/docs/latest/en/html/pcp-node-info.html

Also make sure you are always using health_check


Specific debuggi= ng:

2025-06-19 16:44:31.934: main pid 6248: LOG: reading status file: 1 th= backend is set to up status

This wou= ld seem to indicate it's reading cached info about the state of the nod= e, so you may need to remove the pgpool_status file. You=C2=A0can also tell= pgpool to ignore it on startup via the=C2=A0 -D or --discard-status flag.<= /div>

Hope that helps,
Greg


--
Enterpri= se Postgres Software Products & Tech Support

=
--00000000000091fda6063866a041--