[pgpool-general: 4926] Re: PGPOOL 3.5.3 - Duplicate IP

[Shay Cohavi]

Hi,
thanks for the reply, the problem does not related to the warning massages
(its another issue) but related to an existing bug which the delegate IP in
not being shutdown after de-escalation function!
http://www.sraoss.jp/pipermail/pgpool-hackers/2016-August/001742.html

Thanks again,
cohavisi

On Mon, Aug 15, 2016 at 12:52 AM, Daniel Huhardeaux <tech at tootai.net> wrote:

> Hello
>
> Le 14/08/2016 à 17:24, Shay Cohavi a écrit :
> [...]
>
>>
>>
>> DUPLICATE IP
>>
>>  3. the “first” master node (mgrdb84) declare that *"we have not
>>     received a beacon message from master node "Linux_mgrdb85_9999" and
>>     it has not replied to our info request”* and *"re-initializing the
>>     cluster”* which demote its state into [STANDBY] mode but the
>>     delegate ip is not being shut down (if_down)!!
>>
> [...]
>
> Answer is in  your logs
>
> 016-08-14 18:01:39: pid 2086: WARNING:  watchdog failed to bring up
> delegate IP, 'if_up_cmd' failed
> 2016-08-14 18:01:39: pid 2086: LOCATION:  wd_if.c:142
> 2016-08-14 18:01:39: pid 2086: WARNING:  watchdog de-escalation failed to
> bring down delegate IP
> 2016-08-14 18:01:39: pid 2086: LOCATION:  wd_escalation.c:140
>
> Please check your configuration.
>
> --
> TOOTAi Networks
> _______________________________________________
> pgpool-general mailing list
> pgpool-general at pgpool.net
> http://www.pgpool.net/mailman/listinfo/pgpool-general
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20160818/64bccc76/attachment.html>