<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Tatsuo,<div class=""><br class=""></div><div class="">I am running on:</div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class=""><font face="Courier" class="">CentOS 7 (systemd)</font></div><div class=""><font face="Courier" class="">x86_64</font></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><font face="Courier" class="">OS/preocessor</font></div><div class=""><font face="Courier" class="">uname -a</font></div><div class=""><font face="Courier" class="">Linux <a href="http://hostname.com" class="">hostname.com</a> 3.10.0-229.4.2.el7.x86_64 #1 SMP Wed May 13 10:06:09 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux</font></div><div class=""><div class=""><font face="Courier" class=""><br class="webkit-block-placeholder"></font></div></div><div class=""><font face="Courier" class="">package installed</font></div><div class=""><div class=""><font face="Courier" class=""> * epel: <a href="http://mirror.umd.edu" class="">mirror.umd.edu</a></font></div></div><div class=""><div class=""><font face="Courier" class="">Installed Packages</font></div></div><div class=""><div class=""><font face="Courier" class="">Name : postgresql-pgpool-II</font></div></div><div class=""><div class=""><font face="Courier" class="">Arch : x86_64</font></div></div><div class=""><div class=""><font face="Courier" class="">Version : 3.4.1</font></div></div><div class=""><div class=""><font face="Courier" class="">Release : 1.el7</font></div></div><div class=""><div class=""><font face="Courier" class="">Size : 2.8 M</font></div></div><div class=""><div class=""><font face="Courier" class="">Repo : installed</font></div></div><div class=""><div class=""><font face="Courier" class="">From repo : epel-testing</font></div></div><div class=""><div class=""><font face="Courier" class="">Summary : Pgpool is a connection pooling/replication server for PostgreSQL</font></div></div><div class=""><div class=""><font face="Courier" class="">URL : <a href="http://pgpool.net" class="">http://pgpool.net</a></font></div></div><div class=""><div class=""><font face="Courier" class="">License : BSD</font></div></div><div class=""><div class=""><font face="Courier" class="">Description : pgpool-II is a inherited project of pgpool (to classify from</font></div></div><div class=""><div class=""><font face="Courier" class=""> : pgpool-II, it is sometimes called a… … </font></div></div><div class=""><font face="Courier" class=""><br class=""></font></div><div class=""><font face="Courier" class="">Name : postgresql-pgpool-II-extensions<br class="">Arch : x86_64<br class="">Version : 3.4.1<br class="">Release : 1.el7<br class="">Size : 28 k<br class="">Repo : installed<br class="">From repo : epel-testing<br class="">Summary : Postgresql extensions for pgpool-II<br class="">URL : <a href="http://pgpool.net" class="">http://pgpool.net</a><br class="">License : BSD<br class="">Description : Postgresql extensions libraries and sql files for pgpool-II.</font></div></blockquote><div class=""><div class=""><font face="Courier" class=""><br class=""></font></div><div class="">If you would like more info, please let me know.</div><div class=""><br class="">Cheers,<br class="">Gervais<br class=""></div><br class=""><blockquote type="cite" class="">On May 19, 2015, at 7:48 PM, Tatsuo Ishii <<a href="mailto:ishii@postgresql.org" class="">ishii@postgresql.org</a>> wrote:<br class=""><br class=""><blockquote type="cite" class="">However, now I have a different issue: if I use the service command to stop/restart pgpool, sometimes Unix domain socket files are left dangling (and sometimes they are cleaned up properly), preventing the restart from succeeding.<br class=""></blockquote><br class="">Interesting. What kind of platform are you using? I would like to<br class="">know if the issue is of pgpool-II itself or the service script of the<br class="">system (or both?).<br class=""><br class=""><blockquote type="cite" class="">Is this a known issue? Should I pre-emptively remove the socket files, perhaps in the init.d/pgpool-II script? Or, can I avoid the issue altogether by some magic in pool_hba.conf?<br class="">I find it difficult to search the archives. Is there full-text search capability somewhere for the list?<br class=""><br class="">Here are my settings. I have a non-root user with sudo privileges only for ifconfig and arping, which is why the paths don’t look right (but it works!)<br class=""><br class=""><br class="">use_watchdog = 'on'<br class=""><br class="">wd_hostname = 'pgpool1'<br class=""><br class="">Note: 'pgpool2' on second machine<br class=""><br class=""><br class=""><br class="">wd_port = 19000<br class=""><br class="">delegate_IP = 'your virtual IP'<br class=""><br class="">if_up_cmd = 'sudo ifconfig eth0:0 inet $_IP_$ netmask 255.255.255.0'<br class=""><br class="">ifconfig_path = '/usr/bin'<br class=""><br class="">if_down_cmd = 'sudo ifconfig eth0:0 down'<br class=""><br class="">arping_path = '/usr/bin'<br class=""><br class="">arping_cmd = 'sudo arping -U $_IP_$ -w 1<br class=""><br class="">wd_interval = 3<br class=""><br class="">wd_heartbeat_port = 19464<br class=""><br class="">heartbeat_destination_port0 = 19464<br class=""><br class="">other_pgpool_port0 = 15432<br class=""><br class="">other_wd_port0 = 19000<br class=""><br class="">Note: these lines must be different on the different hosts. On host pgpool1, use<br class=""><br class="">heartbeat_destination0 = 'pgpool2'<br class=""><br class="">other_pgpool_hostname0 = 'pgpool2'<br class=""><br class=""><br class=""><br class="">On host pgpool2, use<br class=""><br class="">heartbeat_destination0 = 'pgpool1'<br class=""><br class="">other_pgpool_hostname0 = 'pgpool1'<br class=""><br class="">Thanks for your response,<br class=""><br class="">Wes<br class=""><br class="">From: Gervais de Montbrun <<a href="mailto:gervais@silverorange.com" class="">gervais@silverorange.com</a><<a href="mailto:gervais@silverorange.com" class="">mailto:gervais@silverorange.com</a>>><br class="">Date: Monday, May 18, 2015 at 3:13 PM<br class="">To: Wes Mitchell <<a href="mailto:wes.mitchell@ericsson.com" class="">wes.mitchell@ericsson.com</a><<a href="mailto:wes.mitchell@ericsson.com" class="">mailto:wes.mitchell@ericsson.com</a>>><br class="">Cc: "<a href="mailto:pgpool-general@pgpool.net" class="">pgpool-general@pgpool.net</a><<a href="mailto:pgpool-general@pgpool.net" class="">mailto:pgpool-general@pgpool.net</a>>" <<a href="mailto:pgpool-general@pgpool.net" class="">pgpool-general@pgpool.net</a><<a href="mailto:pgpool-general@pgpool.net" class="">mailto:pgpool-general@pgpool.net</a>>><br class="">Subject: Re: [pgpool-general: 3721] Questions about watchdog<br class=""><br class="">Hi Wes,<br class=""><br class="">Something must be awry with your configs. Can you share the watchdog relevant settings of your configs?<br class="">Perhaps your heartbeat_destination0 and other_pgpool_hostname0 are not set. Just a hunch. Make sure that the first is the hostname of the server you are running on and the “other” points to the other pgpool server.<br class=""><br class="">Cheers,<br class="">Gervais<br class=""><br class="">On May 18, 2015, at 5:30 PM, Wes Mitchell <<a href="mailto:wes.mitchell@ericsson.com" class="">wes.mitchell@ericsson.com</a><<a href="mailto:wes.mitchell@ericsson.com" class="">mailto:wes.mitchell@ericsson.com</a>>> wrote:<br class=""><br class="">Hi,<br class=""><br class="">I am trying to configure pgpool-II for HA using watchdog.<br class="">I am running into the following issue: if I specify the delegate_IP parameter on both pgpool hosts, then whichever one is brought up second fails:<br class=""><br class="">2015-05-18 16:11:44: pid 26948: LOCATION: wd_ping.c:309<br class="">2015-05-18 16:11:44: pid 26948: FATAL: failed to initialize watchdog, delegate_IP "10.61.156.162" already exists<br class=""><br class="">And all processes then terminate.<br class=""><br class="">Please help me understand the proper configuration. I am setting<br class="">delegate_IP = ’10.61.156.162’<br class=""><br class="">I see that the interface is brought up and bound to that IP on the first instance, using ifconfig:<br class="">eth0:0 Link encap:Ethernet HWaddr 00:0C:29:39:17:DF<br class=""> inet addr:10.61.156.162 Bcast:10.61.156.255 Mask:255.255.255.0<br class=""><br class="">Is there some setting to tell pgpool process that it is master or standby? How do I set delegate_IP so that failover will bring up the IP on the promoted machine?<br class=""><br class="">If you could also reply directly, I would appreciate it.<br class=""><br class="">Thanks,<br class="">//w<br class="">_______________________________________________<br class="">pgpool-general mailing list<br class=""><a href="mailto:pgpool-general@pgpool.net" class="">pgpool-general@pgpool.net</a><<a href="mailto:pgpool-general@pgpool.net" class="">mailto:pgpool-general@pgpool.net</a>><br class=""><a href="http://www.pgpool.net/mailman/listinfo/pgpool-general" class="">http://www.pgpool.net/mailman/listinfo/pgpool-general</a><br class=""><br class=""></blockquote></blockquote><br class=""></div></body></html>