[pgpool-general: 3730] Re: Questions about watchdog

Wed May 20 08:11:56 JST 2015

Hi Tatsuo,

I am running on:
CentOS 7 (systemd)
x86_64

OS/preocessor
uname -a
Linux hostname.com 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

package installed
 * epel: mirror.umd.edu
Installed Packages
Name        : postgresql-pgpool-II
Arch        : x86_64
Version     : 3.4.1
Release     : 1.el7
Size        : 2.8 M
Repo        : installed
From repo   : epel-testing
Summary     : Pgpool is a connection pooling/replication server for PostgreSQL
URL         : http://pgpool.net
License     : BSD
Description : pgpool-II is a inherited project of pgpool (to classify from
            : pgpool-II, it is sometimes called a… … 

Name        : postgresql-pgpool-II-extensions
Arch        : x86_64
Version     : 3.4.1
Release     : 1.el7
Size        : 28 k
Repo        : installed
From repo   : epel-testing
Summary     : Postgresql extensions for pgpool-II
URL         : http://pgpool.net
License     : BSD
Description : Postgresql extensions libraries and sql files for pgpool-II.

If you would like more info, please let me know.

Cheers,
Gervais

> On May 19, 2015, at 7:48 PM, Tatsuo Ishii <ishii at postgresql.org> wrote:
> 
>> 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.
> 
> Interesting. What kind of platform are you using?  I would like to
> know if the issue is of pgpool-II itself or the service script of the
> system (or both?).
> 
>> 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?
>> I find it difficult to search the archives. Is there full-text search capability somewhere for the list?
>> 
>> 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!)
>> 
>> 
>> use_watchdog = 'on'
>> 
>> wd_hostname = 'pgpool1'
>> 
>> Note: 'pgpool2' on second machine
>> 
>> 
>> 
>> wd_port = 19000
>> 
>> delegate_IP = 'your virtual IP'
>> 
>> if_up_cmd = 'sudo ifconfig eth0:0 inet $_IP_$ netmask 255.255.255.0'
>> 
>> ifconfig_path = '/usr/bin'
>> 
>> if_down_cmd = 'sudo ifconfig eth0:0 down'
>> 
>> arping_path = '/usr/bin'
>> 
>> arping_cmd = 'sudo arping -U $_IP_$ -w 1
>> 
>> wd_interval = 3
>> 
>> wd_heartbeat_port = 19464
>> 
>> heartbeat_destination_port0 = 19464
>> 
>> other_pgpool_port0 = 15432
>> 
>> other_wd_port0 = 19000
>> 
>> Note: these lines must be different on the different hosts. On host pgpool1, use
>> 
>> heartbeat_destination0 = 'pgpool2'
>> 
>> other_pgpool_hostname0 = 'pgpool2'
>> 
>> 
>> 
>> On host pgpool2, use
>> 
>> heartbeat_destination0 = 'pgpool1'
>> 
>> other_pgpool_hostname0 = 'pgpool1'
>> 
>> Thanks for your response,
>> 
>> Wes
>> 
>> From: Gervais de Montbrun <gervais at silverorange.com<mailto:gervais at silverorange.com>>
>> Date: Monday, May 18, 2015 at 3:13 PM
>> To: Wes Mitchell <wes.mitchell at ericsson.com<mailto:wes.mitchell at ericsson.com>>
>> Cc: "pgpool-general at pgpool.net<mailto:pgpool-general at pgpool.net>" <pgpool-general at pgpool.net<mailto:pgpool-general at pgpool.net>>
>> Subject: Re: [pgpool-general: 3721] Questions about watchdog
>> 
>> Hi Wes,
>> 
>> Something must be awry with your configs. Can you share the watchdog relevant settings of your configs?
>> 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.
>> 
>> Cheers,
>> Gervais
>> 
>> On May 18, 2015, at 5:30 PM, Wes Mitchell <wes.mitchell at ericsson.com<mailto:wes.mitchell at ericsson.com>> wrote:
>> 
>> Hi,
>> 
>> I am trying to configure pgpool-II for HA using watchdog.
>> 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:
>> 
>> 2015-05-18 16:11:44: pid 26948: LOCATION:  wd_ping.c:309
>> 2015-05-18 16:11:44: pid 26948: FATAL:  failed to initialize watchdog, delegate_IP "10.61.156.162" already exists
>> 
>> And all processes then terminate.
>> 
>> Please help me understand the proper configuration. I am setting
>> delegate_IP = ’10.61.156.162’
>> 
>> I see that the interface is brought up and bound to that IP on the first instance, using ifconfig:
>> eth0:0    Link encap:Ethernet  HWaddr 00:0C:29:39:17:DF
>>          inet addr:10.61.156.162  Bcast:10.61.156.255  Mask:255.255.255.0
>> 
>> 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?
>> 
>> If you could also reply directly, I would appreciate it.
>> 
>> Thanks,
>> //w
>> _______________________________________________
>> pgpool-general mailing list
>> pgpool-general at pgpool.net<mailto: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/20150519/c9cfe036/attachment-0001.html>