Borja, I'm pretty confident that the system is not finding the file. I noticed that if stonith_admin cannot even find the fencing agent, it will still produce XML output, much like what you're seeing. To prove this, execute the following:
stonith_admin --metadata --agent=fence_blah I bet you see the same output as you're seeing now. I would check the following, in this order: 1. Verify you have the file/code that Andreas recently posted. You may even want to delete your existing fence_ec2 file and recopy the file, just to be safe. 2. Verify the permissions on the file. Mine are owned by root:root and 755. 3. Verify you have copied the file according to #1 above to all of your nodes. Let us know how it goes, and good luck! Best regards, Kevin F. La Barre Senior IT Engineer Infidati, Inc. -- (512) 696-1416 x6111 www.infidati.com On Thu, Oct 11, 2012 at 10:20 AM, Borja García de Vinuesa < [email protected]> wrote: > This is so strange. I swear I placed the new code there... > > [root@ha1 resource.d]# stonith_admin --metadata --agent=fence_ec2 > <?xml version="1.0"?> > <!DOCTYPE resource-agent SYSTEM "ra-api-1.dtd"> > <resource-agent name="fence_ec2"> > <version>1.0</version> > <longdesc lang="en"> > <!-- no value --> > </longdesc> > <shortdesc lang="en"><!-- no value --></shortdesc> > <parameters> > <parameter name="action"> > <getopt mixed="-o" /> > <content type="string" default="reboot" /> > <shortdesc lang="en">Fencing action (null, off, on, [reboot], > status, hostlist, devstatus)</shortdesc> > </parameter> > </parameters> > <actions> > <action name="start" timeout="20" /> > <action name="stop" timeout="15" /> > <action name="status" timeout="20" /> > <action name="monitor" timeout="20" interval="3600"/> > <action name="meta-data" timeout="15" /> > </actions> > <special tag="heartbeat"> > <version>2.0</version> > </special> > </resource-agent> > > > I cannot explain this? Where could I start from to solve this? I > mean..something is wrong..but don't know what. Andreas, anything that my > system could mess things up? > > Thank you people. > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Kevin F. La Barre > Sent: jueves, 11 de octubre de 2012 17:13 > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] STONITH for Amazon EC2 - fence_ec2 > > Borja, > > The new code that Andreas posted did the trick for me. Prior to the new > code, issuing "stonith_admin --metadata --agent fence_ec2" would list > metadata with only the "action" parameter. Once the new fence_ec2 code was > in place, the same command would output all the proper parameters. I did > not have to modify the fence_ec2 file at all to get it working (except for > some custom work which is specific to my environment). You should be able > to drop the file in the proper location (/usr/sbin for me) and run with it. > Do verify that you have the file Andreas refers to here as this is key: > https://raw.github.com/akurz/fence_ec2/master/fence_ec2 > > > Best regards, > > Kevin F. La Barre > Senior IT Engineer > Infidati, Inc. -- (512) 696-1416 x6111 > > > > On Thu, Oct 11, 2012 at 8:47 AM, Borja García de Vinuesa < > [email protected]> wrote: > > > Hi people, > > > > As Kevin, I'm trying to use fence_ec2 but exactly the same problem > > arises (just param action is listed when doing stonith_admin). It's > > weird because I'm using the last version of fence_ec2. Any idea why this > can happen? > > Kevin, did you do anything besides changing the code? > > Any further information you need just tell me. > > > > Thanks! > > > > > > Borja Gª de Vinuesa O. > > Communications Administrator > > Skype: borja.garcia.actualize > > > > > > [Descripción: LogoActualizeRGB] <http://www.actualize.es/> > > > > > > Avda. Valdelaparra, 27 > > P. E. Neisa Norte Edif. 1, 3ªpl. > > 28108 Alcobendas Madrid- España > > Tel. +34 91 799 40 70 > > Fax +34 91 799 40 79 > > www.actualize.es<http://www.actualize.es/> > > > > > > > > > > ESPAÑA * BRASIL * CHILE * COLOMBIA * MEXICO * UK > > > > > > Aviso sobre confidencialidad > > Este documento se dirige exclusivamente a su destinatario y puede > > contener información confidencial o cuya divulgación debe estar > > autorizada en virtud de la legislación vigente. Se informa a quien lo > > recibiera sin ser el destinatario o persona autorizada por éste, que > > la información contenida en el mismo es reservada y su utilización o > > divulgación con cualquier fin está prohibida. Si ha recibido este > > documento por error, le rogamos que nos lo comunique inmediatamente > > por esta misma vía o por teléfono, y proceda a su destrucción. > > > > Confidentiality and Privacy: If you have received this email in error, > > please notify the sender and delete it as well as any attachments. The > > e-mail and any attached files are intended only for the use of the > > person or organisation to whom they are addressed. It is prohibited > > and may be unlawful to use copy or disclose these documents unless > > authorised to do so. We may need to monitor emails we send and receive. > > > > > > _______________________________________________ > > Linux-HA mailing list > > [email protected] > > http://lists.linux-ha.org/mailman/listinfo/linux-ha > > See also: http://linux-ha.org/ReportingProblems > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
