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
On 11/01/2015 03:43 AM, Karthikeyan Ramasamy wrote:
> Thanks, Ken.
>
> I understand about stonith. We are introducing pacemaker for an existing
> product not for a new product. Currently, client-side is responsible for
> load-balancing.
>
> High-availability for our product is the next
Hi all.
We have one cluster that has 9 nodes and 20 resources.
Four of those hosts are PSIP-SRV01-active, PSIP-SRV01-passive,
PSIP-SRV02-active and PSIP-SRV02-active.
They should provide an lsb:opensips service, 2 by 2:
. The SRV01-opensips and SRV01-IP resources should be active
