Hii,<br><br> How can we apply encryption in corosync layer???<br><br><div class="gmail_quote">On Tue, Sep 4, 2012 at 4:34 PM, <span dir="ltr"><<a href="mailto:pacemaker-request@oss.clusterlabs.org" target="_blank">pacemaker-request@oss.clusterlabs.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send Pacemaker mailing list submissions to<br>
<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:pacemaker-request@oss.clusterlabs.org">pacemaker-request@oss.clusterlabs.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:pacemaker-owner@oss.clusterlabs.org">pacemaker-owner@oss.clusterlabs.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Pacemaker digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Pacemaker Digest (Deepshikha Singh)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 4 Sep 2012 16:32:55 +0530<br>
From: Deepshikha Singh <<a href="mailto:deepshikhasingh@drishti-soft.com">deepshikhasingh@drishti-soft.com</a>><br>
To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
Subject: [Pacemaker] Pacemaker Digest<br>
Message-ID:<br>
<<a href="mailto:CAJ9vscPvBvm5kKKxQdiMCvRtk0b8PQyDBmOChhhMp3rKK0AqYg@mail.gmail.com">CAJ9vscPvBvm5kKKxQdiMCvRtk0b8PQyDBmOChhhMp3rKK0AqYg@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="iso-8859-1"<br>
<br>
Hii,<br>
Sorry if I am repeating my question.My question is that<br>
pacmaker also work on WAN, if yes then how????<br>
<br>
<br>
Thank you<br>
On Tue, Sep 4, 2012 at 3:01 PM, <<a href="mailto:pacemaker-request@oss.clusterlabs.org">pacemaker-request@oss.clusterlabs.org</a>>wrote:<br>
<br>
> Send Pacemaker mailing list submissions to<br>
> <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
><br>
> To subscribe or unsubscribe via the World Wide Web, visit<br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
> or, via email, send a message with subject or body 'help' to<br>
> <a href="mailto:pacemaker-request@oss.clusterlabs.org">pacemaker-request@oss.clusterlabs.org</a><br>
><br>
> You can reach the person managing the list at<br>
> <a href="mailto:pacemaker-owner@oss.clusterlabs.org">pacemaker-owner@oss.clusterlabs.org</a><br>
><br>
> When replying, please edit your Subject line so it is more specific<br>
> than "Re: Contents of Pacemaker digest..."<br>
><br>
><br>
> Today's Topics:<br>
><br>
> 1. RES: "Using ldirectord" page question (Carlos Xavier)<br>
> 2. Re: Compilation problem in centos 6.3 (Vladislav Bogdanov)<br>
> 3. Change Hostname (Thorsten Rehm)<br>
> 4. Re: Change Hostname (Vit Pelcak)<br>
> 5. Re: Change Hostname (Thorsten Rehm)<br>
> 6. Re: Pacemaker Digest, Vol 58, Issue 3 (Deepshikha Singh)<br>
><br>
><br>
> ----------------------------------------------------------------------<br>
><br>
> Message: 1<br>
> Date: Tue, 4 Sep 2012 01:34:38 -0300<br>
> From: "Carlos Xavier" <<a href="mailto:cbastos@connection.com.br">cbastos@connection.com.br</a>><br>
> To: "'The Pacemaker cluster resource manager'"<br>
> <<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
> Subject: [Pacemaker] RES: "Using ldirectord" page question<br>
> Message-ID: <000001cd8a56$9bdf36d0$d39da470$@<a href="http://com.br" target="_blank">com.br</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
> Hi.<br>
><br>
> The virtual IP on the loopback are needed for the real servers, so as they<br>
> can answer the packets sent to them.<br>
> You also need to edit the file /etc/sysctl.conf to disable the reply to arp<br>
> requests of the virtual addresses configured on the loopback.<br>
> This is what I had to add to my web servers sysctl.conf, adjust it to your<br>
> configuration:<br>
> ########<br>
> # Enable configuration of arp_ignore option<br>
> net.ipv4.conf.all.arp_ignore = 1<br>
><br>
> # When an arp request is received on eth0, only respond if that address is<br>
> # configured on eth0. In particular, do not respond if the address is<br>
> # configured on lo<br>
> net.ipv4.conf.eth0.arp_ignore = 1<br>
><br>
> # Ditto for eth1, add for all ARPing interfaces<br>
> net.ipv4.conf.bond0.arp_ignore = 1<br>
> net.ipv4.conf.vlan0.arp_ignore = 1<br>
><br>
><br>
> # Enable configuration of arp_announce option<br>
> net.ipv4.conf.all.arp_announce = 2<br>
><br>
> # When making an ARP request sent through eth0 Always use an address that<br>
> # is configured on eth0 as the source address of the ARP request. If this<br>
> # is not set, and packets are being sent out eth0 for an address that is on<br>
> # lo, and an arp request is required, then the address on lo will be used.<br>
> # As the source IP address of arp requests is entered into the ARP cache on<br>
> # the destination, it has the effect of announcing this address. This is<br>
> # not desirable in this case as adresses on lo on the real-servers should<br>
> # be announced only by the linux-director.<br>
> net.ipv4.conf.eth0.arp_announce = 2<br>
><br>
> # Ditto for eth1, add for all ARPing interfaces<br>
> net.ipv4.conf.bond0.arp_announce = 2<br>
> net.ipv4.conf.vlan0.arp_announce = 2<br>
> ########<br>
><br>
> I?m configuring some servers to work with ldiretord, but my approach as a<br>
> little bit different, I already have a cluster working for mysql and they<br>
> will be the ldirector manager and I configured anther cluster just to<br>
> manage<br>
> http/https<br>
><br>
> Regards,<br>
> Carlos<br>
><br>
><br>
> -----Mensagem original-----<br>
> De: Dennis Jacobfeuerborn [mailto:<a href="mailto:dennisml@conversis.de">dennisml@conversis.de</a>]<br>
> Enviada em: segunda-feira, 3 de setembro de 2012 23:28<br>
> Para: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> Assunto: [Pacemaker] "Using ldirectord" page question<br>
><br>
> > Hi,<br>
> > I'm trying to set up a redundant load-balancer using pacemaker and<br>
> ldirectord and found an example for the configuration on the following<br>
> page:<br>
> > <a href="http://www.clusterlabs.org/wiki/Using_ldirectord" target="_blank">http://www.clusterlabs.org/wiki/Using_ldirectord</a><br>
><br>
> > What I don't understand is the following part:<br>
> > "This gives you the virtual IP address and ldirectord running together in<br>
> a group (ip-lvs) on one node, and the same virtual IP address assigned to<br>
> the loopback address on all other nodes. This is necessary to make the<br>
> routing work correctly. "<br>
><br>
> > Why is the configuration of the IP on the lo interfaces necessary for<br>
> routing?<br>
> > As far as I understand is the VIP only needs to run on the active node<br>
> that is also running the ldirectord daemon. Once the failover happens both<br>
> move over to the new active node and the setup should continue to work as<br>
> before. Is there something I'm missing here?<br>
><br>
> > Regards,<br>
> > Dennis<br>
><br>
><br>
><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 2<br>
> Date: Tue, 04 Sep 2012 08:55:27 +0300<br>
> From: Vladislav Bogdanov <<a href="mailto:bubble@hoster-ok.com">bubble@hoster-ok.com</a>><br>
> To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> Subject: Re: [Pacemaker] Compilation problem in centos 6.3<br>
> Message-ID: <<a href="mailto:504597CF.2090602@hoster-ok.com">504597CF.2090602@hoster-ok.com</a>><br>
> Content-Type: text/plain; charset=windows-1252<br>
><br>
> 04.09.2012 03:46, Keisuke MORI wrote:<br>
> > Hi,<br>
> ><br>
> > I've seen a similar problem.<br>
> > It was caused by an unseen escape sequence produced by the crm shell<br>
> > (readline library in particular) when TERM=xterm.<br>
> ><br>
> > Try "export TERM=vt100" and rebuild it.<br>
> > Or grab the latest crm shell.<br>
><br>
> Shouldn't it be listed as build dep if docs are enabled in spec then?<br>
> Although, as crm shell is not longer part of pacemaker and it heavily<br>
> depends on pacemaker utils, it could be hard to implement correct<br>
> cross-deps between two packages (also heaving in mind that there is no<br>
> crmsh package in fedora yet). So, may be it is better to include some<br>
> example crm shell output in sources rather then trying to run it at the<br>
> build time? I do not have crm shell installed on my build systems and<br>
> docs I get are inconsistent - sys::[crm --help] resolves to an empty<br>
> string. Just checked it.<br>
> If would be fine to replace sys::[crm --help] with<br>
> sys::[cat crm_--help.txt] having crm_--help.txt exists in tarball and is<br>
> regenerated if local crm shell is found and is newer than one used to<br>
> generate original output. Of course that is a lot of work. And I'm not<br>
> sure what to do with crm shell output i18n (after/if it has one).<br>
><br>
> ><br>
> > 2012/9/4 Miguel Angel Guerrero <<a href="mailto:miguel.guerrero@itac.com.co">miguel.guerrero@itac.com.co</a>><br>
> >><br>
> >> Hi all<br>
> >><br>
> >> I'm trying to compile the last version of the src package of pacemaker<br>
> from red hat in centos 6.3 with snmp support but i get this error in the<br>
> process and i don't understand this, i check the dependencies and all is<br>
> correct, thanks for your help<br>
> >><br>
> >> Processing file tmp/en-US/xml_tmp/Ch-Tools.xml -><br>
> tmp/en-US/xml/Ch-Tools.xml<br>
> >><br>
> >> not well-formed (invalid token) at line 20, column 8, byte 884:<br>
> >> <para>Take some time to familiarize yourself with what it can do.</para><br>
> >> <para># <command>crm --help</command></para><br>
> >> <screen><br>
> >> =======^<br>
> >> usage:<br>
> >> crm [-D display_type] [-f file] [-hF] [args]<br>
> >> at /usr/lib64/perl5/XML/Parser.pm line 187<br>
> >> gmake[1]: *** [Clusters_from_Scratch.txt] Error 255<br>
> >> gmake[1]: Leaving directory<br>
> `/home/itac/rpmbuild/BUILD/ClusterLabs-pacemaker-148fccf/doc'<br>
> >> make: *** [all-recursive] Error 1<br>
> >> error: Estado de salida err?neo de /var/tmp/rpm-tmp.yHX51k (%build)<br>
> >><br>
> >><br>
> >> Errores de construcci?n RPM:<br>
> >> InstallSourcePackage at: psm.c:244: CabeceraV3 RSA/SHA256<br>
> Signature, ID de clave fd431d51: NOKEY<br>
> >> Estado de salida err?neo de /var/tmp/rpm-tmp.yHX51k (%build)<br>
> >><br>
> >><br>
> >> --<br>
> >><br>
> >><br>
> >> <a href="http://www.itac.com.co" target="_blank">www.itac.com.co</a><br>
> >><br>
> >> Miguel Angel Guerrero<br>
> >> Ingeniero de Infraestructura<br>
> >><br>
> >> ITAC - IT Applications Consulting<br>
> >> Avenida 19 # 114 ? 65 Oficina 215<br>
> >> Bogota, DC. Colombia<br>
> >> Telefono (+571) 6400338 Ext. 147<br>
> >> <a href="mailto:miguel.guerrero@itac.com.co">miguel.guerrero@itac.com.co</a><br>
> >><br>
> >> ________________________________<br>
> >><br>
> >> Nuestros clientes hacen parte de la calidad que brindamos por lo que lo<br>
> invitamos a que si tiene una queja, reclamo o sugerencia nos la haga saber<br>
> a <a href="mailto:calidad@itac.com.co">calidad@itac.com.co</a><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >><br>
> >> _______________________________________________<br>
> >> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> >> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
> >><br>
> >> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> >> Getting started:<br>
> <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> >> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
> >><br>
> ><br>
> ><br>
> ><br>
> > --<br>
> > Keisuke MORI<br>
> ><br>
> > _______________________________________________<br>
> > Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
> ><br>
> > Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> > Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> > Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
> ><br>
><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 3<br>
> Date: Tue, 4 Sep 2012 10:28:23 +0200<br>
> From: Thorsten Rehm <<a href="mailto:thorsten.rehm@gmail.com">thorsten.rehm@gmail.com</a>><br>
> To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> Subject: [Pacemaker] Change Hostname<br>
> Message-ID:<br>
> <CABT3_pxBBNBFPc=<br>
> <a href="mailto:T6YdmZDPku1FEdo%2BiFWGPLDtGTXy5vRnxQg@mail.gmail.com">T6YdmZDPku1FEdo+iFWGPLDtGTXy5vRnxQg@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset=ISO-8859-1<br>
><br>
> Hi everyone,<br>
><br>
> I have a cluster with three nodes (stack: heartbeat) and I need to<br>
> change the hostname of all systems (only the hostname, not the ip<br>
> address or other network configuration). I have already made several<br>
> attempts, but so far I have not managed that resources are available<br>
> without interruption, after I changed the hostname. Is there a<br>
> procedure that allows me to change the hostname, without loss of<br>
> resources? If so, how would this look like? Is there a best case?<br>
><br>
><br>
> Cheers,<br>
> Thorsten<br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 4<br>
> Date: Tue, 04 Sep 2012 10:38:24 +0200<br>
> From: Vit Pelcak <<a href="mailto:vpelcak@suse.cz">vpelcak@suse.cz</a>><br>
> To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> Subject: Re: [Pacemaker] Change Hostname<br>
> Message-ID: <<a href="mailto:5045BE00.7020703@suse.cz">5045BE00.7020703@suse.cz</a>><br>
> Content-Type: text/plain; charset=ISO-8859-1<br>
><br>
> -----BEGIN PGP SIGNED MESSAGE-----<br>
> Hash: SHA1<br>
><br>
> Dne 4.9.2012 10:28, Thorsten Rehm napsal(a):<br>
> > Hi everyone,<br>
> ><br>
> > I have a cluster with three nodes (stack: heartbeat) and I need to<br>
> > change the hostname of all systems (only the hostname, not the ip<br>
> > address or other network configuration). I have already made<br>
> > several attempts, but so far I have not managed that resources are<br>
> > available without interruption, after I changed the hostname. Is<br>
> > there a procedure that allows me to change the hostname, without<br>
> > loss of resources? If so, how would this look like? Is there a best<br>
> > case?<br>
><br>
><br>
> Hm. What about modifying corosync.conf to reflect hostname change on<br>
> all nodes, restarting corosync on all one after another (so you always<br>
> have at least 2 nodes running corosync and resources) and then<br>
> changing that hostname on desired machine and restarting corosync on it?<br>
><br>
> In general, do not stop corosync on more than 1 node at the time and<br>
> you should be safe.<br>
><br>
> > Cheers, Thorsten<br>
> ><br>
> > _______________________________________________ Pacemaker mailing<br>
> > list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
> ><br>
> > Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a> Getting started:<br>
> > <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a> Bugs:<br>
> > <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
> -----BEGIN PGP SIGNATURE-----<br>
> Version: GnuPG v2.0.19 (GNU/Linux)<br>
> Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
><br>
> iQEcBAEBAgAGBQJQRb4AAAoJEG+ytY6bjOob0AUH+gKl8OXHnGUUkXe4rFNc1qqr<br>
> W1hkafkjDOl2k475kiXiJ9CbgvP4mJSZJ+naMvyh53BJDuWiZH4i3kl1KZVSCvQ6<br>
> DNrZhHG90BmTLXiE6tCeVWP6K5tKamvLCRGBehiu83lW2kdH0X3uF9KqZlPnBFhy<br>
> AeEYvCsJKfM+u7WndNDFeQVdV//FQaHAB8JZBkgSyHmlvN+bnjUzRTOE1qLyv3/b<br>
> nPYVBOYCJgBjmENRRMoP1xWZgAAMeRCzRrpXo2ZSJ8945E/pmc1+9fPDJCqBXqvr<br>
> CFzI7iZcyidfpKq6h1S9dlDDMdRidj9P8kfEokThtHXpy45/LhdzYrMg6LmvuIc=<br>
> =tZ+G<br>
> -----END PGP SIGNATURE-----<br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 5<br>
> Date: Tue, 4 Sep 2012 10:55:29 +0200<br>
> From: Thorsten Rehm <<a href="mailto:thorsten.rehm@gmail.com">thorsten.rehm@gmail.com</a>><br>
> To: The Pacemaker cluster resource manager<br>
> <<a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a>><br>
> Subject: Re: [Pacemaker] Change Hostname<br>
> Message-ID:<br>
> <CABT3_pwTtF0_1W9cVVrTLfvFsfME0dWka=<br>
> <a href="mailto:74yVWeE0fybU27Gw@mail.gmail.com">74yVWeE0fybU27Gw@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset=ISO-8859-1<br>
><br>
> Hi,<br>
><br>
> ohh, thanks, but I have heartbeat in use.<br>
> "Legacy cluster stack based on heartbeat"<br>
> <a href="http://www.clusterlabs.org/wiki/File:Stack-lha.png" target="_blank">http://www.clusterlabs.org/wiki/File:Stack-lha.png</a><br>
><br>
> So, there is no corosync.conf ;)<br>
><br>
> Regards,<br>
> Thorsten<br>
><br>
> On Tue, Sep 4, 2012 at 10:38 AM, Vit Pelcak <<a href="mailto:vpelcak@suse.cz">vpelcak@suse.cz</a>> wrote:<br>
> > -----BEGIN PGP SIGNED MESSAGE-----<br>
> > Hash: SHA1<br>
> ><br>
> > Dne 4.9.2012 10:28, Thorsten Rehm napsal(a):<br>
> >> Hi everyone,<br>
> >><br>
> >> I have a cluster with three nodes (stack: heartbeat) and I need to<br>
> >> change the hostname of all systems (only the hostname, not the ip<br>
> >> address or other network configuration). I have already made<br>
> >> several attempts, but so far I have not managed that resources are<br>
> >> available without interruption, after I changed the hostname. Is<br>
> >> there a procedure that allows me to change the hostname, without<br>
> >> loss of resources? If so, how would this look like? Is there a best<br>
> >> case?<br>
> ><br>
> ><br>
> > Hm. What about modifying corosync.conf to reflect hostname change on<br>
> > all nodes, restarting corosync on all one after another (so you always<br>
> > have at least 2 nodes running corosync and resources) and then<br>
> > changing that hostname on desired machine and restarting corosync on it?<br>
> ><br>
> > In general, do not stop corosync on more than 1 node at the time and<br>
> > you should be safe.<br>
> ><br>
> >> Cheers, Thorsten<br>
> >><br>
> >> _______________________________________________ Pacemaker mailing<br>
> >> list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> >> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
> >><br>
> >> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a> Getting started:<br>
> >> <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a> Bugs:<br>
> >> <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
> ><br>
> > -----BEGIN PGP SIGNATURE-----<br>
> > Version: GnuPG v2.0.19 (GNU/Linux)<br>
> > Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/" target="_blank">http://enigmail.mozdev.org/</a><br>
> ><br>
> > iQEcBAEBAgAGBQJQRb4AAAoJEG+ytY6bjOob0AUH+gKl8OXHnGUUkXe4rFNc1qqr<br>
> > W1hkafkjDOl2k475kiXiJ9CbgvP4mJSZJ+naMvyh53BJDuWiZH4i3kl1KZVSCvQ6<br>
> > DNrZhHG90BmTLXiE6tCeVWP6K5tKamvLCRGBehiu83lW2kdH0X3uF9KqZlPnBFhy<br>
> > AeEYvCsJKfM+u7WndNDFeQVdV//FQaHAB8JZBkgSyHmlvN+bnjUzRTOE1qLyv3/b<br>
> > nPYVBOYCJgBjmENRRMoP1xWZgAAMeRCzRrpXo2ZSJ8945E/pmc1+9fPDJCqBXqvr<br>
> > CFzI7iZcyidfpKq6h1S9dlDDMdRidj9P8kfEokThtHXpy45/LhdzYrMg6LmvuIc=<br>
> > =tZ+G<br>
> > -----END PGP SIGNATURE-----<br>
> ><br>
> > _______________________________________________<br>
> > Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
> ><br>
> > Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> > Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> > Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
><br>
><br>
> --<br>
> Mit freundlichen Gruessen / Kind regards<br>
> Thorsten Rehm<br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 6<br>
> Date: Tue, 4 Sep 2012 14:59:46 +0530<br>
> From: Deepshikha Singh <<a href="mailto:deepshikhasingh@drishti-soft.com">deepshikhasingh@drishti-soft.com</a>><br>
> To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> Subject: Re: [Pacemaker] Pacemaker Digest, Vol 58, Issue 3<br>
> Message-ID:<br>
> <<br>
> <a href="mailto:CAJ9vscPK2tqGE6cjdNAWcpd8cJ-0usxd73wfeSmehG0VhZiVJw@mail.gmail.com">CAJ9vscPK2tqGE6cjdNAWcpd8cJ-0usxd73wfeSmehG0VhZiVJw@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
> Hii,<br>
><br>
> Is pacmaker also work on WAN, if yes then how????<br>
><br>
><br>
> Thank you<br>
> On Mon, Sep 3, 2012 at 3:30 PM, <<a href="mailto:pacemaker-request@oss.clusterlabs.org">pacemaker-request@oss.clusterlabs.org</a><br>
> >wrote:<br>
><br>
> > Send Pacemaker mailing list submissions to<br>
> > <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> ><br>
> > To subscribe or unsubscribe via the World Wide Web, visit<br>
> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
> > or, via email, send a message with subject or body 'help' to<br>
> > <a href="mailto:pacemaker-request@oss.clusterlabs.org">pacemaker-request@oss.clusterlabs.org</a><br>
> ><br>
> > You can reach the person managing the list at<br>
> > <a href="mailto:pacemaker-owner@oss.clusterlabs.org">pacemaker-owner@oss.clusterlabs.org</a><br>
> ><br>
> > When replying, please edit your Subject line so it is more specific<br>
> > than "Re: Contents of Pacemaker digest..."<br>
> ><br>
> ><br>
> > Today's Topics:<br>
> ><br>
> > 1. Pacemaker 1.1.6 order possible bug ? (Tom?? Vav?i?ka)<br>
> > 2. Two c72f5ca stonithd coredumps (Vladislav Bogdanov)<br>
> ><br>
> ><br>
> > ----------------------------------------------------------------------<br>
> ><br>
> > Message: 1<br>
> > Date: Mon, 03 Sep 2012 07:41:25 +0200<br>
> > From: Tom?? Vav?i?ka <<a href="mailto:vavricka@ttc.cz">vavricka@ttc.cz</a>><br>
> > To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> > Subject: [Pacemaker] Pacemaker 1.1.6 order possible bug ?<br>
> > Message-ID: <<a href="mailto:50444305.4090501@ttc.cz">50444305.4090501@ttc.cz</a>><br>
> > Content-Type: text/plain; charset=UTF-8; format=flowed<br>
> ><br>
> > Hello,<br>
> ><br>
> > Sorry If I send same question twice, but message did not appeared on<br>
> > mailing list.<br>
> ><br>
> > I have a problem with orders in pacemaker 1.1.6 and corosync 1.4.1.<br>
> ><br>
> > Order below is working for failover, but it is not working when one<br>
> > cluster node starts up (drbd stays in Slave state and ms_toponet is<br>
> > started before DRBD gets promoted).<br>
> ><br>
> > order o_start inf: ms_drbd_postgres:promote postgres:start<br>
> > ms_toponet:promote monitor_cluster:start<br>
> ><br>
> > Order below is not working for failover (it kills slave toponet app and<br>
> > start it again) but it is working correctly when cluster starts up.<br>
> ><br>
> > order o_start inf: ms_drbd_postgres:promote postgres:start<br>
> > ms_toponet:start ms_toponet:promote monitor_cluster:start<br>
> ><br>
> > I want to the pacemaker to act as in 1.0.12 version.<br>
> > * when toponet master app is killed, move postgres resource to other<br>
> > node and promote ms_toponet and ms_drbd_postgres to Master<br>
> > * when one node is starting promote DRBD to master is is UpToDate<br>
> ><br>
> > Am I doing something wrong?<br>
> ><br>
> > It looks to me pacemaker ignores some orders (pacemaker should wait for<br>
> > DRBD promotion when starting toponet app, but toponet app is started<br>
> > right after DRBD start (slave)). I tried to solve this by different<br>
> > orders with combination symmetrical=false, split orders, different<br>
> > orders for start and stop, but no success at all (seems to me like<br>
> > completely ignoring symmetrical=false directive).<br>
> ><br>
> > Pacemaker 1.1.7 is not working for me, because it has broken on-fail<br>
> > directive.<br>
> ><br>
> > crm_mon output:<br>
> ><br>
> > ============<br>
> > Last updated: Fri Aug 31 14:51:11 2012<br>
> > Last change: Fri Aug 31 14:50:27 2012 by hacluster via crmd on toponet30<br>
> > Stack: openais<br>
> > Current DC: toponet30 - partition WITHOUT quorum<br>
> > Version: 1.1.6-b988976485d15cb702c9307df55512d323831a5e<br>
> > 2 Nodes configured, 2 expected votes<br>
> > 10 Resources configured.<br>
> > ============<br>
> ><br>
> > Online: [ toponet30 toponet31 ]<br>
> ><br>
> > st_primary (stonith:external/xen0): Started toponet30<br>
> > st_secondary (stonith:external/xen0): Started toponet31<br>
> > Master/Slave Set: ms_drbd_postgres<br>
> > Masters: [ toponet30 ]<br>
> > Slaves: [ toponet31 ]<br>
> > Resource Group: postgres<br>
> > pg_fs (ocf::heartbeat:Filesystem): Started toponet30<br>
> > PGIP (ocf::heartbeat:IPaddr2): Started toponet30<br>
> > postgresql (ocf::heartbeat:pgsql): Started toponet30<br>
> > monitor_cluster (ocf::heartbeat:monitor_cluster): Started toponet30<br>
> > Master/Slave Set: ms_toponet<br>
> > Masters: [ toponet30 ]<br>
> > Slaves: [ toponet31 ]<br>
> ><br>
> > configuration:<br>
> ><br>
> > node toponet30<br>
> > node toponet31<br>
> > primitive PGIP ocf:heartbeat:IPaddr2 \<br>
> > params ip="192.168.100.3" cidr_netmask="29" \<br>
> > op monitor interval="5s"<br>
> > primitive drbd_postgres ocf:linbit:drbd \<br>
> > params drbd_resource="postgres" \<br>
> > op start interval="0" timeout="240s" \<br>
> > op stop interval="0" timeout="120s" \<br>
> > op monitor interval="5s" role="Master" timeout="10s" \<br>
> > op monitor interval="10s" role="Slave" timeout="20s"<br>
> > primitive monitor_cluster ocf:heartbeat:monitor_cluster \<br>
> > op monitor interval="30s" \<br>
> > op start interval="0" timeout="30s" \<br>
> > meta target-role="Started"<br>
> > primitive pg_fs ocf:heartbeat:Filesystem \<br>
> > params device="/dev/drbd0" directory="/var/lib/pgsql"<br>
> > fstype="ext3"<br>
> > primitive postgresql ocf:heartbeat:pgsql \<br>
> > op start interval="0" timeout="80s" \<br>
> > op stop interval="0" timeout="60s" \<br>
> > op monitor interval="10s" timeout="10s" depth="0"<br>
> > primitive st_primary stonith:external/xen0 \<br>
> > op start interval="0" timeout="60s" \<br>
> > params hostlist="toponet31:/etc/xen/vm/toponet31"<br>
> > dom0="172.16.103.54"<br>
> > primitive st_secondary stonith:external/xen0 \<br>
> > op start interval="0" timeout="60s" \<br>
> > params hostlist="toponet30:/etc/xen/vm/toponet30"<br>
> > dom0="172.16.103.54"<br>
> > primitive toponet ocf:heartbeat:toponet \<br>
> > op start interval="0" timeout="180s" \<br>
> > op stop interval="0" timeout="60s" \<br>
> > op monitor interval="10s" role="Master" timeout="20s"<br>
> > on-fail="standby" \<br>
> > op monitor interval="20s" role="Slave" timeout="40s" \<br>
> > op promote interval="0" timeout="120s" \<br>
> > op demote interval="0" timeout="120s"<br>
> > group postgres pg_fs PGIP postgresql<br>
> > ms ms_drbd_postgres drbd_postgres \<br>
> > meta master-max="1" master-node-max="1" clone-max="2"<br>
> > clone-node-max="1" notify="true" target-role="Master"<br>
> > ms ms_toponet toponet \<br>
> > meta master-max="1" master-node-max="1" clone-max="2"<br>
> > clone-node-max="1" target-role="Master"<br>
> > location loc_st_pri st_primary -inf: toponet31<br>
> > location loc_st_sec st_secondary -inf: toponet30<br>
> > location master-prefer-node1 postgres 100: toponet30<br>
> > colocation pg_on_drbd inf: monitor_cluster ms_toponet:Master postgres<br>
> > ms_drbd_postgres:Master<br>
> > order o_start inf: ms_drbd_postgres:start ms_drbd_postgres:promote<br>
> > postgres:start ms_toponet:start ms_toponet:promote monitor_cluster:start<br>
> > property $id="cib-bootstrap-options" \<br>
> > dc-version="1.1.6-b988976485d15cb702c9307df55512d323831a5e" \<br>
> > cluster-infrastructure="openais" \<br>
> > expected-quorum-votes="2" \<br>
> > no-quorum-policy="ignore" \<br>
> > stonith-enabled="true"<br>
> > rsc_defaults $id="rsc-options" \<br>
> > resource-stickiness="5000"<br>
> ><br>
> ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > Message: 2<br>
> > Date: Mon, 03 Sep 2012 10:03:28 +0300<br>
> > From: Vladislav Bogdanov <<a href="mailto:bubble@hoster-ok.com">bubble@hoster-ok.com</a>><br>
> > To: <a href="mailto:pacemaker@oss.clusterlabs.org">pacemaker@oss.clusterlabs.org</a><br>
> > Subject: [Pacemaker] Two c72f5ca stonithd coredumps<br>
> > Message-ID: <<a href="mailto:50445640.1060505@hoster-ok.com">50445640.1060505@hoster-ok.com</a>><br>
> > Content-Type: text/plain; charset=UTF-8<br>
> ><br>
> > Hi Andrew, all,<br>
> ><br>
> > as I wrote before, I caught two paths where stonithd (c72f5ca) dumps<br>
> core.<br>
> > Here are gdb backtraces for them (sorry for posting them inline, I was<br>
> > requested to do that ASAP and I hope it is not yet too late for 1.1.8 ;)<br>
> > ). Some vars are optimized out, but I hope that doesn't matter. If some<br>
> > more information is needed please just request it.<br>
> ><br>
> > First one is:<br>
> > ...<br>
> > Core was generated by `/usr/libexec/pacemaker/stonithd'.<br>
> > Program terminated with signal 11, Segmentation fault.<br>
> > ...<br>
> > (gdb) bt<br>
> > #0 0x00007f4aec6cdb51 in __strlen_sse2 () from /lib64/libc.so.6<br>
> > #1 0x00007f4aec6cd866 in strdup () from /lib64/libc.so.6<br>
> > #2 0x000000000040c6f6 in create_remote_stonith_op (client=0x1871120<br>
> > "2194f1b8-5722-49c3-bed1-c8fecc78ca02", request=0x1884840, peer=<value<br>
> > optimized out>)<br>
> > at remote.c:313<br>
> > #3 0x000000000040cf40 in initiate_remote_stonith_op (client=<value<br>
> > optimized out>, request=0x1884840, manual_ack=0) at remote.c:336<br>
> > #4 0x000000000040a2be in stonith_command (client=0x1870a80, id=<value<br>
> > optimized out>, flags=<value optimized out>, request=0x1884840,<br>
> remote=0x0)<br>
> > at commands.c:1380<br>
> > #5 0x0000000000403252 in st_ipc_dispatch (c=0x18838d0, data=<value<br>
> > optimized out>, size=329) at main.c:142<br>
> > #6 0x00007f4aebaf8d64 in ?? () from /usr/lib64/libqb.so.0<br>
> > #7 0x00007f4aebaf908e in qb_ipcs_dispatch_connection_request () from<br>
> > /usr/lib64/libqb.so.0<br>
> > #8 0x00007f4aee26fda5 in gio_read_socket (gio=<value optimized out>,<br>
> > condition=G_IO_IN, data=0x18732f0) at mainloop.c:353<br>
> > #9 0x00007f4aebf8ef0e in g_main_context_dispatch () from<br>
> > /lib64/libglib-2.0.so.0<br>
> > #10 0x00007f4aebf92938 in ?? () from /lib64/libglib-2.0.so.0<br>
> > #11 0x00007f4aebf92d55 in g_main_loop_run () from /lib64/libglib-2.0.so.0<br>
> > #12 0x0000000000403a98 in main (argc=<value optimized out>,<br>
> > argv=0x7fffa3443148) at main.c:890<br>
> > (gdb) bt full<br>
> > #0 0x00007f4aec6cdb51 in __strlen_sse2 () from /lib64/libc.so.6<br>
> > No symbol table info available.<br>
> > #1 0x00007f4aec6cd866 in strdup () from /lib64/libc.so.6<br>
> > No symbol table info available.<br>
> > #2 0x000000000040c6f6 in create_remote_stonith_op (client=0x1871120<br>
> > "2194f1b8-5722-49c3-bed1-c8fecc78ca02", request=0x1884840, peer=<value<br>
> > optimized out>)<br>
> > at remote.c:313<br>
> > nodeid = <value optimized out><br>
> > node = 0x1871790<br>
> > op = 0x187e2e0<br>
> > dev = <value optimized out><br>
> > __func__ = "create_remote_stonith_op"<br>
> > __PRETTY_FUNCTION__ = "create_remote_stonith_op"<br>
> > #3 0x000000000040cf40 in initiate_remote_stonith_op (client=<value<br>
> > optimized out>, request=0x1884840, manual_ack=0) at remote.c:336<br>
> > query = 0x0<br>
> > client_id = 0x1871120 "2194f1b8-5722-49c3-bed1-c8fecc78ca02"<br>
> > op = 0x0<br>
> > __func__ = "initiate_remote_stonith_op"<br>
> > __PRETTY_FUNCTION__ = "initiate_remote_stonith_op"<br>
> > #4 0x000000000040a2be in stonith_command (client=0x1870a80, id=<value<br>
> > optimized out>, flags=<value optimized out>, request=0x1884840,<br>
> remote=0x0)<br>
> > at commands.c:1380<br>
> > alternate_host = <value optimized out><br>
> > dev = <value optimized out><br>
> > target = 0x1883f40 "1074005258"<br>
> > call_options = 4610<br>
> > rc = -95<br>
> > is_reply = 0<br>
> > always_reply = 0<br>
> > reply = 0x0<br>
> > data = 0x0<br>
> > op = 0x187e550 "st_fence"<br>
> > client_id = 0x1874cb0 "2194f1b8-5722-49c3-bed1-c8fecc78ca02"<br>
> > __func__ = "stonith_command"<br>
> > __PRETTY_FUNCTION__ = "stonith_command"<br>
> > __FUNCTION__ = "stonith_command"<br>
> > #5 0x0000000000403252 in st_ipc_dispatch (c=0x18838d0, data=<value<br>
> > optimized out>, size=329) at main.c:142<br>
> > id = 4<br>
> > flags = 1<br>
> > request = 0x1884840<br>
> > client = 0x1870a80<br>
> > __FUNCTION__ = "st_ipc_dispatch"<br>
> > __func__ = "st_ipc_dispatch"<br>
> > __PRETTY_FUNCTION__ = "st_ipc_dispatch"<br>
> > #6 0x00007f4aebaf8d64 in ?? () from /usr/lib64/libqb.so.0<br>
> > No symbol table info available.<br>
> > #7 0x00007f4aebaf908e in qb_ipcs_dispatch_connection_request () from<br>
> > /usr/lib64/libqb.so.0<br>
> > No symbol table info available.<br>
> > #8 0x00007f4aee26fda5 in gio_read_socket (gio=<value optimized out>,<br>
> > condition=G_IO_IN, data=0x18732f0) at mainloop.c:353<br>
> > adaptor = 0x18732f0<br>
> > fd = 15<br>
> > __func__ = "gio_read_socket"<br>
> > #9 0x00007f4aebf8ef0e in g_main_context_dispatch () from<br>
> > /lib64/libglib-2.0.so.0<br>
> > No symbol table info available.<br>
> > #10 0x00007f4aebf92938 in ?? () from /lib64/libglib-2.0.so.0<br>
> > No symbol table info available.<br>
> > #11 0x00007f4aebf92d55 in g_main_loop_run () from /lib64/libglib-2.0.so.0<br>
> > No symbol table info available.<br>
> > #12 0x0000000000403a98 in main (argc=<value optimized out>,<br>
> > argv=0x7fffa3443148) at main.c:890<br>
> > flag = <value optimized out><br>
> > lpc = 0<br>
> > ---Type <return> to continue, or q <return> to quit---<br>
> > argerr = 0<br>
> > option_index = 0<br>
> > cluster = {uuid = 0x176da90 "1090782474", uname = 0x176dac0<br>
> > "vd01-b", nodeid = 1090782474, cs_dispatch = 0x404050<br>
> > <stonith_peer_ais_callback>,<br>
> > destroy = 0x404230 <stonith_peer_ais_destroy>}<br>
> > actions = {0x40e3fb "reboot", 0x40e402 "off", 0x40ea75 "list",<br>
> > 0x40e406 "monitor", 0x40e40e "status"}<br>
> > __func__ = "main"<br>
> ><br>
> ><br>
> ><br>
> > Second is (segfault in CRM_ASSERT()):<br>
> > ...<br>
> > Core was generated by `/usr/libexec/pacemaker/stonithd'.<br>
> > Program terminated with signal 11, Segmentation fault.<br>
> > #0 stonith_command (client=0x0, id=0, flags=0, request=0xb342f0,<br>
> > remote=0xb39cf0 "vd01-d") at commands.c:1258<br>
> > 1258 commands.c: No such file or directory.<br>
> > in commands.c<br>
> > ...<br>
> > (gdb) bt<br>
> > #0 stonith_command (client=0x0, id=0, flags=0, request=0xb342f0,<br>
> > remote=0xb39cf0 "vd01-d") at commands.c:1258<br>
> > #1 0x00000000004040e4 in stonith_peer_callback (kind=<value optimized<br>
> > out>, from=<value optimized out>,<br>
> > data=0x7fffa5327cc8 "<st-reply<br>
> > st_origin=\"stonith_construct_async_reply\" t=\"stonith-ng\"<br>
> > st_op=\"st_notify\" st_device_id=\"manual_ack\"<br>
> > st_remote_op=\"25917710-8972-4c40-b783-9648749396a4\"<br>
> > st_clientid=\"936ea671-61ba-4258-8e12-"...) at main.c:218<br>
> > #2 stonith_peer_ais_callback (kind=<value optimized out>, from=<value<br>
> > optimized out>,<br>
> > data=0x7fffa5327cc8 "<st-reply<br>
> > st_origin=\"stonith_construct_async_reply\" t=\"stonith-ng\"<br>
> > st_op=\"st_notify\" st_device_id=\"manual_ack\"<br>
> > st_remote_op=\"25917710-8972-4c40-b783-9648749396a4\"<br>
> > st_clientid=\"936ea671-61ba-4258-8e12-"...) at main.c:254<br>
> > #3 0x00007f92ded376ca in ais_dispatch_message (handle=<value optimized<br>
> > out>, groupName=<value optimized out>, nodeid=<value optimized out>,<br>
> > pid=<value optimized out>, msg=0x7fffa5327a78, msg_len=<value<br>
> > optimized out>) at corosync.c:551<br>
> > #4 pcmk_cpg_deliver (handle=<value optimized out>, groupName=<value<br>
> > optimized out>, nodeid=<value optimized out>, pid=<value optimized out>,<br>
> > msg=0x7fffa5327a78, msg_len=<value optimized out>) at corosync.c:619<br>
> > #5 0x00007f92de91ceaf in cpg_dispatch (handle=7749363892505018368,<br>
> > dispatch_types=<value optimized out>) at cpg.c:412<br>
> > #6 0x00007f92ded34a42 in pcmk_cpg_dispatch (user_data=<value optimized<br>
> > out>) at corosync.c:577<br>
> > #7 0x00007f92def61d27 in mainloop_gio_callback (gio=<value optimized<br>
> > out>, condition=G_IO_IN, data=0xb2d400) at mainloop.c:535<br>
> > #8 0x00007f92dcc7ff0e in g_main_context_dispatch () from<br>
> > /lib64/libglib-2.0.so.0<br>
> > #9 0x00007f92dcc83938 in ?? () from /lib64/libglib-2.0.so.0<br>
> > #10 0x00007f92dcc83d55 in g_main_loop_run () from /lib64/libglib-2.0.so.0<br>
> > #11 0x0000000000403a98 in main (argc=<value optimized out>,<br>
> > argv=0x7fffa5427de8) at main.c:890<br>
> > (gdb) bt full<br>
> > #0 stonith_command (client=0x0, id=0, flags=0, request=0xb342f0,<br>
> > remote=0xb39cf0 "vd01-d") at commands.c:1258<br>
> > call_options = 4104<br>
> > rc = -95<br>
> > is_reply = 1<br>
> > always_reply = 0<br>
> > reply = 0x0<br>
> > data = 0x0<br>
> > op = 0xb34370 "st_notify"<br>
> > client_id = 0xb3ddc0 "936ea671-61ba-4258-8e12-98542a541b23"<br>
> > __func__ = "stonith_command"<br>
> > __PRETTY_FUNCTION__ = "stonith_command"<br>
> > __FUNCTION__ = "stonith_command"<br>
> > #1 0x00000000004040e4 in stonith_peer_callback (kind=<value optimized<br>
> > out>, from=<value optimized out>,<br>
> > data=0x7fffa5327cc8 "<st-reply<br>
> > st_origin=\"stonith_construct_async_reply\" t=\"stonith-ng\"<br>
> > st_op=\"st_notify\" st_device_id=\"manual_ack\"<br>
> > st_remote_op=\"25917710-8972-4c40-b783-9648749396a4\"<br>
> > st_clientid=\"936ea671-61ba-4258-8e12-"...) at main.c:218<br>
> > remote = 0xb39cf0 "vd01-d"<br>
> > #2 stonith_peer_ais_callback (kind=<value optimized out>, from=<value<br>
> > optimized out>,<br>
> > data=0x7fffa5327cc8 "<st-reply<br>
> > st_origin=\"stonith_construct_async_reply\" t=\"stonith-ng\"<br>
> > st_op=\"st_notify\" st_device_id=\"manual_ack\"<br>
> > st_remote_op=\"25917710-8972-4c40-b783-9648749396a4\"<br>
> > st_clientid=\"936ea671-61ba-4258-8e12-"...) at main.c:254<br>
> > xml = 0xb342f0<br>
> > __func__ = "stonith_peer_ais_callback"<br>
> > #3 0x00007f92ded376ca in ais_dispatch_message (handle=<value optimized<br>
> > out>, groupName=<value optimized out>, nodeid=<value optimized out>,<br>
> > pid=<value optimized out>, msg=0x7fffa5327a78, msg_len=<value<br>
> > optimized out>) at corosync.c:551<br>
> > data = 0x7fffa5327cc8 "<st-reply<br>
> > st_origin=\"stonith_construct_async_reply\" t=\"stonith-ng\"<br>
> > st_op=\"st_notify\" st_device_id=\"manual_ack\"<br>
> > st_remote_op=\"25917710-8972-4c40-b783-9648749396a4\"<br>
> > st_clientid=\"936ea671-61ba-4258-8e12-"...<br>
> > uncompressed = 0x0<br>
> > xml = 0x0<br>
> > #4 pcmk_cpg_deliver (handle=<value optimized out>, groupName=<value<br>
> > optimized out>, nodeid=<value optimized out>, pid=<value optimized out>,<br>
> > msg=0x7fffa5327a78, msg_len=<value optimized out>) at corosync.c:619<br>
> > ais_msg = 0x7fffa5327a78<br>
> > __func__ = "pcmk_cpg_deliver"<br>
> > #5 0x00007f92de91ceaf in cpg_dispatch (handle=7749363892505018368,<br>
> > dispatch_types=<value optimized out>) at cpg.c:412<br>
> > timeout = 0<br>
> > error = <value optimized out><br>
> > cpg_inst = 0xb2cd90<br>
> > res_cpg_confchg_callback = <value optimized out><br>
> > res_cpg_deliver_callback = 0x7fffa53279c0<br>
> > res_cpg_totem_confchg_callback = <value optimized out><br>
> > cpg_inst_copy = {c = 0xb2cdf0, finalize = 0, context = 0x0,<br>
> > {model_data = {model = CPG_MODEL_V1}, model_v1_data = {model =<br>
> > CPG_MODEL_V1,<br>
> > cpg_deliver_fn = 0x7f92ded37300 <pcmk_cpg_deliver>,<br>
> > cpg_confchg_fn = 0x7f92ded33fb0 <pcmk_cpg_membership>,<br>
> > cpg_totem_confchg_fn = 0,<br>
> > flags = 0}}, iteration_list_head = {next = 0xb2cdd0, prev<br>
> > = 0xb2cdd0}}<br>
> > dispatch_data = 0x7fffa53279c0<br>
> > member_list = {{nodeid = 1090782474, pid = 4965, reason = 0},<br>
> > {nodeid = 1107559690, pid = 3544, reason = 0}, {nodeid = 1124336906, pid<br>
> > = 4487,<br>
> > reason = 3544}, {nodeid = 0, pid = 0, reason = 0} <repeats<br>
> > 125 times>}<br>
> > left_list = {{nodeid = 0, pid = 0, reason = 0} <repeats 128<br>
> times>}<br>
> > joined_list = {{nodeid = 1107559690, pid = 3544, reason = 1},<br>
> > {nodeid = 0, pid = 0, reason = 0} <repeats 127 times>}<br>
> > group_name = {length = 11, value = "stonith-ng", '\000' <repeats<br>
> > 117 times>}<br>
> > left_list_start = <value optimized out><br>
> > joined_list_start = <value optimized out><br>
> > i = <value optimized out><br>
> > ring_id = {nodeid = 0, seq = 0}<br>
> > totem_member_list = {0 <repeats 128 times>}<br>
> > errno_res = <value optimized out><br>
> > dispatch_buf =<br>
> ><br>
> ><br>
> "\005\000\000\000\000\000\000\000W\004\000\000\000\000\000\000\240\224\327)\204\177\000\000\v\000\000\000\000\000\000\000stonith-ng",<br>
> > '\000' <repeats 118 times>"\237,<br>
> ><br>
> ><br>
> \003\000\000\000\000\000\000\n\005\004C\000\000\000\000\207\021\000\000\204\177\000\000\000\000\000\000\000\000\000\000\237\003\000\000\000\000\000\000\001\000\000\000\000\000\000\000\001",<br>
> > '\000' <repeats 19 times>, "\t", '\000' <repeats 263 times>,<br>
> ><br>
> ><br>
> "\n\005\004C\207\021\000\000\000\000\000\000\t\000\000\000\006\000\000\000vd01-d",<br>
> > '\000' <repeats 250 times>, "O\001\000\000\000\000\000\000<st-reply<br>
> > st_origin=\"stonith_construct_asyn"...<br>
> > #6 0x00007f92ded34a42 in pcmk_cpg_dispatch (user_data=<value optimized<br>
> > out>) at corosync.c:577<br>
> > rc = 0<br>
> > ---Type <return> to continue, or q <return> to quit---<br>
> > __func__ = "pcmk_cpg_dispatch"<br>
> > #7 0x00007f92def61d27 in mainloop_gio_callback (gio=<value optimized<br>
> > out>, condition=G_IO_IN, data=0xb2d400) at mainloop.c:535<br>
> > keep = 1<br>
> > client = 0xb2d400<br>
> > __func__ = "mainloop_gio_callback"<br>
> > #8 0x00007f92dcc7ff0e in g_main_context_dispatch () from<br>
> > /lib64/libglib-2.0.so.0<br>
> > No symbol table info available.<br>
> > #9 0x00007f92dcc83938 in ?? () from /lib64/libglib-2.0.so.0<br>
> > No symbol table info available.<br>
> > #10 0x00007f92dcc83d55 in g_main_loop_run () from /lib64/libglib-2.0.so.0<br>
> > No symbol table info available.<br>
> > #11 0x0000000000403a98 in main (argc=<value optimized out>,<br>
> > argv=0x7fffa5427de8) at main.c:890<br>
> > flag = <value optimized out><br>
> > lpc = 0<br>
> > argerr = 0<br>
> > option_index = 0<br>
> > cluster = {uuid = 0xb2da90 "1090782474", uname = 0xb2dac0<br>
> > "vd01-b", nodeid = 1090782474, cs_dispatch = 0x404050<br>
> > <stonith_peer_ais_callback>,<br>
> > destroy = 0x404230 <stonith_peer_ais_destroy>}<br>
> > actions = {0x40e3fb "reboot", 0x40e402 "off", 0x40ea75 "list",<br>
> > 0x40e406 "monitor", 0x40e40e "status"}<br>
> > __func__ = "main"<br>
> ><br>
> > Best,<br>
> > Vladislav<br>
> ><br>
> ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > _______________________________________________<br>
> > Pacemaker mailing list<br>
> > <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> > <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
> ><br>
> ><br>
> > End of Pacemaker Digest, Vol 58, Issue 3<br>
> > ****************************************<br>
> ><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<br>
> <a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20120904/ffc03c6f/attachment.html" target="_blank">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20120904/ffc03c6f/attachment.html</a><br>
> ><br>
><br>
> ------------------------------<br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list<br>
> <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
><br>
> End of Pacemaker Digest, Vol 58, Issue 6<br>
> ****************************************<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20120904/31f9f697/attachment.html" target="_blank">http://oss.clusterlabs.org/pipermail/pacemaker/attachments/20120904/31f9f697/attachment.html</a>><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Pacemaker mailing list<br>
<a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
<br>
End of Pacemaker Digest, Vol 58, Issue 8<br>
****************************************<br>
</blockquote></div><br>