[Pacemaker] "op monitor timeout" not supported in my RA.

[Andrew Beekhof]

On 20 Aug 2014, at 5:15 pm, N, Ravikiran <ravikiran.n at hp.com> wrote:

> On 19 Aug 2014, at 5:31 pm, N, Ravikiran <ravikiran.n at hp.com> wrote:
> 
>> Hi
>> 
>> I have resource as ocf:heartbeat:ocrtms.
> 
> Please do not use the 'heartbeat' namespace for custom agents.
> [Ravikiran ] : Thanks for this info. Can u tell me which provider to use if not "Heartbeat"..?

Since you work for HP, "hp" sounds like a good option.
Just create a directory with that name under resource.d


>> I'm trying to create resource using as pcs as
>> 
>> "pcs resource create hpocrtms ocf:heartbeat:ocrtms cstype=active rtmsdir=/media/sf_Desktop/rtms" but when I add "op monitor interval=3s" to this statement, resource creation fails with the following error :
> 
> Do you mean you ran:
> 
> pcs resource create hpocrtms ocf:heartbeat:ocrtms cstype=active rtmsdir=/media/sf_Desktop/rtms
> 
> AND
> 
> pcs resource create hpocrtms ocf:heartbeat:ocrtms cstype=active rtmsdir=/media/sf_Desktop/rtms op monitor interval=3s
> 
> ?
> 
> Because that would try to create the same resource twice.
> [Ravikiran] : No, I did not run the same statement twice. First I tried 
> 
> pcs resource create hpocrtms ocf:heartbeat:ocrtms cstype=active rtmsdir=/media/sf_Desktop/rtms
> 
> which created the resource successfully. Then I delete this resource as 
> 
> pcs resource delete hpocrtms
> 
> Then, I tried running 
> 
> pcs resource create hpocrtms ocf:heartbeat:ocrtms cstype=active rtmsdir=/media/sf_Desktop/rtms op monitor interval=3s
> 
> which fails.
> Yes, you are right, we cannot have 2 resources with the same name.

Ah ok. Sorry, I had to ask.

> 
>> 
>> ERROR: Unable to create resource/fence device Call cib_create failed 
>> (-1003): Update does not conform to the configured schema
> 
> What version of pacemaker and pcs is this?

^^^ ?

Perhaps also try:

replacing:

<action name="monitor" depth="0"  timeout="20" interval="10" />

with:

<action name="monitor" depth="0"  timeout="20" interval="0" />

Quoting the arguments might also be of use, eg. rtmsdir="/media/sf_Desktop/rtms".

Also, try:

pcs resource describe ocrtms

that will tell you if the metadata is being parsed correctly

> 
>> 
>> My metadata is as below :
>> meta_data() {
>>                cat <<END
>> <?xml version="1.0"?>
>> <!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd"> <resource-agent 
>> name="hpocrtms"> <version>1.0</version>
>> 
>> <longdesc lang="en">
>> This is a Resource Agent for OC-RTMS_Server.
>> It outputs current cluster status to the html.
>> </longdesc>
>> <shortdesc lang="en">
>> Manages Collection Server.
>> </shortdesc>
>> 
>> <parameters>
>> 
>> <parameter name="pidfile" unique="0" required="0"> <longdesc 
>> lang="en">PID file</longdesc> <shortdesc lang="en">PID 
>> file</shortdesc> <content type="string" default="/var/run/rtmscs.pid" 
>> /> </parameter>
>> 
>> <parameter name="port" unique="0" required="0"> <longdesc lang="en"> 
>> This is the TCP port over which the RA shall interact with Collection 
>> server to know of any configuration or presence of the collection server.
>> </longdesc>
>> <shortdesc lang="en">TCP port</shortdesc> <content type="string" 
>> default="6789" /> </parameter>
>> 
>> <parameter name="user" unique="0">
>> <longdesc lang="en">
>> The user we want to run pingd as
>> </longdesc>
>> <shortdesc lang="en">The user we want to run pingd as</shortdesc> 
>> <content type="string" default="root" /> </parameter>
>> 
>> <parameter name="rtmsdir" unique="0" required="0"> <longdesc 
>> lang="en"> This is the base directory of the RTMS Collection Server 
>> installation.
>> By Default, its value is /opt/OC/rtms/ </longdesc> <shortdesc 
>> lang="en">RTMS Installtion directory</shortdesc> <content 
>> type="string" default="/media/sf_Desktop/rtms" /> </parameter> 
>> </parameters> <actions>
>> <action name="start"   timeout="20" />
>> <action name="stop"    timeout="20" />
>> <action name="status" depth="0"  timeout="20s" interval="10s" /> 
>> <action name="monitor" depth="0"  timeout="20" interval="10" /> 
>> <action name="meta-data"  timeout="5" /> <action name="validate-all"  
>> timeout="30" /> </actions> </resource-agent> END }
>> 
>> Am I Missing anything here.. ?? ;)
>> 
>> Regards,
>> Ravikiran N
>> 
>> 
>> _______________________________________________
>> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org 
>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>> 
>> Project Home: http://www.clusterlabs.org Getting started: 
>> http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20140820/8e9fb7e9/attachment-0003.sig>