Hi Andrei,
After this state the system went through some more fencings and we saw the
following state:
:~ # crm status
Cluster Summary:
* Stack: corosync
* Current DC: FILE-2 (version
2.1.2+20211124.ada5c3b36-150400.2.43-2.1.2+20211124.ada5c3b36) - partition
with quorum
* Last updated: Mon
On 26.06.2023 21:14, Priyanka Balotra wrote:
Hi All,
We are seeing an issue where we replaced no-quorum-policy=ignore with other
options in corosync.conf order to simulate the same behaviour :
* wait_for_all: 0*
*last_man_standing: 1last_man_standing_window: 2*
There
Hi All,
We are seeing an issue where we replaced no-quorum-policy=ignore with other
options in corosync.conf order to simulate the same behaviour :
* wait_for_all: 0*
*last_man_standing: 1last_man_standing_window: 2*
There was another property (auto-tie-breaker) tried
On Mon, 2023-06-26 at 08:46 +0200, Klaus Wenninger wrote:
>
>
> On Fri, Jun 23, 2023 at 3:57 PM S Sathish S via Users <
> users@clusterlabs.org> wrote:
> > Hi Team,
> >
> > The pacemaker logs is written in both '/var/log/messages' and
> > '/var/log/pacemaker/pacemaker.log'.
> > Could you
On Fri, Jun 23, 2023 at 3:57 PM S Sathish S via Users
wrote:
> Hi Team,
>
>
>
> The pacemaker logs is written in both '/var/log/messages' and
> '/var/log/pacemaker/pacemaker.log'.
>
> Could you please help us for not write pacemaker processes in
> /var/log/messages? Even corosync configuration
