info 20 node1/crm: node 'node2': state changed from 'unknown' => 'online'
info 20 node1/crm: node 'node3': state changed from 'unknown' => 'online'
info 20 node1/crm: adding new service 'vm:103' on node 'node3'
+info 20 node1/crm: service 'vm:103': state changed from 'request_start' to 'started' (node = node3)
info 22 node2/crm: status change wait_for_quorum => slave
info 24 node3/crm: status change wait_for_quorum => slave
info 25 node3/lrm: got lock 'ha_agent_node3_lock'
info 340 node1/crm: fencing: acknowledged - got agent lock for node 'node3'
info 340 node1/crm: node 'node3': state changed from 'fence' => 'unknown'
emai 340 node1/crm: SUCCEED: fencing: acknowledged - got agent lock for node 'node3'
+info 340 node1/crm: service 'vm:103': state changed from 'fence' to 'recovery'
info 340 node1/crm: recover service 'vm:103' from fenced node 'node3' to node 'node1'
warn 340 node1/crm: removed leftover lock 'backup' from recovered service 'vm:103' to allow its start.
-info 340 node1/crm: service 'vm:103': state changed from 'fence' to 'started' (node = node1)
+info 340 node1/crm: service 'vm:103': state changed from 'recovery' to 'started' (node = node1)
info 341 node1/lrm: got lock 'ha_agent_node1_lock'
info 341 node1/lrm: status change wait_for_agent_lock => active
info 341 node1/lrm: starting service vm:103