[ClusterLabs] What Does the Monitor Action of the IPaddr2 RA Actually Do?
Andrei Borzenkov
arvidjaar at gmail.com
Thu Jun 3 01:22:59 EDT 2021
On 02.06.2021 23:38, Eric Robinson wrote:
>> -----Original Message-----
>> From: Users <users-bounces at clusterlabs.org> On Behalf Of Andrei
>> Borzenkov
>> Sent: Tuesday, June 1, 2021 1:14 PM
>> To: users at clusterlabs.org
>> Subject: Re: [ClusterLabs] What Does the Monitor Action of the IPaddr2 RA
>> Actually Do?
>>
>> On 01.06.2021 19:50, Eric Robinson wrote:
>>> This is related to another question I currently have ongoing.
>>>
>>> I see in the logs that monitoring failed for a VIP resource, and that may
>> have been responsible for node failover. I read the code for the IPaddr2 RA
>> but it is not clear to me exactly what the monitor action looks for to
>> determine resource health.
>>>
>>> May 27 09:55:31 001store01a crmd[92171]: notice: State transition S_IDLE -
>>> S_POLICY_ENGINE May 27 09:55:31 001store01a pengine[92170]: warning:
>> Processing failed op monitor for p_vip_ftpclust01 on 001store01a: unknown
>> error (1)
>>>
>>
>> enable trace for monitor operation. See e.g.
>> https://www.suse.com/support/kb/doc/?id=000019138.
>>
>
> How does that differ from just doing debug-start, debug-stop, or debug-monitor?
>
I do not know what these do.
More information about the Users
mailing list