<div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 18, 2024 at 5:07 PM NOLIBOS Christophe via Users <<a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Classified as: {OPEN}<br>
<br>
I'm using RedHat 8.8 (4.18.0-477.21.1.el8_8.x86_64).<br>
When I kill Corosync, no new corosync process is created and pacemaker is in failure.<br>
The only solution is to restart the pacemaker service.<br>
<br>
[~]$ pcs status<br>
Error: unable to get cib<br>
[~]$<br>
<br>
[~]$systemctl status pacemaker<br>
● pacemaker.service - Pacemaker High Availability Cluster Manager<br>
Loaded: loaded (/usr/lib/systemd/system/pacemaker.service; enabled; vendor preset: disabled)<br>
Active: active (running) since Thu 2024-04-18 13:16:04 UTC; 1h 43min ago<br>
Docs: man:pacemakerd<br>
<a href="https://clusterlabs.org/pacemaker/doc/" rel="noreferrer" target="_blank">https://clusterlabs.org/pacemaker/doc/</a><br>
Main PID: 1324923 (pacemakerd)<br>
Tasks: 91<br>
Memory: 132.1M<br>
CGroup: /system.slice/pacemaker.service<br>
...<br>
Apr 18 14:59:02 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:03 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:04 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:05 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:06 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:07 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:08 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:09 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:10 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
Apr 18 14:59:11 - pacemakerd[1324923]: crit: Could not connect to Corosync CFG: CS_ERR_LIBRARY<br>
[~]$<br>
<br>
<br></blockquote><div>Well if corosync isn't there that this is to be expected and pacemaker won't recover corosync.</div><div>Can you check what systemd thinks about corosync (status/journal). </div><div><br></div><div>Klaus</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
{OPEN}<br>
<br>
-----Message d'origine-----<br>
De : Ken Gaillot <<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>> <br>
Envoyé : jeudi 18 avril 2024 16:40<br>
À : Cluster Labs - All topics related to open-source clustering welcomed <<a href="mailto:users@clusterlabs.org" target="_blank">users@clusterlabs.org</a>><br>
Cc : NOLIBOS Christophe <<a href="mailto:christophe.nolibos@thalesgroup.com" target="_blank">christophe.nolibos@thalesgroup.com</a>><br>
Objet : Re: [ClusterLabs] "pacemakerd: recover properly from Corosync crash" fix<br>
<br>
What OS are you using? Does it use systemd?<br>
<br>
What does happen when you kill Corosync?<br>
<br>
On Thu, 2024-04-18 at 13:13 +0000, NOLIBOS Christophe via Users wrote:<br>
> Classified as: {OPEN}<br>
> <br>
> Dear All,<br>
> <br>
> I have a question about the "pacemakerd: recover properly from <br>
> Corosync crash" fix implemented in version 2.1.2.<br>
> I have observed the issue when testing pacemaker version 2.0.5, just <br>
> by killing the ‘corosync’ process: Corosync was not recovered.<br>
> <br>
> I am using now pacemaker version 2.1.5-8.<br>
> Doing the same test, I have the same result: Corosync is still not <br>
> recovered.<br>
> <br>
> Please confirm the "pacemakerd: recover properly from Corosync crash"<br>
> fix implemented in version 2.1.2 covers this scenario.<br>
> If it is, did I miss something in the configuration of my cluster?<br>
> <br>
> Best Regard.<br>
> <br>
> Christophe.<br>
> <br>
> <br>
> <br>
> {OPEN}<br>
> _______________________________________________<br>
> Manage your subscription:<br>
> <a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
> <br>
> ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
--<br>
Ken Gaillot <<a href="mailto:kgaillot@redhat.com" target="_blank">kgaillot@redhat.com</a>><br>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">https://lists.clusterlabs.org/mailman/listinfo/users</a><br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/" rel="noreferrer" target="_blank">https://www.clusterlabs.org/</a><br>
</blockquote></div></div>