On Fri, Oct 14, 2011 at 6:56 PM, <sagar.shi...@tieto.com> wrote: > Hi, > > I didn't find any link to download pacemaker-1.1.7.
Its not out yet. I said I implemented the feature _yesterday_. Sheesh. > Can you please pass me the link for download. > > Regards, > > Sagar Shimpi, Senior Technical Specialist, OSS Labs > > Tieto > email sagar.shi...@tieto.com, > Wing 1, Cluster D, EON Free Zone, Plot No. 1, Survery # 77, > MIDC Kharadi Knowledge Park, Pune 411014, India, www.tieto.com www.tieto.in > > TIETO. Knowledge. Passion. Results. > > -----Original Message----- > From: Andrew Beekhof [mailto:and...@beekhof.net] > Sent: Friday, October 14, 2011 4:51 AM > To: The Pacemaker cluster resource manager > Subject: Re: [Pacemaker] stonith_admin problems with Redhat6 > > On Thu, Oct 13, 2011 at 11:08 PM, <sagar.shi...@tieto.com> wrote: >> Hi, >> >> >> >> I am facing problem with configuring stonith on REDHAT6 on my virtual >> workstation. >> >> >> >> I am trying to configure stonith using fence_ack_manual for my vmware >> workstation as there is no hardware fencing device. > > fence_ack_manual isn't something you can configure. > its something you need to run, but is specific to rgmanager. > > i implemented the equivalent for pacemaker yesterday, look for it in 1.1.7 > >> >> >> >> Can anyone please help me in testing stonith configuration with >> fence_ack_manual, that will be gr8 for me.. >> >> >> >> >> >> Following are the errors - >> >> >> >> ======================================================================================================= >> [root@node1 ~]# crm ra info fence_ack_manual >> >> lrmadmin[12247]: 2011/10/04_15:31:53 ERROR: lrm_get_rsc_type_metadata(578): >> got a return code HA_FAIL from a reply message of rmetadata with function >> get_ret_from_msg. >> >> ERROR: ocf:heartbeat:fence_ack_manual: could not parse meta-data: >> >> [root@node1 ~]# >> >> >> >> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> >> [root@node1 ~]# crm ra info stonith:fence_ack_manual >> >> stonith:fence_ack_manual >> >> >> >> <!-- no value --> >> >> >> >> Parameters (* denotes required, [] the default): >> >> >> >> action (string, [reboot]): Fencing action (null, off, on, [reboot], status, >> hostlist, devstatus) >> >> stonith-timeout (time, [60s]): How long to wait for the STONITH action to >> complete. >> >> Overrides the stonith-timeout cluster property >> >> >> >> priority (integer, [0]): The priority of the stonith resource. The lower the >> number, the higher the priority. >> >> pcmk_arg_map (string): A mapping of host attributes to device arguments. >> >> Eg. uname:domain would tell the cluster to pass the machines name as the >> domain argument to the device. Useful for devices that have non-standard >> interfaces >> >> >> >> pcmk_host_map (string): A mapping of host names to ports numbers for devices >> that do not support names. >> >> Eg. node1:1,node2:3 would tell the cluster to use port 1 for node1 and >> port 3 for node2 >> >> >> >> pcmk_host_list (string): A list of machines controlled by this device >> (Optional unless pcmk_host_check=static-list). >> >> pcmk_host_check (string, [dynamic-list]): How to determin which machines are >> controlled by the device. >> >> Allowed values: dynamic-list (query the device), static-list (check the >> pcmk_host_list attribute), none (assume every device can fence every >> machine) >> >> >> >> pcmk_list_cmd (string, [list]): Which device operation to use for listing >> machines controlled by the device. >> >> pcmk_status_cmd (string, [status]): Which device operation to use for >> testing the state of a machine controlled by the device. >> >> pcmk_monitor_cmd (string, [monitor]): Which device operation to use for >> monitoring the health of the device. >> >> >> >> Operations' defaults (advisory minimum): >> >> >> >> start timeout=15 >> >> stop timeout=15 >> >> status timeout=15 >> >> monitor_0 interval=15 timeout=15 start-delay=15 >> >> [root@node1 ~]# >> >> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> >> >> >> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> >> >> >> [root@node1 ~]# stonith_admin --metadata --agent type >> >> stonith_admin[11852]: 2011/10/04_15:30:35 info: crm_log_init_worker: Changed >> active directory to /var/lib/heartbeat/cores/root >> >> stonith_admin[11852]: 2011/10/04_15:30:35 ERROR: get_stonith_provider: No >> such device: type >> >> stonith_admin[11852]: 2011/10/04_15:30:35 info: stonith_api_device_metadata: >> looking up type/(null) metadata >> >> stonith_admin[11852]: 2011/10/04_15:30:35 ERROR: crm_abort: crm_strdup_fn: >> Triggered assert at utils.c:822 : src != NULL >> >> stonith_admin[11852]: 2011/10/04_15:30:35 ERROR: crm_strdup_fn: Could not >> perform copy at st_client.c:507 (stonith_api_device_metadata) >> >> stonith_admin[11852]: 2011/10/04_15:30:35 WARN: stonith_api_device_metadata: >> no long description in type's metadata. >> >> stonith_admin[11852]: 2011/10/04_15:30:35 ERROR: crm_abort: crm_strdup_fn: >> Triggered assert at utils.c:822 : src != NULL >> >> stonith_admin[11852]: 2011/10/04_15:30:35 ERROR: crm_strdup_fn: Could not >> perform copy at st_client.c:513 (stonith_api_device_metadata) >> >> stonith_admin[11852]: 2011/10/04_15:30:35 info: stonith_api_device_metadata: >> short description: (null) >> >> stonith_admin[11852]: 2011/10/04_15:30:35 WARN: stonith_api_device_metadata: >> no short description in type's metadata. >> >> stonith_admin[11852]: 2011/10/04_15:30:35 ERROR: crm_abort: crm_strdup_fn: >> Triggered assert at utils.c:822 : src != NULL >> >> stonith_admin[11852]: 2011/10/04_15:30:35 ERROR: crm_strdup_fn: Could not >> perform copy at st_client.c:520 (stonith_api_device_metadata) >> >> stonith_admin[11852]: 2011/10/04_15:30:35 WARN: stonith_api_device_metadata: >> no list of parameters in type's metadata. >> >> <?xml version="1.0"?> >> >> <!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd"> >> >> <resource-agent name="type"> >> >> <version>1.0</version> >> >> <longdesc lang="en"> >> >> <!-- no value --> >> >> </longdesc> >> >> <shortdesc lang="en"><!-- no value --></shortdesc> >> >> <!-- no value --> >> >> <actions> >> >> <action name="start" timeout="15" /> >> >> <action name="stop" timeout="15" /> >> >> <action name="status" timeout="15" /> >> >> <action name="monitor" timeout="15" interval="15" start-delay="15" /> >> >> <action name="meta-data" timeout="15" /> >> >> </actions> >> >> <special tag="heartbeat"> >> >> <version>2.0</version> >> >> </special> >> >> </resource-agent> >> >> [root@node1 ~]# >> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> >> [root@node1 ~]# stonith_admin -t ssh -n >> >> stonith_admin[11980]: 2011/10/04_15:31:00 info: crm_log_init_worker: Changed >> active directory to /var/lib/heartbeat/cores/root >> >> stonith_admin: invalid option -- 't' >> >> stonith_admin - Provides access to the stonith-ng API. >> >> >> >> Usage: stonith_admin mode [options] >> >> Options: >> >> -?, --help This text >> >> -$, --version Version information >> >> -V, --verbose Increase debug output >> >> -l, --list=value List devices that can terminate the specified host >> >> -L, --list-all List all registered devices >> >> -M, --metadata Check the device's metadata >> >> -Q, --query=value Check the device's status >> >> -F, --fence=value Fence the named host >> >> -U, --unfence=value Unfence the named host >> >> -C, --confirm=value Confirm the named host is now safely down >> >> -R, --register=value Register a stonith device >> >> -D, --deregister=value De-register a stonith device >> >> -e, --env-option=value >> >> -o, --option=value >> >> -a, --agent=value >> >> >> >> Report bugs to pacemaker@oss.clusterlabs.org >> >> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- >> >> >> >> >> >> >> >> Regards, >> >> >> >> Sagar Shimpi, Senior Technical Specialist, OSS Labs >> >> >> >> Tieto >> >> email sagar.shi...@tieto.com, >> >> Wing 1, Cluster D, EON Free Zone, Plot No. 1, Survery # 77, >> >> MIDC Kharadi Knowledge Park, Pune 411014, India, www.tieto.com www.tieto.in >> >> TIETO. Knowledge. Passion. Results. >> >> >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker >> >> > > _______________________________________________ > Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > > _______________________________________________ > Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker > _______________________________________________ Pacemaker mailing list: Pacemaker@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://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
