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 1uU1ey-00EFck-5p for pgsql-general@arkaria.postgresql.org; Tue, 24 Jun 2025 11:17:52 +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 1uU1ev-00Ba61-Fr for pgsql-general@arkaria.postgresql.org; Tue, 24 Jun 2025 11:17:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uTzGx-00AZEx-L5 for pgsql-general@lists.postgresql.org; Tue, 24 Jun 2025 08:44:56 +0000 Received: from mail-io1-xd2c.google.com ([2607:f8b0:4864:20::d2c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uTzGw-003hQD-0U for pgsql-general@postgresql.org; Tue, 24 Jun 2025 08:44:55 +0000 Received: by mail-io1-xd2c.google.com with SMTP id ca18e2360f4ac-86d00ae076dso159826539f.0 for ; Tue, 24 Jun 2025 01:44:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1750754693; x=1751359493; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=+S4wmzmvrA3LgtoovPv1r++nSYSjN93Kah8UTpnFU1s=; b=iR/hkVHawyFjog+lDGRNBMPuyZU5MBl1SOa3kWNbGEBvr+Fgj8jHbbpzJbLLe0EWUT 87qlxdjj11AoeTd8wFqT93q8JqYAnYeF98/uy5AoSxrDzJFvPp8JaCIgl23x882aVVRP eUKh4rJDIpwvLtcEy+UxzUpn8QPxcMtqpiPu69/GFhfHaKH8Pf5zwHtvdhr6L7ZMn5LS KUnWNfQh/oIRIJ62m1UcBAP4FR1NZaQAw8/23uZHgEHRPSY8mcSqpnogwiy/OW0Fw2Pl IePu7yMZvn/+bpVan7jZE1pNbPf9LtU+PbzHk/QMUKE7aztfUTHl9r+YL+LY/kFyb4zx mM/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750754693; x=1751359493; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=+S4wmzmvrA3LgtoovPv1r++nSYSjN93Kah8UTpnFU1s=; b=vba5I6yy9rD2akYWCwmI0IWI4HF7zS+OEsePWPIUnPAS5iXHhOZF7DWGgaYsQEv1s7 u6JdJAipvRnYznka9LWpOnmiYIdFKiFabo7Hac9id6niQtE1MEBwsI5eNHJjhP5CugPB 4v9v7941wo8yU1pVyo4UO4iN+7T8HxArA2pfSi5mVcBVjTkeW2tTqU9F1F5JO8LdIXo4 O+r6XAs6UubOzeviaH0U79jSwQllG9RVJvpamy9Pu3+9gPRL/Vr2rHOzEULxTP04l2Eu mDaa26lj7RrcqSt++dBNxeLoZdSvZD0uV1B4APptohTbmdv32EAAAoxwKPL7hohwudml KAiQ== X-Gm-Message-State: AOJu0Yx08ZJc82pqLqhD7cVtWhZZiOCf6zZ2lgeOKGZc0TsKeMf+QkLo hMGhs434LVeXVyUBqxtamER+zq9vR1neEtWh7RfugUf8xATiJHL8Y/3hX5av+JULvFIySw7uHit tSPpRWtqAGUNT5qdzDij3yM9tUAhAzzSxUF9B X-Gm-Gg: ASbGncs1bSCOu2Qf8mgoCT10cnnenr7hNNdo7oYxktgQ7oGQsxmddBfUTm438fdwQpG ZlOF8ICkabP6jDLnq4X3EQhmYHxnIKok5opM55uibim9RbqyK6jNWZXHyzrHVQlVHnD5aVvAwFD jjNndbpxcv6zfcpf5gSOM5CvhcBmw6iI7ZFoEehc91 X-Google-Smtp-Source: AGHT+IHM01ojTrPXD3ElFFoItJuCSSZxgQBNmA6YHWAhq72QQAc3JntiF2MlTX3tdMwGJXpOlyDZ/bFZNCUz5MnSefg= X-Received: by 2002:a5d:9b88:0:b0:85e:16e9:5e8d with SMTP id ca18e2360f4ac-8765d896c0cmr217641939f.7.1750754693142; Tue, 24 Jun 2025 01:44:53 -0700 (PDT) MIME-Version: 1.0 From: Pablo Calientos Date: Tue, 24 Jun 2025 10:44:42 +0200 X-Gm-Features: AX0GCFudrIvOmNdXhWPMpRaXCEGEsQM45G4ECPc96uPHRZ2QEXh0XUDBUZEtbPk Message-ID: Subject: PGPool II does not recognize backend_server0 To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="00000000000092dee806384d5795" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000092dee806384d5795 Content-Type: text/plain; charset="UTF-8" Hi all, I'm new to pgpool, I'm testing from scratch with version [postgres@pgpool-01 ~]$ pgpool --version pgpool-II version 4.6.2 (chirikoboshi) I'm following the ufficial guide at https://www.pgpool.net/docs/latest/en/html/example-basic.html. I started testing native replication mode, I use this configuration in virtualbox VMs: server pgppol 192.168.1.118 OEL 9.6 server post01 192.168.1.116 OEL 9.6 server post02 192.168.1.117 OEL 9.6 All VMs can ping/telnet between them, from server pgpool I can connect to others postgres server via psql: [postgres@pgpool-01 ~]$ psql -h 192.168.1.116 psql (13.20) Type "help" for help. postgres=# \q [postgres@pgpool-01 ~]$ psql -h 192.168.1.117 psql (13.20) Type "help" for help. postgres=# The relevant parameters in pgpool.conf are the following: backend_clustering_mode = 'native_replication' backend_hostname0 = '192.168.1.116' backend_port0 = 5432 backend_weight0 = 1 backend_data_directory0 = '/PGDATA' backend_application_name0 = 'server0' backend_hostname1 = '192.168.1.117' backend_port1 = 5432 backend_weight1 = 1 backend_data_directory1 = '/PGDATA' backend_application_name1 = 'server1' following the guide I sent creation for a database "test" from pgpool: [postgres@pgpool-01 ~]$ createdb -p 9999 test but the db has been created only in backend_hostname1. IN fact pgpool report as down backend_hostname0: [postgres@pgpool-01 ~]$ psql -h localhost -p 9999 psql (13.20) Type "help" for help. postgres=# show pool_nodes; node_id | hostname | port | status | pg_status | lb_weight | role | pg_role | select_cnt | load_balance_no de | replication_delay | replication_state | replication_sync_state | last_status_change ---------+---------------+------+--------+-----------+-----------+---------+---------+------------+---------------- ---+-------------------+-------------------+------------------------+--------------------- 0 | 192.168.1.116 | 5432 | down | unknown | 0.500000 | replica | replica | 0 | false | 0 | | | 2025-06-19 16:28:12 1 | 192.168.1.117 | 5432 | up | unknown | 0.500000 | main | main | 0 | true | 0 | | | 2025-06-19 16:28:12 (2 rows) But I dont see errors in configuration. If I change the backend server, switching the IP addresses (to be sure there are not network or access misconfiguration) the server down results always the same backend_hostname0, I mean the problem is not in the postgres server (changing IP does not change the status of show pool_nodes): new configurazion: backend_hostname0 = '192.168.1.117' <<< switched IP backend_port0 = 5432 backend_weight0 = 1 backend_data_directory0 = '/PGDATA' backend_application_name0 = 'server0' backend_hostname1 = '192.168.1.116' <<< switched IP backend_port1 = 5432 backend_weight1 = 1 backend_data_directory1 = '/PGDATA' backend_application_name1 = 'server1' reboot pgpopol and resent show pool_nodes: [postgres@pgpool-01 ~]$ pgpool stop 2025-06-19 16:44:23.112: main pid 6247: LOG: stop request sent to pgpool (pid: 6124). waiting for termination... .done. [1]+ Done pgpool -n [postgres@pgpool-01 ~]$ pgpool -n & [1] 6248 [postgres@pgpool-01 ~]$ 2025-06-19 16:44:31.934: main pid 6248: LOG: reading status file: 0 th backend is set to down status 2025-06-19 16:44:31.934: main pid 6248: LOG: reading status file: 1 th backend is set to up status 2025-06-19 16:44:31.935: main pid 6248: LOG: redirecting log output to logging collector process 2025-06-19 16:44:31.935: main pid 6248: HINT: Future log output will appear in directory "/var/log/pgpool_log". [postgres@pgpool-01 ~]$ psql -h localhost -p 9999 psql (13.20) Type "help" for help. postgres=# show pool_nodes; node_id | hostname | port | status | pg_status | lb_weight | role | pg_role | select_cnt | load_balance_no de | replication_delay | replication_state | replication_sync_state | last_status_change ---------+---------------+------+--------+-----------+-----------+---------+---------+------------+---------------- ---+-------------------+-------------------+------------------------+--------------------- 0 | 192.168.1.117 | 5432 | down | unknown | 0.500000 | replica | replica | 0 | false | 0 | | | 2025-06-19 16:44:31 1 | 192.168.1.116 | 5432 | up | unknown | 0.500000 | main | main | 0 | true | 0 | | | 2025-06-19 16:44:31 (2 rows) postgres=# I cannot understand what I'm missing. Any advice is welcome. thanks in advance. MP --00000000000092dee806384d5795 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi all,
I'm new to pgpool, I'm testing from scratch = with version
[postgres@pgpool-01 ~]$ pgpool --version
pgpool-II vers= ion 4.6.2 (chirikoboshi)

I'm following the ufficial guide at http= s://www.pgpool.net/docs/latest/en/html/example-basic.html.
I started= testing native replication mode, I use this configuration in virtualbox VM= s:

server pgppol 192.168.1.118 OEL 9.6
server post01 192.168.1.1= 16 OEL 9.6
server post02 192.168.1.117 OEL 9.6

All VMs can ping= /telnet between them, from server pgpool I can connect to others postgres s= erver via psql:

[postgres@pgpool-01 ~]$ psql -h 192.168.1.116
psq= l (13.20)
Type "help" for help.

postgres=3D# \q
[pos= tgres@pgpool-01 ~]$ psql -h 192.168.1.117
psql (13.20)
Type "hel= p" for help.

postgres=3D#

The relevant parameters in pgp= ool.conf are the following:

backend_clustering_mode =3D 'native_= replication'

backend_hostname0 =3D '192.168.1.116'
ba= ckend_port0 =3D 5432
backend_weight0 =3D 1
backend_data_directory0 = =3D '/PGDATA'
backend_application_name0 =3D 'server0'
backend_hostname1 =3D '192.168.1.117'
backend_port1 =3D 543= 2
backend_weight1 =3D 1
backend_data_directory1 =3D '/PGDATA'=
backend_application_name1 =3D 'server1'

following the gu= ide I sent creation for a database "test" from pgpool:

[po= stgres@pgpool-01 ~]$ createdb -p 9999 test

but the db has been creat= ed only in backend_hostname1.
IN fact pgpool report as down backend_host= name0:


[postgres@pgpool-01 ~]$ psql -h localhost -p 9999
psql= (13.20)
Type "help" for help.

postgres=3D# show pool_n= odes;
node_id | hostname | port | status | pg_status | lb_weight |= role | pg_role | select_cnt | load_balance_no
de | replication_delay= | replication_state | replication_sync_state | last_status_change
-----= ----+---------------+------+--------+-----------+-----------+---------+----= -----+------------+----------------
---+-------------------+------------= -------+------------------------+---------------------
0 | 192.16= 8.1.116 | 5432 | down | unknown | 0.500000 | replica | replica | 0 = | false
| 0 | | = | 2025-06-19 16:28:12
1 | 192.168.1.117 | 5432 | up = | unknown | 0.500000 | main | main | 0 | true
| 0 = | | | 2025-06-19 1= 6:28:12
(2 rows)


But I dont see errors in configuration. If I= change the backend server, switching the IP addresses (to be sure there ar= e not
network or access misconfiguration) the server down results always= the same backend_hostname0, I mean the problem is not in
the postgres = server (changing IP does not change the status of show pool_nodes):

= new configurazion:

backend_hostname0 =3D '192.168.1.117' &l= t;<< switched IP
backend_port0 =3D 5432
backend_weight0 =3D 1backend_data_directory0 =3D '/PGDATA'
backend_application_name= 0 =3D 'server0'

backend_hostname1 =3D '192.168.1.116'= ; <<< switched IP
backend_port1 =3D 5432
backend_weight1 = =3D 1
backend_data_directory1 =3D '/PGDATA'
backend_applicati= on_name1 =3D 'server1'

reboot pgpopol and resent show pool_n= odes:

[postgres@pgpool-01 ~]$ pgpool stop
2025-06-19 16:44:23.112= : main pid 6247: LOG: stop request sent to pgpool (pid: 6124). waiting for= termination...
.done.
[1]+ Done pgpool -n
[postgres@pgpool-01 ~]$ pgpool -n &
[1] 6248
[postgres@pgpool-01= ~]$ 2025-06-19 16:44:31.934: main pid 6248: LOG: reading status file: 0 t= h backend is set to down status
2025-06-19 16:44:31.934: main pid 6248: = LOG: reading status file: 1 th backend is set to up status
2025-06-19 1= 6:44:31.935: main pid 6248: LOG: redirecting log output to logging collect= or process
2025-06-19 16:44:31.935: main pid 6248: HINT: Future log out= put will appear in directory "/var/log/pgpool_log".

[postg= res@pgpool-01 ~]$ psql -h localhost -p 9999
psql (13.20)
Type "h= elp" for help.

postgres=3D# show pool_nodes;
node_id | ho= stname | port | status | pg_status | lb_weight | role | pg_role | sel= ect_cnt | load_balance_no
de | replication_delay | replication_state | r= eplication_sync_state | last_status_change
---------+---------------+---= ---+--------+-----------+-----------+---------+---------+------------+-----= -----------
---+-------------------+-------------------+----------------= --------+---------------------
0 | 192.168.1.117 | 5432 | down = | unknown | 0.500000 | replica | replica | 0 | false
| 0 = | | | 2025-06-19 1= 6:44:31
1 | 192.168.1.116 | 5432 | up | unknown | 0.500000 = | main | main | 0 | true
| 0 | = | | 2025-06-19 16:44:31
(2 rows)
<= br>postgres=3D#

I cannot understand what I'm missing.
Any adv= ice is welcome.

thanks in advance.

MP

--00000000000092dee806384d5795--