<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">In addition I can state, that sometimes
when Active gets disconnected, the Standby takes over the IP
successfully. It happens to work fine. If you read <br>
<li><a
href="http://www.sraoss.jp/pipermail/pgpool-general/2015-May/003777.html">[pgpool-general:
3724] delegate ip lost</a></li>
the case described there is based on the successful IP switch.
Unfortunately, successful IP switch seems to be rather rare -
usually I see the situation as described below. When it happens
only manual restart on both machines helps.<br>
<br>
J.<br>
<br>
On 20.05.2015 13:54, Janusz Borkowski wrote:<br>
</div>
<blockquote cite="mid:555C75D9.40600@infobright.com" type="cite">
<pre wrap="">Hi!
I use pgpool 3.4.2-1
When the Active host 0 (.189) gets its network disconnected, the Standby host 1 (.188) does not switch the delegate IP. Standby watchdog does not realize that Active is not available:
[root@ib-wawa-188 ~]# pcp_watchdog_info 2 192.168.10.188 9898 admin pgpool 0
192.168.10.189 9999 9000 3
In the Standby logs I see repeating every few seconds indefinitely:
May 20 13:22:30 localhost pgpool: 2015-05-20 13:22:30: pid 1229: DEBUG: watchdog heartbeat: send heartbeat signal to 192.168.10.189:9694
May 20 13:22:32 localhost pgpool[902]: [5430-1] 2015-05-20 13:22:32: pid 902: LOG: failed to create watchdog sending socket
May 20 13:22:32 localhost pgpool[902]: [5430-2] 2015-05-20 13:22:32: pid 902: DETAIL: connect() reports failure "No route to host"
May 20 13:22:32 localhost pgpool[902]: [5430-3] 2015-05-20 13:22:32: pid 902: HINT: You can safely ignore this while starting up.
May 20 13:22:32 localhost pgpool[902]: [5431-1] 2015-05-20 13:22:32: pid 902: LOG: watchdog sending packet for nodes
May 20 13:22:32 localhost pgpool[902]: [5431-2] 2015-05-20 13:22:32: pid 902: DETAIL: packet for "192.168.10.189:9000" is canceled
May 20 13:22:32 localhost pgpool: 2015-05-20 13:22:32: pid 902: LOG: failed to create watchdog sending socket
May 20 13:22:32 localhost pgpool: 2015-05-20 13:22:32: pid 902: DETAIL: connect() reports failure "No route to host"
May 20 13:22:32 localhost pgpool: 2015-05-20 13:22:32: pid 902: HINT: You can safely ignore this while starting up.
May 20 13:22:32 localhost pgpool: 2015-05-20 13:22:32: pid 902: LOG: watchdog sending packet for nodes
May 20 13:22:32 localhost pgpool: 2015-05-20 13:22:32: pid 902: DETAIL: packet for "192.168.10.189:9000" is canceled
Is it known that watchdog failover does not work when network connection to Active gets down?
J.
_______________________________________________
pgpool-general mailing list
<a class="moz-txt-link-abbreviated" href="mailto:pgpool-general@pgpool.net">pgpool-general@pgpool.net</a>
<a class="moz-txt-link-freetext" href="http://www.pgpool.net/mailman/listinfo/pgpool-general">http://www.pgpool.net/mailman/listinfo/pgpool-general</a>
</pre>
</blockquote>
<br>
</body>
</html>