> -Original Message-
> From: Users [mailto:users-boun...@clusterlabs.org] On Behalf Of Lentes,
> Bernd
> Sent: 2019年10月14日 20:04
> To: Pacemaker ML
> Subject: Re: [ClusterLabs] trace of Filesystem RA does not log
>
>
> >> -Original Message-
> >> From: Users
Hi all,
With Pacemaker 2.0.2, we introduced a new experimental option for XML
output from stonith_admin. This was the test case for a new output
model for Pacemaker tools. I'm happy to say this has been extended to
crm_mon and will be considered stable as of 2.0.3.
crm_mon has always supported
On Fri, 2019-10-11 at 17:15 +, Reynolds, John F - San Mateo, CA -
Contractor wrote:
> > If pacemaker is managing a resource, the service should not be
> > enabled to start on boot (regardless of init or systemd). Pacemaker
> > will start and stop the service as needed according to the cluster
>> -Original Message-
>> From: Users [mailto:users-boun...@clusterlabs.org] On Behalf Of Lentes,
>> Bernd
>> Sent: 2019年10月11日 22:32
>> To: Pacemaker ML
>> Subject: [ClusterLabs] trace of Filesystem RA does not log
>>
>> Hi,
>>
>> occasionally the stop of a Filesystem resource for an
- On Oct 14, 2019, at 6:27 AM, Roger Zhou zz...@suse.com wrote:
> The stop failure is very bad, and is crucial for HA system.
Yes, that's true.
> You can try o2locktop cli to find the potential INODE to be blamed[1].
>
> `o2locktop --help` gives you more usage details
I will try that.
>>> "Reynolds, John F - San Mateo, CA - Contractor"
schrieb am 11.10.2019 um 19:15 in Nachricht
:
>> If pacemaker is managing a resource, the service should not be enabled to
> start on boot (regardless of init or systemd). Pacemaker will start and stop
> the service as needed according to
>>> Ken Gaillot schrieb am 10.10.2019 um 21:19 in
Nachricht
<53c0a1ef1ac0d83d7e3d67dbd0251602bbdd82d1.ca...@redhat.com>:
> On Thu, 2019‑10‑10 at 17:22 +0200, Lentes, Bernd wrote:
>> HI,
>>
>> i have a two node cluster running on SLES 12 SP4.
>> I did some testing on it.
>> I put one into standby
