Hi!
Using SBD, I got this message from crm's top-level "verify":
crm(live/h16)# verify
Current cluster status:
Online: [ h16 h18 h19 ]
prm_stonith_sbd(stonith:external/sbd): Started h18
(unpack_config) notice: Watchdog will be used via SBD if fencing is
required and
Hi!
Is it intentional that "crm node server" is the only command that cannot
complete the node?
crmsh-4.2.0+git.1604052559.2a348644-5.26.1 of SLES15 SP2
Regards,
Ulrich
___
Manage your subscription:
I created https://github.com/ClusterLabs/pacemaker/pull/2241 to
correct the schema mistake.
On Wed, Nov 25, 2020 at 10:51 PM wrote:
>
> Hi, thank you for your reply.
>
> I tried it this way:
>
>
>path="/usr/share/pacemaker/alerts/test_alert.sh">
>
>
Hi, thank you for your reply.
I tried it this way:
hana_node_1
During the save the select is been reset to
Do I need to specify in addition
What version of Pacemaker are you using, and how does it behave?
Depending on the error/misbehavior you're experiencing, this might
have been me. Looks like in commit bd451763[1], I copied the
alerts-2.9.rng[2] schema instead of the alerts-2.10.rng[3] schema.
[1]
Hi, I would like to trigger an external script, if something happens on a
specific node.
In the documentation of alerts, i can see but whatever I
put into the XML, it's not working...
configuration>
>>> Christine Caulfield schrieb am 25.11.2020 um 10:17
in
Nachricht <56738406-9222-a9f3-c57c-e30400a0b...@redhat.com>:
> On 25/11/2020 08:45, Ulrich Windl wrote:
>> Hi!
>>
>> Setting up a cluster in SLES15 SP2, I wonder about a few log messages:
>>
>> 1) what does "QB" stand for?
>>
>> 2) When
