Dear Pacemaker support, 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
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. 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. http://clusterlabs.org/pipermail/users/2015-August/001084.html 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. Thanks, Karthik.
_______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
