View Issue Details

IDProjectCategoryView StatusLast Update
0000429Pgpool-IIBugpublic2018-09-18 11:43
Reportersandesh.lal Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status closedResolutionopen 
Product Version3.7.2 
Summary0000429: FATAL: Add to watchdog cluster request is rejected by node
DescriptionI have 2 nodes in my PGPOOL cluster. When I try to start the second node, I get an error and pgpool shuts down.

FATAL: Add to watchdog cluster request is rejected by node

Need help to resolve

Regards
Additional InformationThe log entry is as follows:

Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: WARNING: checking setuid bit of if_up_cmd
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: DETAIL: ifup[/sbin/ip] doesn't have setuid bit
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: WARNING: checking setuid bit of if_down_cmd
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: DETAIL: ifdown[/sbin/ip] doesn't have setuid bit
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: WARNING: checking setuid bit of arping command
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: DETAIL: arping[/usr/sbin/arping] doesn't have setuid bit
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: LOG: waiting for watchdog to initialize
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: LOG: setting the local watchdog node name to "server2.abc.com:9999 Linux server2.abc.com"
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: LOG: watchdog cluster is configured with 1 remote nodes
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: LOG: watchdog remote node:0 on server1.abc.com:9000
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: LOG: interface monitoring is disabled in watchdog
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: LOG: watchdog node state changed from [DEAD] to [LOADING]
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: LOG: new outbound connection to server1.abc.com:9000
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: FATAL: Add to watchdog cluster request is rejected by node "server1.abc.com:9000"
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: HINT: check the watchdog configurations.
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9770: LOG: Watchdog is shutting down
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: LOG: watchdog child process with pid: 9770 exits with status 768
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9767: FATAL: watchdog child process exit with fatal error. exiting pgpool-II
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9772: LOG: setting the local watchdog node name to "server2.abc.com:9999 Linux server2.abc.com"
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9772: LOG: watchdog cluster is configured with 1 remote nodes
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9772: LOG: watchdog remote node:0 on server1.abc.com:9000
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9772: LOG: interface monitoring is disabled in watchdog
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9772: LOG: watchdog node state changed from [DEAD] to [LOADING]
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9772: LOG: new outbound connection to server1.abc.com:9000
Sep 02 11:38:10 server2.abc.com pgpool[9767]: 2018-09-02 11:38:10: pid 9772: LOG: Watchdog is shutting down
Sep 02 11:38:10 server2.abc.com systemd[1]: pgpool.service: main process exited, code=exited, status=3/NOTIMPLEMENTED
Sep 02 11:38:10 server2.abc.com pgpool[9773]: 2018-09-02 11:38:10: pid 9773: FATAL: could not read pid file
Sep 02 11:38:10 server2.abc.com systemd[1]: pgpool.service: control process exited, code=exited status=3
Sep 02 11:38:10 server2.abc.com systemd[1]: Unit pgpool.service entered failed state.
Sep 02 11:38:10 server2.abc.com systemd[1]: pgpool.service failed.
TagsNo tags attached.

Activities

pengbo

2018-09-05 17:58

developer   ~0002179

Could you share pgpool.conf?

sandesh.lal

2018-09-06 20:12

reporter   ~0002180

please find attached the pgpool.conf from the server that fails to join the cluster.
pgpool.conf (40,850 bytes)

sandesh.lal

2018-09-09 02:26

reporter   ~0002181

I have resolved the issue. It was coming because the Master node had the standby nodes name entered in CAPS while other places it is configured in small. Linux being case sensitive was having some conflict because of this and would not allow the server to join the watchdog cluster.

After fixing all the names across the board. it worked fine.

Regards

Issue History

Date Modified Username Field Change
2018-09-04 17:33 sandesh.lal New Issue
2018-09-05 17:58 pengbo Note Added: 0002179
2018-09-06 20:12 sandesh.lal File Added: pgpool.conf
2018-09-06 20:12 sandesh.lal Note Added: 0002180
2018-09-09 02:26 sandesh.lal Note Added: 0002181
2018-09-11 13:28 t-ishii Status new => resolved
2018-09-18 11:43 administrator Status resolved => closed