summaryrefslogtreecommitdiffstats
path: root/doc/website-v1/include/history-guide/stonith-corosync-stopped.typescript
blob: 1bca5acb73fcb0705cb6c95866967630af6b2e47 (plain)
1
2
3
4
5
6
7
8
# crm history node sle12-c
INFO: fetching new logs, please wait ...
Dec 19 14:36:18 sle12-c corosync[29551]:   [MAIN  ] Corosync Cluster Engine ('2.3.3'): started and ready to provide service.
Dec 19 14:36:19 sle12-c corosync[29545]: Starting Corosync Cluster Engine (corosync): [  OK  ]
Dec 19 14:36:20 sle12-a pengine[6906]:  warning: pe_fence_node: Node sle12-c will be fenced because our peer process is no longer available
Dec 19 14:36:20 sle12-a pengine[6906]:  warning: stage6: Scheduling Node sle12-c for STONITH
Dec 19 14:36:20 sle12-a crmd[6907]:   notice: te_fence_node: Executing reboot fencing operation (65) on sle12-c (timeout=60000)
Dec 19 14:36:20 sle12-a crmd[6907]:   notice: peer_update_callback: Node return implies stonith of sle12-c (action 65) completed