t;call_options &
> st_opt_sync_call, FALSE);
> +
> /* mark this op as having notify's already sent */
> op->notify_sent = TRUE;
> free_xml(reply);
>
> Regards,
> Kazunori INOUE
>
>> -----Original Message-
>> From: Ken Gaillot [mailto:
day, May 17, 2017 11:09 PM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Pacemaker's "stonith too many failures" log is not
> accurate
>
> On 05/17/2017 04:56 AM, Klaus Wenninger wrote:
> > On 05/17/2017 11:28 AM, 井上 和徳 wrote:
> >> Hi,
> >> I'm te
Hi Ken,
thank you for your comment.
I'll try to check behavior.
> -Original Message-
> From: Ken Gaillot [mailto:kgail...@redhat.com]
> Sent: Wednesday, May 17, 2017 11:09 PM
> To: users@clusterlabs.org
> Subject: Re: [ClusterLabs] Pacemaker's "stonith to
On 05/17/2017 04:56 AM, Klaus Wenninger wrote:
> On 05/17/2017 11:28 AM, 井上 和徳 wrote:
>> Hi,
>> I'm testing Pacemaker-1.1.17-rc1.
>> The number of failures in "Too many failures (10) to fence" log does not
>> match the number of actual failures.
>
> Well it kind of does as after 10 failures it
On 05/17/2017 11:28 AM, 井上 和徳 wrote:
> Hi,
> I'm testing Pacemaker-1.1.17-rc1.
> The number of failures in "Too many failures (10) to fence" log does not
> match the number of actual failures.
Well it kind of does as after 10 failures it doesn't try fencing again
so that is what
failures stay at
