Re: [Pacemaker] [Problem] Error message of crm_failcount is not right.

2014-11-04 Thread renayama19661014
Hi Andrew, > I would suggest neither is correct. > I've changed it to: >  > [root@rh70-node1 ~]# crm_failcount  > You must supply a resource name to check. See 'crm_failcount --help' for  > details This is the message which is plain with kindness. Many Thanks! Hideo Yamauchi. - Origin

Re: [Pacemaker] [Problem] Error message of crm_failcount is not right.

2014-11-04 Thread Andrew Beekhof
> On 5 Nov 2014, at 1:05 pm, renayama19661...@ybb.ne.jp wrote: > > Hi All, > > The next error is displayed when I carry out crm_failcount of Pacemaker. > > [root@rh70-node1 ~]# crm_failcount >error: crm_abort:read_attr_delegate: Triggered assert at > cib_attrs.c:342 : attr_name != NUL

[Pacemaker] [Problem] Error message of crm_failcount is not right.

2014-11-04 Thread renayama19661014
Hi All, The next error is displayed when I carry out crm_failcount of Pacemaker. [root@rh70-node1 ~]# crm_failcount     error: crm_abort:    read_attr_delegate: Triggered assert at cib_attrs.c:342 : attr_name != NULL || attr_id != NULL However, I think that the next error should be displayed.

Re: [Pacemaker] stonith q

2014-11-04 Thread Andrew Beekhof
> On 5 Nov 2014, at 9:39 am, Alex Samad - Yieldbroker > wrote: > > > > >> I read to mean that demorp2 killed this node >>> Nov 4 23:21:37 >> demorp1 corosync[23415]: cman killed by node 2 because we were killed by >> cman_tool or other application > > Nov 4 23:21:37 demorp1

Re: [Pacemaker] stonith q

2014-11-04 Thread Alex Samad - Yieldbroker
> -Original Message- > From: Digimer [mailto:li...@alteeve.ca] > Sent: Wednesday, 5 November 2014 8:54 AM > To: Alex Samad - Yieldbroker; Andrei Borzenkov > Cc: The Pacemaker cluster resource manager > Subject: Re: [Pacemaker] stonith q > > On 04/11/14 02:45 PM, Alex Samad - Yieldbroker

Re: [Pacemaker] stonith q

2014-11-04 Thread Digimer
On 04/11/14 02:45 PM, Alex Samad - Yieldbroker wrote: {snip} Any pointers to a frame work somewhere ? I do not think there is any formal stonith agent developers guide; take at any existing agent like external/ipmi and modify to suite your needs. Does fenced have any handlers, I notice it

Re: [Pacemaker] One direction switchover not working

2014-11-04 Thread Andrew Beekhof
> On 4 Nov 2014, at 3:46 am, Andrei Borzenkov wrote: > > В Mon, 3 Nov 2014 15:05:39 +0530 > Arjun Pandey пишет: > >> Hi >> >> I have a 2 node CentOS -6.5 based cluster. This being run in active >> standby mode. >> When i want to trigger switchover from blackwidow to elektra (using >> 1.pcs st

Re: [Pacemaker] Occasional nonsensical resource agent errors, redux

2014-11-04 Thread Andrew Beekhof
> On 5 Nov 2014, at 4:21 am, Ken Gaillot wrote: > >>> Sep 13 20:17:07 pisces lrmd: [3509]: info: RA output: >>> (pan:monitor:stderr) /usr/lib/ocf/resource.d//heartbeat/Xen: 71: local: >> >> This "local" seems to be from ocf-binaries:have_binary(): >> >> 71 local bin=`echo $1 | sed -e 's/

Re: [Pacemaker] stonith q

2014-11-04 Thread Alex Samad - Yieldbroker
{snip} > >> Any pointers to a frame work somewhere ? > > > > I do not think there is any formal stonith agent developers guide; > > take at any existing agent like external/ipmi and modify to suite your > needs. > > > >> Does fenced have any handlers, I notice it logs a message in syslog and > clus

Re: [Pacemaker] Occasional nonsensical resource agent errors, redux

2014-11-04 Thread Ken Gaillot
On 11/04/2014 11:02 AM, Dejan Muhamedagic wrote: On 1 Nov 2014, at 11:03 pm, Patrick Kane wrote: Hi all: In July, list member Ken Gaillot reported occasional nonsensical resource agent errors using Pacemaker (http://oss.clusterlabs.org/pipermail/pacemaker/2014-July/022231.html). I was

Re: [Pacemaker] Occasional nonsensical resource agent errors, redux

2014-11-04 Thread Dejan Muhamedagic
Hi, On Mon, Nov 03, 2014 at 11:36:40AM -0500, Ken Gaillot wrote: > On 11/03/2014 09:26 AM, Dejan Muhamedagic wrote: >> On Mon, Nov 03, 2014 at 08:46:00AM +0300, Andrei Borzenkov wrote: >>> В Mon, 3 Nov 2014 13:32:45 +1100 >>> Andrew Beekhof пишет: >>> > On 1 Nov 2014, at 11:03 pm, Patric

Re: [Pacemaker] stonith q

2014-11-04 Thread Digimer
On 04/11/14 03:55 AM, Andrei Borzenkov wrote: В Mon, 3 Nov 2014 07:07:41 + Alex Samad - Yieldbroker пишет: {snip} What I am hearing is that its not available. Is it possible to hook to a custom script on that event, I can write my own restart Sure you can write your own external stonit

Re: [Pacemaker] environment variable for current timeout

2014-11-04 Thread Felix Zachlod
Am 04.11.2014 13:57, schrieb Felix Zachlod: So for my RA to do this I would need access to an environment variable that specifies the timeout of a specific action. Okay have found the answer myself studying the ocf-tester which sets OCF_RESKEY_CRM_meta_timeout so no answer needed anymore. r

[Pacemaker] environment variable for current timeout

2014-11-04 Thread Felix Zachlod
Hello! one thing in advance, yes I have read the OCF developer guide and I know that generally the cluster manager should take care of timeouts. Anyway I am in a special situation where I want my resource agent to monitor a timeout itself and return rather "partly configured" then to timeout

Re: [Pacemaker] stonith q

2014-11-04 Thread Andrei Borzenkov
В Mon, 3 Nov 2014 07:07:41 + Alex Samad - Yieldbroker пишет: > {snip} > > > What I am hearing is that its not available. Is it possible to hook to > > > a custom script on that event, I can write my own restart > > > > > > > Sure you can write your own external stonith script. > > > Any po