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

Tatsuo Ishii ishii at postgresql.org
Wed May 20 10:17:01 JST 2015


> Hi, Tatsuo,
> 
> RHEL 6.6

pgpool-II RPM details please.

> Wes
> 
> On 5/19/15, 3: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
>>> 
> 


More information about the pgpool-general mailing list