[Pacemaker] warning log is outputted after pacemaker stopped

[Kazunori INOUE]

Hi,

WARNING of the following is outputted after pacemaker stopped in
Pacemaker-1.1.11.

Feb 21 18:22:57 bl460g1n6 ping(prmPing)[9195]: WARNING: Could not
update default_ping_set = 100: rc=141


This is because pacemaker does not wait for completion of 'monitor' of
the ping resource.

Feb 21 18:22:52 bl460g1n6 lrmd[9100]:    debug:
recurring_action_timer: Scheduling another invokation of
prmPing_monitor_30000
Feb 21 18:22:52 bl460g1n6 pacemakerd[9094]:     info:
crm_signal_dispatch: Invoking handler for signal 15: Terminated
(snip)
Feb 21 18:22:54 bl460g1n6 crmd[9103]:   notice: process_lrm_event: LRM
operation prmPing_stop_0 (call=9, rc=0, cib-update=29, confirmed=true)
ok
(snip)
Feb 21 18:22:54 bl460g1n6 lrmd[9100]:     info:
services_action_cancel: Cancelling op: prmPing_monitor_30000 will
occur once operation completes
(snip)
Feb 21 18:22:54 bl460g1n6 pacemakerd[9094]:     info: main: Exiting pacemakerd
(snip)
Feb 21 18:22:55 bl460g1n6 corosync[9083]:  [MAIN  ] Corosync Cluster
Engine exiting normally
Feb 21 18:22:57 bl460g1n6 ping(prmPing)[9195]: WARNING: Could not
update default_ping_set = 100: rc=141


As with pacemaker-1.0, I think that it's better to perform a 'stop'
after completion of 'monitor'.
(Who manages 'monitor' after pacemaker stopped?)

Regards,
Kazunori INOUE
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ha-log
Type: application/octet-stream
Size: 85801 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140221/c2b67ff9/attachment-0003.obj>