Thanks. In the end, I found out that my target application has a setting
whereby the application becomes instantly detectable to the monitoring side
of my script. After doing this, the associated resource is created
flawlessly every time.
On Tue, Apr 16, 2019 at 1:46 PM Jan Pokorný wrote:
>
[letter-casing wise:
it's either "Pacemaker" or down-to-the-terminal "pacemaker"]
On 16/04/19 10:21 -0600, JCA wrote:
> 2. It would seem that what Pacemaker is doing is the following:
>a. Check out whether the app is running.
>b. If it is not, launch it.
>c. Check out again
>d.
Hi all,
I wanted to point out an experimental feature that will be part of the
next release.
We are adding a "crm_rule" command that has the ability to check
whether a particular date-based rule is currently in effect.
The motivation is a perennial user complaint: expired constraints
remain in
Well, I checked this PR
https://github.com/ClusterLabs/sbd/pull/27
from author repository
https://github.com/jjd27/sbd/tree/cluster-quorum
The problem is still exists. When corosync is frozen on one node, both node are
rebooted. Don’t apply this PR.
> 16 апр. 2019 г., в 19:13, Klaus Wenninger
Thanks to everybody who has contributed to this. Let me summarize things,
if it is only for my own benefit - I learn more quickly when I try to
explain that I am trying to learn something to others.
I instrumented my script in order to find out exactly how many times it is
invoked when creating
On 4/16/19 5:27 PM, Олег Самойлов wrote:
>
>> 16 апр. 2019 г., в 16:21, Klaus Wenninger написал(а):
>>
>> On 4/16/19 3:12 PM, Олег Самойлов wrote:
>>> Okey, looked like I found where it must be fixed.
>>>
>>> sbd-cluster.c
>>>
>>>/* TODO - Make a CPG call and only call notify_parent()
> 16 апр. 2019 г., в 16:21, Klaus Wenninger написал(а):
>
> On 4/16/19 3:12 PM, Олег Самойлов wrote:
>> Okey, looked like I found where it must be fixed.
>>
>> sbd-cluster.c
>>
>>/* TODO - Make a CPG call and only call notify_parent() when we
>> get a reply */
>>
On 4/16/19 3:12 PM, Олег Самойлов wrote:
> Okey, looked like I found where it must be fixed.
>
> sbd-cluster.c
>
> /* TODO - Make a CPG call and only call notify_parent() when we
> get a reply */
> notify_parent();
>
> Can anyone explain me, how to make mentioned CPG call?
On 15/04/19 16:01 -0600, JCA wrote:
> This is weird. Further experiments, consisting of creating and deleting the
> resource, reveal that, on creating the resource, myapp-script may be
> invoked multiple times - sometimes four, sometimes twenty or so, sometimes
> returning OCF_SUCCESS, some other
>>> Ken Gaillot schrieb am 16.04.2019 um 00:30 in
Nachricht
<144df656215fc1ed6b3a35cffd1cbd2436f2a785.ca...@redhat.com>:
[...]
> The cluster successfully probed the service on both nodes, and started
> it on node one. It then tried to start a 30‑second recurring monitor
> for the service, but the
>>> JCA <1.41...@gmail.com> schrieb am 15.04.2019 um 23:30 in Nachricht
:
> Well, I remain puzzled. I added a statement to the end of my script in
> order to capture its return value. Much to my surprise, when I create the
> associated resource (as described in my previous post) myapp-script gets
11 matches
Mail list logo
