<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif">Alexandru,<br><br></div><div class="gmail_default" style="font-family:georgia,serif">I had faced the same problem. During initial setup, when you first start the pgpool master keep use_watchdog=off. Start the master. On pgpool slave, keep use_watchdog=on. Start pgpool slave.<br>
<br></div><div class="gmail_default" style="font-family:georgia,serif">Now stop pgpool master. Make use_watchdog=on on master pgpool and start again. Restart the slave pgpool to make the other pgpool the master.<br>
<br></div><div class="gmail_default" style="font-family:georgia,serif">Let me know if that helps.<br><br></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><span style="color:rgb(68,68,68)"><font face="georgia,serif">Regards,<br>
</font></span></div><font face="georgia,serif"><span style="color:rgb(68,68,68)">Granthana</span><br></font></div></div>
<br><br><div class="gmail_quote">On Tue, Apr 8, 2014 at 1:45 AM, Alexandru Cardaniuc <span dir="ltr"><<a href="mailto:cardaniuc@gmail.com" target="_blank">cardaniuc@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div>Hi,<br><br><br></div><div>Is pgpool 3.3.3 having a watchdog problem?<br><br></div><div>I have a 2 node cluster.<br></div><div>pgpool on 10.0.90.11<br></div><div>pgpool on 10.0.90.12<br></div><div>delegate_IP = 10.0.90.1 and was set on primary pgpool (10.0.90.11)<br>
</div><div>now both pgpool have the delegate_IP up:<br><br># ifconfig<br>eth0 Link encap:Ethernet HWaddr 00:1D:55:14:B1:BD<br> inet addr:10.0.90.11 Bcast:10.0.255.255 Mask:255.255.0.0<br> inet6 addr: fe80::21d:55ff:fe14:b1bd/64 Scope:Link<br>
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:26828863 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:32509057 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:1000<br>
RX bytes:2808044025 (2.6 GiB) TX bytes:4026576497 (3.7 GiB)<br><br>eth0:0 Link encap:Ethernet HWaddr 00:1D:55:14:B1:BD<br> inet addr:10.0.90.1 Bcast:10.0.255.255 Mask:255.255.0.0<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
<br># ifconfig<br>eth0 Link encap:Ethernet HWaddr 00:1D:55:34:D0:86<br> inet addr:10.0.90.12 Bcast:10.0.255.255 Mask:255.255.0.0<br> inet6 addr: fe80::21d:55ff:fe34:d086/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br>
RX packets:16619236 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:15740439 errors:0 dropped:0 overruns:0 carrier:0<br> collisions:0 txqueuelen:1000<br> RX bytes:1676092603 (1.5 GiB) TX bytes:2112486773 (1.9 GiB)<br>
<br>eth0:0 Link encap:Ethernet HWaddr 00:1D:55:34:D0:86<br> inet addr:10.0.90.1 Bcast:10.0.255.255 Mask:255.255.0.0<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br><br></div><div>10.0.90.1 should be up only on the 10.0.90.11 at this point.<br>
<br>Looks like earlier today watchdog became confused:<br></div><div>on 10.0.90.11 from pgpool.log:<br>2014-04-07 11:42:31 DEBUG: pid 11380: wd_hb_receiver: received heartbeat signal from <a href="http://10.0.90.12:9999" target="_blank">10.0.90.12:9999</a><br>
2014-04-07 11:42:32 DEBUG: pid 11382: check_pgpool_status_by_hb: checking pgpool 0 (<a href="http://10.0.90.11:9999" target="_blank">10.0.90.11:9999</a>)<br>2014-04-07 11:42:32 DEBUG: pid 11382: check_pgpool_status_by_hb: OK; status 3<br>
2014-04-07 11:42:32 DEBUG: pid 11382: check_pgpool_status_by_hb: checking pgpool 1 (<a href="http://10.0.90.12:9999" target="_blank">10.0.90.12:9999</a>)<br>2014-04-07 11:42:32 LOG: pid 11382: check_pgpool_status_by_hb: pgpool 1 (<a href="http://10.0.90.12:9999" target="_blank">10.0.90.12:9999</a>) is in down status<br>
2014-04-07 11:42:32 DEBUG: pid 11381: wd_hb_send: send 224 byte packet<br>2014-04-07 11:42:32 DEBUG: pid 11381: wd_hb_sender: send heartbeat signal to <a href="http://10.0.90.12:9694" target="_blank">10.0.90.12:9694</a><br>
2014-04-07 11:42:33 DEBUG: pid 11380: wd_hb_recv: received 224 byte packet<br>
<br></div><div>also same from 10.0.90.12<br></div><div>2014-04-07 11:15:44 DEBUG: pid 12975: check_pgpool_status_by_hb: checking pgpool 1 (<a href="http://10.0.90.11:9999" target="_blank">10.0.90.11:9999</a>)<br>2014-04-07 11:15:44 LOG: pid 12975: check_pgpool_status_by_hb: pgpool 1 (<a href="http://10.0.90.11:9999" target="_blank">10.0.90.11:9999</a>) is in down status<br>
<br></div><div>Using pgpool 3.3.3 and replication configured using postgres 8.4.4<span><font color="#888888"><br></font></span></div><span><font color="#888888"><div><br></div><div><div><br>
-- <br>Sincerely yours,<br>Alexandru Cardaniuc
</div></div></font></span></div>
<br>_______________________________________________<br>
pgpool-general mailing list<br>
<a href="mailto:pgpool-general@pgpool.net" target="_blank">pgpool-general@pgpool.net</a><br>
<a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" target="_blank">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br>
<br></blockquote></div><br></div></div>