[pgpool-general: 5283] Re: Starting 2 pgpools at the same time cause duplicate VIP.

[Avi Weinberg]

Hi,

Duplicate VIP occurred on our system again.  I'm sending pgpool.log and pgpool.conf files from both servers.
We have an agent on both machines that monitor the healthiness of pgpool and postgres and brings them up if they fail and alert if database is inaccessible etc.
At 2017-01-26 11:32:09 our agent detected duplicate VIP and restarted pgpools.
We also had the following lines in our system log
2017-01-26 11:32:01: ERROR:  connection to PCP server failed.
2017-01-26 11:32:01: DETAIL:  ERROR: connection to host "172.18.255.42" failed with error "Connection refused"

The agent is running at 1 minute interval on both servers.

Please advise what might be causing it.

Thanks
Avi


From: Muhammad Usama [mailto:m.usama at gmail.com]
Sent: Wednesday, January 25, 2017 11:23 AM
To: Avi Weinberg <AviW at gilat.com>
Cc: pgpool-general at pgpool.net
Subject: Re: [pgpool-general: 5274] Starting 2 pgpools at the same time cause duplicate VIP.



On Tue, Jan 24, 2017 at 6:57 PM, Avi Weinberg <AviW at gilat.com<mailto:AviW at gilat.com>> wrote:
Hi all,

Our setup has two servers each running postgres 9.5.5 and pgpool 3.6.1 .  When we bring up both pgpools at the same exact time we have the VIP on both machines.  If the application is running on a third machine how can we know which of the VIPs it is using so we will be able to restart the other pgpool.

It is not the intended behavior. Can you please share the Pgpool.conf and log files of both Pgpool-II nodes when this issue happens.

Thanks
Best regards
Muhammad Usama


Thanks,
Avi
IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you should not copy or use this e-mail for any purpose nor disclose its contents to any person.

_______________________________________________
pgpool-general mailing list
pgpool-general at pgpool.net<mailto:pgpool-general at pgpool.net>
http://www.pgpool.net/mailman/listinfo/pgpool-general

IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you should not copy or use this e-mail for any purpose nor disclose its contents to any person.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170129/5cb3351a/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool1.log
Type: application/octet-stream
Size: 1065289 bytes
Desc: pgpool1.log
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170129/5cb3351a/attachment-0004.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool2.log
Type: application/octet-stream
Size: 2321975 bytes
Desc: pgpool2.log
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170129/5cb3351a/attachment-0005.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool2.conf
Type: application/octet-stream
Size: 35009 bytes
Desc: pgpool2.conf
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170129/5cb3351a/attachment-0006.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pgpool1.conf
Type: application/octet-stream
Size: 35009 bytes
Desc: pgpool1.conf
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20170129/5cb3351a/attachment-0007.obj>