<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Dear Reid,<div><br></div><div>Thanks for the reply. Yes, lots of pacemaker logs - I have included just over a minute of them below and 5m of them as an attached .log file. The same behaviour occurs for a period of roughly 6 minutes before the corosync shutdown happens and can be summarised like so:</div><div><br></div><div><ul class="MailOutline"><li>Both cluster nodes (test cluster-c1 and testcluster-c2) are online</li><li>High CPU load is detected on the active cluster node (testcluster-c1)</li><li>High CPU load (presumably) leads to monitor operations on cluster resources timing out</li><li>Pacemaker attempts to recover/restart managed resources several times - unsuccessfully</li><li>Cluster processes start shutting down</li><li>Pacemaker is responsible for corosync shutting down (<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);"><i>pcmkd_shutdown_corosync) info: Asking Corosync to shut down)</i></span></li></ul><div><br></div><div>This leads to several more questions…</div><div><br></div><div><ul class="MailOutline"><li>Why does the corosync log say ’shutdown by sysadmin’ when the shutdown was triggered by pacemaker? Isn’t this misleading?</li><li>Why was there no transition to the other node?</li><li>What is the purpose of shutting down corosync? Isn’t this how the 2 cluster nodes communicate with each other? Since testcluster-c1 requests a shutdown - and this is acknowledged by testcluster-c2 - isn’t corosync then required for the transition to occur?</li></ul><div><br></div></div><div>Any help is much appreciated!</div><div><br></div><div>Cheers</div><div><br></div><div>Alex</div><div><br></div><div></div></div></body></html>