On Thu, 2023-07-20 at 12:43 +0530, Priyanka Balotra wrote:
> What I mainly want to understand is that:
> - why "fatal failure" is coming
The logs so far don't show that. The earliest sign is:
Jul 17 14:18:20.085 FILE-6 pacemaker-fenced[19411]
(remote_op_done) notice: Operation 'reboot'
On Wed, Jul 19, 2023 at 8:33 PM Priyanka Balotra
wrote:
>
> Sure,
> Here are the logs:
>
>
> 63138:Jul 17 14:16:25.132 FILE-2 pacemaker-controld [15962]
> (post_cache_update)debug: Updated cache after membership event 44.
> 63139:Jul 17 14:16:25.132 FILE-2 pacemaker-controld [15962]
>
Sure,
Here are the logs:
63138:Jul 17 14:16:25.132 FILE-2 pacemaker-controld [15962]
(post_cache_update)debug: Updated cache after membership event 44.
63139:Jul 17 14:16:25.132 FILE-2 pacemaker-controld [15962]
(pcmk__set_flags_as) debug: FSA action flags 0x2
On Wed, 2023-07-19 at 23:49 +0530, Priyanka Balotra wrote:
> Hi All,
> I am using SLES 15 SP4. One of the nodes of the cluster is brought
> down and boot up after sometime. Pacemaker service came up first but
> later it faced a fatal shutdown. Due to that crm service is down.
>
> The logs from
Hi All,
I am using SLES 15 SP4. One of the nodes of the cluster is brought down and
boot up after sometime. Pacemaker service came up first but later it faced
a fatal shutdown. Due to that crm service is down.
The logs from /var/log/pacemaker.pacemaker.log are as follows:
Jul 17 14:18:20.093
