[pgpool-general: 5119] Problem with watchdog in 3.5

[Piotr Gbyliczek]

Hi, 

I'm trying to set up pgpool with watchdog for IP control. I have two servers 
with streaming replication set up and want just floating IP, so disabled 
pooling and load balancing, left only replication on with type stream. 

As far as I can see, the only difference between my config files are below : 


[root at pgsql95_1 ~]# diff pgpool-1.conf pgpool-2.conf
482c482
< wd_hostname = 'pgsql95_1'
---
> wd_hostname = 'pgsql95_2'
569c569
< heartbeat_destination0 = 'pgsql95_2'
---
> heartbeat_destination0 = 'pgsql95_1'
610c610
< other_pgpool_hostname0 = 'pgsql95_2'
---
> other_pgpool_hostname0 = 'pgsql95_1'

Both hostnames are in hosts file on both servers, and backends are recognised 
fine (running on same two servers as pgpool). When I try to start pgpool 
service on second server (regardless which one that would be, second in 
starting sequence ), I'm getting rejecdet, error suggesting that config of 
watchdog on the secondary server is wrong. 

Any idea onto how I can find out more about what it is it thinks is wrong ? 
Do I need anything else, like PCP password set up for that ? 

I have 3.4 setup working while configured about the same way, so bit confused 
as to why this is not working.

Regards,
Piotr

Piotr Gbyliczek
Solutions Engineer

Node4 Ltd Innovation House, Cafferata Way, Newark, NG24 2TN
ddi. 08454 210444 | t. 0845 421 0444
e. P.Gbyliczek at node4.co.uk



Node4 Limited is registered in England No: 04759927 and has its registered office at Millennium Way, Pride Park, Derby, DE24 8HZ
The information contained in this email is confidential and is intended for the exclusive use of the email addressee shown.
If you are not the addressee, any disclosure, reproduction, distribution or other dissemination or use of this communication is strictly prohibited.
If you have received this mail in error, please notify our mail manager at abuse at node4.co.uk and delete it from your system.
Opinions expressed in this email are those of the individual not the company, unless specifically indicated to that effect.

This email has been scanned inbound by Node4's Email Security System.

This email message has been delivered safely and archived online by Mimecast.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161111/6e9a7ed6/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 116111117215502005.png
Type: image/png
Size: 1315 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161111/6e9a7ed6/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 116111117215502205.png
Type: image/png
Size: 16168 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161111/6e9a7ed6/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 116111117215502505.png
Type: image/png
Size: 19451 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161111/6e9a7ed6/attachment-0008.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 116111117215502705.png
Type: image/png
Size: 17391 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161111/6e9a7ed6/attachment-0009.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 116111117215502905.png
Type: image/png
Size: 16076 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161111/6e9a7ed6/attachment-0010.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 116111117215503205.png
Type: image/png
Size: 16233 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20161111/6e9a7ed6/attachment-0011.png>