Hi Ken,
The script now exits properly with 'exit 0'. But it still it creates hanging
processes, as listed below.
root 13405 1 0 13:42 ?00:00:00 /usr/sbin/crm_mon -p
/tmp/ClusterMon_SNMP_10.64.109.36.pid -d -i 15 -E
/opt/occ/CXP_902_0588_R13B2370/tools/PCSESA.sh -h
On 11/09/2015 07:11 AM, Karthikeyan Ramasamy wrote:
> Hi Ken,
> The script now exits properly with 'exit 0'. But it still it creates
> hanging processes, as listed below.
>
> root 13405 1 0 13:42 ?00:00:00 /usr/sbin/crm_mon -p
> /tmp/ClusterMon_SNMP_10.64.109.36.pid -d -i 15
Hi Ken,
Both CPU and this SNMP notification were interrelated, as the number of
retries was infinite. As a service was down, for every retry it was trying to
send a notification as well and that stalled Pacemaker.
Thanks,
Karthik.
-Original Message-
From: Karthikeyan Ramasamy
Sent:
Yes, Ken. There were multiple instances of the external script also running.
What do you think could possibly be wrong with the script that triggers the
crm_mon process everytime?
We are on RHEL 6.5. I am not sure what's the plan for RHEL 6.7 and 7.1.
Thanks,
Karthik.
-Original
Many thanks. Will check and get back.
-Original Message-
From: Ken Gaillot [mailto:kgail...@redhat.com]
Sent: 02 நவம்பர் 2015 21:21
To: Karthikeyan Ramasamy; users@clusterlabs.org
Subject: Re: பதில்: Re: [ClusterLabs] crm_mon memory leak
On 11/02/2015 09:39 AM, Karthikeyan Ramasamy
On 11/02/2015 09:39 AM, Karthikeyan Ramasamy wrote:
> Yes, Ken. There were multiple instances of the external script also running.
> What do you think could possibly be wrong with the script that triggers the
> crm_mon process everytime?
It's the other way around, crm_mon spawns the script.
On 10/31/2015 12:38 AM, Karthikeyan Ramasamy wrote:
> Thanks, Mr.Gaillot.
>
> 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
Thanks, Mr.Gaillot.
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?
We have been given 1.1.10 as the supported version from
