Re: [Pacemaker] process/service watcher

2014-03-13 Thread Frank Brendel
en (yaogen): Thanks Frank, so you confirm that pacemaker doesn't offer this? Yair *From:*Frank Brendel [mailto:frank.bren...@eurolog.com] *Sent:* Thursday, March 13, 2014 16:05 *To:* The Pacemaker cluster resource manager *Subject:* Re: [Pacemaker] process/service watcher Hi Yair,

Re: [Pacemaker] process/service watcher

2014-03-13 Thread Frank Brendel
Hi Yair, try monit http://mmonit.com/monit/ Regards Frank Am 13.03.2014 14:24, schrieb Yair Ogen (yaogen): Does pacemaker have an option to act as a process / service watcher regardless to being part of a cluster? i.e. watch a process and identify when it's down and re-start it. I am loo

Re: [Pacemaker] Stopping resource using pcs

2014-03-05 Thread Frank Brendel
_is_ that the resource name though? From one of your earlier examples: It's an example from me not from Kiran. # pcs resource clone groupPing clone-max=3 clone-node-max=1 # pcs resource Clone Set: groupPing-clone [groupPing] The name you should be passing to pcs is groupPing-clone, _not_ g

Re: [Pacemaker] Stopping resource using pcs

2014-02-26 Thread Frank Brendel
I guess we need some real experts here. I think it's because you're attempting to delete the resource and not the Master. Try deleting the Master instead of the resource. I had a similar problem with a cloned group and solved it by un-cloning before deleting the group. Maybe un-cloning the m

Re: [Pacemaker] Stopping resource using pcs

2014-02-26 Thread Frank Brendel
t=(null), section=status Feb 26 02:28:19 sys11 crmd[4127]: notice: process_lrm_event: LRM operation vha-de5566b1-c2a3-4dc6-9712-c82bb43f19d8_stop_0 (call=27, rc=0, cib-update=303, confirmed=true) ok Feb 26 02:28:19 sys11 crmd[4127]: notice: run_graph: Transition 14 (Complete=7, Pending=0, F

Re: [Pacemaker] Stopping resource using pcs

2014-02-25 Thread Frank Brendel
No erros in syslog? Am 25.02.2014 15:45, schrieb K Mehta: Frank, Creation/Disabling/Deletion of non multi state resource worked fine. When I try to delete a multi state resource, the resource goes into stopped state and the following error is thrown Error: unable to stop: . Regards,

Re: [Pacemaker] Stopping resource using pcs

2014-02-24 Thread Frank Brendel
Hi Kiran, the man page says (or use 'pcs resource help') disable [--wait[=n]] Attempt to stop the resource if it is running and forbid the cluster from starting it again. Depending on the rest of the configuration (constraints, options, failures, etc), the resource ma

Re: [Pacemaker] Migrating resources on custom conditions

2014-02-21 Thread Frank Brendel
Another idea is to create a pacemaker:HealthCPU resource that updates the #health-cpu attribute. Now you can add a location constraint to your resource to migrate away if #health-cpu is, lets say 'red'. # pcs resource describe ocf:pacemaker:HealthCPU Resource options for: ocf:pacemaker:HealthCP

Re: [Pacemaker] Restart of resources

2014-02-07 Thread Frank Brendel
Its somewhat inferred in the description of cluster-recheck-interval cluster-recheck-interval = time [15min] Polling interval for time based changes to options, resource parameters and constraints. The Cluster is primarily event driven, however the configuratio

Re: [Pacemaker] LSB openswan script monitor problems

2014-02-04 Thread Frank Brendel
Please could you post the init script, the resource configuration and the pacemaker version? Frank The return code of "service ipsec status" is always 0 yet crm status shows the failure: p_ipsec_monitor_15000 on node02 'not running' (7): call=113, status=complete, last-rc-change='Mon Jan 2

Re: [Pacemaker] Kamailio managed by Pacemaker

2014-02-03 Thread Frank Brendel
Default shell on Ubuntu is dash. You can set bash as default shell. Try 'dpkg-reconfigure dash' or use update-alternatives(8). Frank Am 03.02.2014 18:16, schrieb Sherwood McGowan: > I found that on Ubuntu servers, the /bin/sh designation fails, but if > you use /bin/bash, it works fine > > On 1

Re: [Pacemaker] LSB openswan script monitor problems

2014-02-03 Thread Frank Brendel
As far as I know, Pacemaker does not parse STDOUT but it keeps STDERR for logging. Experts correct me if I am wrong. The important thing is the return value of the ipsec script. You could debug the ipsec script. If it is a Bash script you can put a logger command after each 'RETVAL=$?'. Example

Re: [Pacemaker] Restart of resources

2014-02-03 Thread Frank Brendel
here http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html-single/Pacemaker_Explained/index.html Regards Frank Am 28.01.2014 14:44, schrieb Frank Brendel: > No one with an idea? > Or can someone tell me if it is even possible? > > > Thanks > Frank > > > Am 23.01.2

Re: [Pacemaker] Running remote SSH commands on another server?

2014-01-31 Thread Frank Brendel
Are you aware that the script returns 0 in case that the ssh command fails? You can test your script as described here http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html/Pacemaker_Explained/ap-lsb.html A better method would be to write your own resource agent. Have a look at the MailTo ag

Re: [Pacemaker] New fence Agent for Proxmox VE

2014-01-29 Thread Frank Brendel
fencing library and include it in fence-agents package. If you do not >> have any objections and you are willing to help us with testing, we can >> do that porting in few days. >> >> m, >> >> >> On 01/29/2014 09:53 AM,

Re: [Pacemaker] New fence Agent for Proxmox VE

2014-01-29 Thread Frank Brendel
> Yup, as an attachment to this list. > > Cheers > Oh, so simple :-) Frank fence_pve-1.0.0.tar.gz Description: fence_pve-1.0.0.tar.gz ___ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Pro

Re: [Pacemaker] New fence Agent for Proxmox VE

2014-01-28 Thread Frank Brendel
Am 28.01.2014 15:45, schrieb Digimer: > On 28/01/14 09:07 AM, Frank Brendel wrote: >> Hi list, >> >> I've written a fence agent for the Proxmox Virtual Environment to fence >> virtual Pacemaker nodes, similar to fence_vmware. >> >> I'd like to

[Pacemaker] New fence Agent for Proxmox VE

2014-01-28 Thread Frank Brendel
Hi list, I've written a fence agent for the Proxmox Virtual Environment to fence virtual Pacemaker nodes, similar to fence_vmware. I'd like to contribute it but I don't know who is responsible. Thanks Frank ___ Pacemaker mailing list: Pacemaker@oss.c

Re: [Pacemaker] Restart of resources

2014-01-28 Thread Frank Brendel
No one with an idea? Or can someone tell me if it is even possible? Thanks Frank Am 23.01.2014 10:50, schrieb Frank Brendel: > Hi list, > > I have some trouble configuring a resource that is allowed to fail > once in two minutes. > The documentation states that I have to conf

Re: [Pacemaker] not able to configure operations(op) using pcs command

2014-01-23 Thread Frank Brendel
Hi Parveen, my pacmaker version is 1.1.10 and pcs is 0.9.90 and it works as expected. The bug you mentioned is fixed in pcs version 0.9.64. pacemaker 1.1.8 is in RHEL 6.4 from February 2013. There is an update version 1.1.10 from November 2013. Likely they fixed it already an you should update

Re: [Pacemaker] not able to configure operations(op) using pcs command

2014-01-23 Thread Frank Brendel
Hi Parveen, specify 'op' only once. pcs resource create app-prim ocf:appprim:appmmra apigw_health_check_port=55000 appmm_instance_name=appgw op stop interval=0 timeout=60s monitor interval=1s timeout=5s start interval=0 timeout=60s see 'pcs resource help' create [resource options]

[Pacemaker] Restart of resources

2014-01-23 Thread Frank Brendel
Hi list, I have some trouble configuring a resource that is allowed to fail once in two minutes. The documentation states that I have to configure migration-threshold and failure-timeout to achieve this. Here is the configuration for the resource. # pcs config Cluster Name: mycluster Corosync N