Hi Honza
I would say there is still a certain ambiguity in "shutdown by cfg request”,
but I would argue that by not using the term “sysadmin” it at least doesn’t
suggest that the shutdown was triggered by a human. So yes, I think that this
phrasing is less misleading.
Cheers,
Alex
> On
Hi,
I will reply just to "sysadmin" question:
On 26/04/2024 14:43, Alexander Eastwood via Users wrote:
Dear Reid,
...
Why does the corosync log say ’shutdown by sysadmin’ when the shutdown was
triggered by pacemaker? Isn’t this misleading?
This basically means shutdown was triggered by
Dear Reid,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:Both cluster nodes
Any logs from Pacemaker?
On Thu, Apr 25, 2024 at 3:46 AM Alexander Eastwood via Users
wrote:
>
> Hi all,
>
> I’m trying to get a better understanding of why our cluster - or specifically
> corosync.service - entered a failed state. Here are all of the relevant
> corosync logs from this event,
