[Pacemaker] What that means? (stonith-ng: crm_abort: Triggered assert at remote.c)

[Aleksey Zholdak]

Hi.

I successfully use sbd stonith on previous version of pacemaker (SLES11).
When I installed SLES11SP1 I found new version of pacemaker.
Everything was fine until I decided to check the work of sbd fensing and 
what I see: _What_ does this mean (see last line of log)?

...
Jun 14 11:29:40 sles1 crmd: [5260]: info: do_state_transition: State 
transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS 
cause=C_IPC_MESSAGE origin=handle_response ]
Jun 14 11:29:40 sles1 crmd: [5260]: info: unpack_graph: Unpacked transition 
18: 27 actions in 27 synapses
Jun 14 11:29:40 sles1 crmd: [5260]: info: do_te_invoke: Processing graph 18 
(ref=pe_calc-dc-1276504180-46) derived from /var/lib/pengine/pe-warn-94.bz2
Jun 14 11:29:40 sles1 crmd: [5260]: info: te_pseudo_action: Pseudo action 8 
fired and confirmed
Jun 14 11:29:40 sles1 crmd: [5260]: info: te_pseudo_action: Pseudo action 
31 fired and confirmed
Jun 14 11:29:40 sles1 crmd: [5260]: info: te_pseudo_action: Pseudo action 
57 fired and confirmed
Jun 14 11:29:40 sles1 crmd: [5260]: info: te_fence_node: Executing reboot 
fencing operation (59) on sles2 (timeout=60000)
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: initiate_remote_stonith_op: 
Initiating remote operation reboot for sles2: 
b99281ed-b72f-4441-982f-3b4fba989065
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: log_data_element: 
stonith_query: Query <stonith_command t="stonith-ng" 
st_async_id="b99281ed-b72f-4441-982f-3b4fba989065" st_op="st_query" 
st_callid="0" st_callopt="0" 
st_remote_op="b99281ed-b72f-4441-982f-3b4fba989065" st_target="sles2" 
st_device_action="reboot" 
st_clientid="000a85ae-f500-4540-808f-95639875f102" src="sles1" seq="66" />
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: can_fence_host_with_device: 
sbd_fense can fence sles2: dynamic-list
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: stonith_query: Found 1 
matching devices for 'sles2'
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: stonith_command: Processed 
st_query from sles1: rc=1
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: call_remote_stonith: 
Requesting that sles1 perform op reboot sles2
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: log_data_element: 
stonith_fence: Exec <stonith_command t="stonith-ng" 
st_async_id="b99281ed-b72f-4441-982f-3b4fba989065" st_op="st_fence" 
st_callid="0" st_callopt="0" 
st_remote_op="b99281ed-b72f-4441-982f-3b4fba989065" st_target="sles2" 
st_device_action="reboot" src="sles1" seq="68" />
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: can_fence_host_with_device: 
sbd_fense can fence sles2: dynamic-list
Jun 14 11:29:40 sles1 stonith-ng: [5255]: info: stonith_fence: Found 1 
matching devices for 'sles2'
Jun 14 11:29:40 sles1 pengine: [5259]: WARN: process_pe_message: Transition 
18: WARNINGs found during PE processing. PEngine Input stored in: 
/var/lib/pengine/pe-warn-94.bz2
Jun 14 11:29:40 sles1 pengine: [5259]: info: process_pe_message: 
Configuration WARNINGs found during PE processing.  Please run "crm_verify 
-L" to identify issues.
Jun 14 11:29:41 sles1 sbd: [6824]: info: sles2 owns slot 1
Jun 14 11:29:41 sles1 sbd: [6824]: info: Writing reset to node slot sles2
Jun 14 11:29:42 sles1 sbd: [6687]: info: reset successfully delivered to sles2
Jun 14 11:29:43 sles1 stonith-ng: [5255]: info: log_operation: Operation 
'reboot' [6680] for host 'sles2' with device 'sbd_fense' returned: 0 (call 
0 from (null))
Jun 14 11:29:43 sles1 stonith-ng: [5255]: info: log_data_element: 
process_remote_stonith_exec: ExecResult <st-reply 
st_origin="stonith_construct_async_reply"t="stonith-ng" st_op="st_notify" 
st_remote_op="4c63c107-eced-44fb-8f57-fd7318a0b5c3" st_callid="0" 
st_callopt="0" st_rc="0" st_output="Performing: stonith -texternal/sbd -T 
reset sles2 success: sles2 0 " src="sles1" seq="69" />
Jun 14 11:29:43 sles1 stonith-ng: [5255]: ERROR: crm_abort: remote_op_done: 
Triggered assert at remote.c:134 : op->request != NULL
!!!



-- 
Aleksey