[pgpool-general: 8456] DETAIL: changing the state to in network trouble

Marco Ferrara m.ferrara at oppent.it
Thu Oct 13 19:47:36 JST 2022


Hello everyone,
I have configured the PgPool 4.1.13 cluster with three servers using PostgreSQL 13 following the guide https://www.pgpool.net/docs/41/en/html/example-cluster.html. After various problems with configuring the virtual ip it now assigns the ip but after a while it goes "in network trouble" and the cluster loses the network connection. When I was not assigning the virtual ip the cluster was up and seemed to work.

The pgpool log:

Oct 13 12:04:24 sv25244 pgpool[1009552]: [26-1] 2022-10-13 12:04:24: pid 1009552: LOG:  new IPC connection received
Oct 13 12:04:24 sv25244 postgres[1009668]: if-up.sh: start: trying to assign 192.168.1.10/24 to 'System ens192'
Oct 13 12:04:24 sv25244 pgpool[1009552]: [27-1] 2022-10-13 12:04:24: pid 1009552: WARNING:  network IP is removed and system has no IP is assigned
Oct 13 12:04:24 sv25244 pgpool[1009552]: [27-2] 2022-10-13 12:04:24: pid 1009552: DETAIL:  changing the state to in network trouble
Oct 13 12:04:24 sv25244 pgpool[1009552]: [28-1] 2022-10-13 12:04:24: pid 1009552: LOG:  waiting for escalation process to exit before starting de-escalation
Oct 13 12:04:24 sv25244 postgres[1009697]: if-up.sh: Command completed with 0
Oct 13 12:04:25 sv25244 pgpool[1009552]: [29-1] 2022-10-13 12:04:25: pid 1009552: LOG:  waiting for escalation process to exit before starting de-escalation
Oct 13 12:04:26 sv25244 pgpool[1009552]: [30-1] 2022-10-13 12:04:26: pid 1009552: LOG:  waiting for escalation process to exit before starting de-escalation
Oct 13 12:04:26 sv25244 pgpool[1009666]: [25-1] 2022-10-13 12:04:26: pid 1009666: LOG:  successfully acquired the delegate IP:"192.168.1.10"
Oct 13 12:04:26 sv25244 pgpool[1009666]: [25-2] 2022-10-13 12:04:26: pid 1009666: DETAIL:  'if_up_cmd' returned with success
Oct 13 12:04:26 sv25244 pgpool[1009552]: [31-1] 2022-10-13 12:04:26: pid 1009552: LOG:  waiting for escalation process to exit before starting de-escalation
Oct 13 12:04:26 sv25244 pgpool[1009552]: [32-1] 2022-10-13 12:04:26: pid 1009552: LOG:  watchdog escalation process with pid: 1009666 exit with SUCCESS.
Oct 13 12:04:27 sv25244 pgpool[1009552]: [33-1] 2022-10-13 12:04:27: pid 1009552: LOG:  watchdog node state changed from [MASTER] to [IN NETWORK TROUBLE]
Oct 13 12:04:27 sv25244 pgpool[1009552]: [34-1] 2022-10-13 12:04:27: pid 1009552: FATAL:  system has lost the network


Thank you very much,
Marco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pgpool.net/pipermail/pgpool-general/attachments/20221013/9ca79054/attachment.htm>


More information about the pgpool-general mailing list