<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="EN-US" link="blue" vlink="purple" style="word-wrap:break-word">
<div class="WordSection1">
<p class="MsoNormal">That looks great … is that a string that an RA can set on failure? I’d love to be able to communicate RA-specific failure reasons back to crm_mon consumers…<o:p></o:p></p>
<p class="MsoNormal">Thanks!<o:p></o:p></p>
<p class="MsoNormal">Chris<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal" style="mso-margin-top-alt:0in;margin-right:0in;margin-bottom:12.0pt;margin-left:.5in">
<b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Users <users-bounces@clusterlabs.org><br>
<b>Date: </b>Tuesday, October 19, 2021 at 1:17 PM<br>
<b>To: </b>users@clusterlabs.org <users@clusterlabs.org><br>
<b>Subject: </b>[ClusterLabs] Coming in Pacemaker 2.1.2: better display of internal failures<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal" style="margin-left:.5in">Hi all,<br>
<br>
I hope to get the first release candidate for Pacemaker 2.1.2 out in a<br>
couple of weeks.<br>
<br>
One improvement will be in status displays (crm_mon, and the<br>
crm_resource --force-* options) for failed actions.<br>
<br>
OCF resource agents already have the ability to output an "exit reason"<br>
for failures. These are displayed in the status, to give more detailed<br>
information than just "error".<br>
<br>
Now, Pacemaker will set exit reasons for internal failures as well.<br>
This includes problems such as an agent or systemd unit not being<br>
installed, timeouts in Pacemaker communication as opposed to the agent<br>
itself, an agent process being killed by a signal, etc.<br>
<br>
As an example, sending a kill -9 to a running agent monitor would<br>
previously result in status with no explanation, requiring some log<br>
diving to figure it out:<br>
<br>
* rsc1_monitor_60000 on node1 'error' (1): call=188, status='Error',<br>
exitreason='', last-rc-change='Fri Sep 24 14:45:02 2021', queued=0ms,<br>
exec=0ms<br>
<br>
Now, the exit reason will plainly say what happened:<br>
<br>
* rsc1_monitor_60000 on node1 'error' (1): call=188, status='Error',<br>
exitreason='Process interrupted by signal', last-rc-change='Fri Sep 24<br>
14:45:02 2021', queued=0ms, exec=0ms<br>
<br>
-- <br>
Ken Gaillot <kgaillot@redhat.com><br>
<br>
_______________________________________________<br>
Manage your subscription:<br>
<a href="https://lists.clusterlabs.org/mailman/listinfo/users">https://lists.clusterlabs.org/mailman/listinfo/users</a>
<br>
<br>
ClusterLabs home: <a href="https://www.clusterlabs.org/">https://www.clusterlabs.org/</a>
<o:p></o:p></p>
</div>
</div>
</body>
</html>