On 01/19/2016 10:30 AM, Kostiantyn Ponomarenko wrote:
> The resource that wasn't running, but was reported as running, is
> "adminServer".
>
> Here are a brief chronological description:
>
> [Jan 19 23:42:16] The first time Pacemaker triggers its monitor function at
> line #1107. (those lines
On 01/19/2016 11:02 AM, Kostiantyn Ponomarenko wrote:
> Just in case, this is the monitor function from the resource agent:
> ra_monitor() {
> # ocf_log info "$RA: [monitor]"
> systemctl status ${service}
> rc=$?
> if [ "$rc" -eq "0" ]; then
> return $OCF_SUCCESS
> fi
>
On 01/19/2016 12:20 PM, Kostiantyn Ponomarenko wrote:
> I've put the wrong entry from "journalctl --since="2016-01-19"
> --until="2016-01-20"".
> The correct one is:
>
> Jan 19 23:42:24 A2-2U12-302-LS ntpd[2204]: 0.0.0.0 c61c 0c clock_step
> -43194.111405 s
> Jan 19 11:42:29 A2-2U12-302-LS
One of resources in my cluster is not actually running, but "crm_mon" shows
it with the "Started" status.
Its resource agent's monitor function returns "$OCF_NOT_RUNNING", but
Pacemaker doesn't react on this anyhow - crm_mon show the resource as
Started.
I couldn't find an explanation to this
On 19.01.2016 13:49, Kostiantyn Ponomarenko wrote:
> One of resources in my cluster is not actually running, but "crm_mon"
> shows it with the "Started" status.
> Its resource agent's monitor function returns "$OCF_NOT_RUNNING", but
> Pacemaker doesn't react on this anyhow - crm_mon show the
On 19.01.2016 16:13, Ken Gaillot wrote:
> On 01/19/2016 06:49 AM, Kostiantyn Ponomarenko wrote:
>> One of resources in my cluster is not actually running, but "crm_mon" shows
>> it with the "Started" status.
>> Its resource agent's monitor function returns "$OCF_NOT_RUNNING", but
>> Pacemaker
Just in case, this is the monitor function from the resource agent:
ra_monitor() {
# ocf_log info "$RA: [monitor]"
systemctl status ${service}
rc=$?
if [ "$rc" -eq "0" ]; then
return $OCF_SUCCESS
fi
ocf_log warn "$RA: [monitor] : got rc=$rc"
return
