<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<p dir="ltr">Thanks, Mr.Gaillot. </p>
<p dir="ltr">Yes, we trigger the snmp notification with an external script. From your response, I understand that the issue wouldn't occur with 1.1.14, as it wouldn't require the crm_mon process. Is this understanding correct?
</p>
<p dir="ltr">We have been given 1.1.10 as the supported version from RedHat. If I raise a ticket to RedHat, would they be able to provide us a patch for 1.1.10?</p>
<p dir="ltr">Many thanks for your response.</p>
<p dir="ltr">Thanks,<br>
Karthik.</p>
<br>
<br>
---- Ken Gaillot எழுதியது ----<br>
<br>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 10/30/2015 05:29 AM, Karthikeyan Ramasamy wrote:<br>
> Dear Pacemaker support,<br>
> We are using pacemaker1.1.10-14 to implement a service management framework, with high availability on the road-map. This pacemaker version was available through redhat for our environments<br>
> <br>
> We are running into an issue where pacemaker causes a node to crash. The last feature we integrated was SNMP notification. While listing out the processes we found that crm_mon processes occupying 58GB of available 64GB, when the node crashed. When we
removed that feature, pacemaker was stable again.<br>
> <br>
> Section 7.1 of the pacemaker document details that SNMP notification agent triggers a crm_mon process at regular intervals. On checking clusterlabs for list of known issues, we found this crm_mon memory leak issue. Although not related, we think that there
is some problem with the crm_mon process.<br>
> <br>
> <a href="http://clusterlabs.org/pipermail/users/2015-August/001084.html">http://clusterlabs.org/pipermail/users/2015-August/001084.html</a><br>
> <br>
> Can you please let us know if there are issues with SNMP notification in Pacemaker or if there is anything that we could be wrong. Also, any workarounds for this issue if available, would be very helpful for us. Please help.<br>
> <br>
> Thanks,<br>
> Karthik.<br>
<br>
Are you using ClusterMon with Pacemaker's built-in SNMP capability, or<br>
an external script that generates the SNMP trap?<br>
<br>
If you're using the built-in capability, that has to be explicitly<br>
enabled when Pacemaker is compiled. Many distributions (including RHEL)<br>
do not enable it. Run "crm_mon --help"; if it shows a "-S" option, you<br>
have it enabled, otherwise not.<br>
<br>
If you're using an external script to generate the SNMP trap, please<br>
post it (with any sensitive info taken out of course).<br>
<br>
The ClusterMon resource will generate a crm_mon at regular intervals,<br>
but it should exit quickly. It sounds like it's not exiting at all,<br>
which is why you see this problem.<br>
<br>
If you have a RHEL subscription, you can open a support ticket with Red<br>
Hat. Note that stonith must be enabled before Red Hat (and many other<br>
vendors) will support a cluster. Also, you should be able to "yum<br>
update" to a much newer version of Pacemaker to get bugfixes, if you're<br>
using RHEL 6 or 7.<br>
<br>
FYI, the latest upstream Pacemaker has a new feature that will be in<br>
1.1.14, allowing it to call an external notification script without<br>
needing a ClusterMon resource.<br>
<br>
_______________________________________________<br>
Users mailing list: Users@clusterlabs.org<br>
<a href="http://clusterlabs.org/mailman/listinfo/users">http://clusterlabs.org/mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf">
http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org">http://bugs.clusterlabs.org</a><br>
</div>
</span></font>
</body>
</html>