Did the "active on too many nodes" message happen right after a probe? If
so, then it does sound like the probe returned code 0.
If a probe returned 0 and it **shouldn't** have done so, then either the
monitor operation needs to be redesigned, or resource-discovery=never (or
>>> Reid Wahl schrieb am 05.03.2021 um 21:22 in Nachricht
:
> On Fri, Mar 5, 2021 at 10:13 AM Ken Gaillot wrote:
>
>> On Fri, 2021-03-05 at 11:39 +0100, Ulrich Windl wrote:
>> > Hi!
>> >
>> > I'm unsure what actually causes a problem I see (a resource was
>> > "detected running" when it
