[ClusterLabs] "pacemakerd: recover properly from Corosync crash" fix

NOLIBOS Christophe christophe.nolibos at thalesgroup.com
Thu Apr 18 09:13:32 EDT 2024


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 now pacemaker version 2.1.5-8.

Doing the same test, I have the same result: Corosync is still not
recovered.

 

Please confirm the "pacemakerd: recover properly from Corosync crash" fix
implemented in version 2.1.2 covers this scenario.

If it is, did I miss something in the configuration of my cluster?

 

Best Regard.

 

Christophe.

 




	
	
	
	
	
	

Christophe Nolibos

DL-FEP Component Manager

THALES Land & Air Systems

105, avenue du Général Eisenhower, 31100 Toulouse, FRANCE

Tél. : +33 (0)5 61 19 79 09

Mobile : +33 (0)6 31 22 20 58

	

Email :  <mailto:christophe.nolibos at thalesgroup.com>
christophe.nolibos at thalesgroup.com

 

 


{OPEN}

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20240418/083747fc/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 1653 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20240418/083747fc/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 10900 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20240418/083747fc/attachment-0001.p7s>


More information about the Users mailing list