Re: [ClusterLabs] பதில்: Re: crm_mon memory leak

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

[ClusterLabs] required nodes for quorum policy

Hi, I have a question regarding the policy to check for cluster quorum for corosync+pacemaker. As far as I know at present it is always (excpected_votes)/2 + 1. Seems like "qdiskd" has an option to change it, but it is not clear to me if corosync 2.x supports different quorum device. What are

Re: [ClusterLabs] பதில்: Re: crm_mon memory leak

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

Re: [ClusterLabs] Loadbalancing using Pacemaker

On 11/08/2015 11:29 AM, didier tanti wrote: > Thank You Michael, > In fact I spent some more time looking at documentions and indeed Pacemaker > is only used for resource control and management. To have my HA solution I > will need to use Corosync directly as well. The OpenAIS API is pretty well

Re: [ClusterLabs] move service basing on both connection status and hostname

On 11/09/2015 10:02 AM, Stefano Sasso wrote: > Hi Guys, > I am having some troubles with the location constraint. > > In particular, what I want to achieve, is to run my service on a host; if > the ip interconnection fails I want to migrate it to another host, but on > IP connectivity

Re: [ClusterLabs] move service basing on both connection status and hostname

Hi Ken, thanks for your reply. the problem was the resource-stickiness. thank you very much! bests stefano 2015-11-09 17:27 GMT+01:00 Ken Gaillot : > On 11/09/2015 10:02 AM, Stefano Sasso wrote: > > Hi Guys, > > I am having some troubles with the location constraint.

Re: [ClusterLabs] required nodes for quorum policy

On Tue, Nov 10, 2015 at 1:20 AM, Radoslaw Garbacz wrote: > Hi, > > I have a question regarding the policy to check for cluster quorum for > corosync+pacemaker. > > As far as I know at present it is always (excpected_votes)/2 + 1. Seems like > "qdiskd" has an

Re: [ClusterLabs] Howto use ocf:heartbeat:nginx check level > 0

On 11/08/2015 04:46 AM, user.clusterlabs@siimnet.dk wrote: > >> On 8. nov. 2015, at 10.26, user.clusterlabs@siimnet.dk wrote: >> >> Setting up my first pacemaker cluster, I’m trying to grasp howto make >> ocf:heartbeat:nginx monitor with check levels > 0. >> >> Got this so far: >> >>