Classified as: {OPEN}
Dear All,
I have a question about the "pacemakerd: recover properly from Corosync
crash" fix implemented in version 2.1.2.
I have observed the issue when testing pacemaker version 2.0.5, just by
killing the corosync process: Corosync was not recovered.
I am using
}
De : Users De la part de NOLIBOS Christophe via
Users
Envoyé : jeudi 18 avril 2024 18:34
À : Klaus Wenninger ; Cluster Labs - All topics related to
open-source clustering welcomed
Cc : NOLIBOS Christophe
Objet : Re: [ClusterLabs] "pacemakerd: recover properly from Corosync crash
cover properly from Corosync crash" fix
On Thu, Apr 18, 2024 at 5:07 PM NOLIBOS Christophe via Users
mailto:users@clusterlabs.org> > wrote:
Classified as: {OPEN}
I'm using RedHat 8.8 (4.18.0-477.21.1.el8_8.x86_64).
When I kill Corosync, no new corosync process is creat
3:13 +0000, NOLIBOS Christophe via Users wrote:
> Classified as: {OPEN}
>
> Dear All,
>
> I have a question about the "pacemakerd: recover properly from
> Corosync crash" fix implemented in version 2.1.2.
> I have observed the issue when testing pacemaker versio
s@clusterlabs.org> >
Cc : Ken Gaillot mailto:kgail...@redhat.com> >; NOLIBOS
Christophe mailto:christophe.noli...@thalesgroup.com> >
Objet : Re: [ClusterLabs] "pacemakerd: recover properly from Corosync crash" fix
On Thu, Apr 18, 2024 at 5:07 PM NOLIBOS Ch
ed to open-source clustering welcomed
mailto:users@clusterlabs.org> >
Cc : Ken Gaillot mailto:kgail...@redhat.com> >; NOLIBOS
Christophe mailto:christophe.noli...@thalesgroup.com> >
Objet : Re: [ClusterLabs] "pacemakerd: recover properly from Corosync crash" fix
ailto:users-boun...@clusterlabs.org> > De la part de NOLIBOS Christophe via
Users
Envoyé : jeudi 18 avril 2024 18:34
À : Klaus Wenninger mailto:kwenn...@redhat.com> >;
Cluster Labs - All topics related to open-source clustering welcomed
mailto:users@clusterlabs.org> >
Cc : NOLIBOS
stem)
with Pacemaker 2.1.5-8 deployed on RHEL 8.4 (not hardened).
I’m checking.
How did, you kill corosync? If it exits gracefully might not be restarted.
Check journal. Sry cant try am on my mobile ATM. Klaus
{OPEN}
{OPEN}
{OPEN}
De : Users mailto:users-boun...@clusterlabs.
eployed on RHEL 8.4 (not hardened).
I’m checking.
How did, you kill corosync? If it exits gracefully might not be restarted.
Check journal. Sry cant try am on my mobile ATM. Klaus
{OPEN}
{OPEN}
{OPEN}
{OPEN}
De : Users < <mailto:users-boun...@clusterlabs.org>
users
