On 12/09/17 19:38, Ken Gaillot wrote:
> On Mon, 2017-09-11 at 23:38 +0100, J Martin Rushton wrote:
>> I've had it switched off over the last week whilst I've been trying to
>> sort this out, but forgot tonight. It must be the combination of
>> setting multicast_querier and stopping the firewall
On Mon, 2017-09-11 at 23:38 +0100, J Martin Rushton wrote:
> I've had it switched off over the last week whilst I've been trying to
> sort this out, but forgot tonight. It must be the combination of
> setting multicast_querier and stopping the firewall that is needed. I
FYI this should open the
On 2017-09-12 07:48 AM, Jehan-Guillaume de Rorthais wrote:
> PostgreSQL Automatic Failover (PAF) v2.2.0 has been released on September
> 12th 2017 under the PostgreSQL licence.
>
> See: https://github.com/dalibo/PAF/releases/tag/v2.2.0
>
> PAF is a PostgreSQL resource agent for Pacemaker. Its
PostgreSQL Automatic Failover (PAF) v2.2.0 has been released on September
12th 2017 under the PostgreSQL licence.
See: https://github.com/dalibo/PAF/releases/tag/v2.2.0
PAF is a PostgreSQL resource agent for Pacemaker. Its original aim is to
keep it clear between the Pacemaker administration and
​Hello,
I have created a resource group from 2 resources: pcs resource group add
Group1 IPaddr Email. From the documentation is clear that resources are
stopped in the reverse order in which are specified (Email first, then
IPaddr).
There is a way to force stopping of the resources from a
Ferenc,
Jan Friesse writes:
Back to problem you have. It's definitively HW issue but I'm thinking
how to solve it in software. Right now, I can see two ways:
1. Set dog FD to be non blocking right at the end of setup_watchdog -
This is proffered but I'm not sure if