<div dir="ltr">Great, it works! Thank you.<div><br><div>It would be extremely helpful if this information will be included in a default corosync.conf as comments:</div></div><div>- regarding allowed and even preferred absense of totem.<span style="font-size:13px">interface in case of UDPu</span></div><div><span style="font-size:13px">- that quorum section must not be empty, and that the default quorum.</span><span style="font-size:13px">provider could be corosync_votequorum (but not empty).</span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">It would help to install and launch corosync instantly by novices.</span></div><div><span style="font-size:13px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 16, 2015 at 7:31 PM, Jan Friesse <span dir="ltr"><<a href="mailto:jfriesse@redhat.com" target="_blank">jfriesse@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dmitry Koterov napsal(a):<span class=""><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
such messages (for now). But, anyway, DNS names in ringX_addr seem not<br>
working, and no relevant messages are in default logs. Maybe add some<br>
validations for ringX_addr?<br>
<br>
I'm having resolvable DNS names:<br>
<br>
root@node1:/etc/corosync# ping -c1 -W100 node1 | grep from<br>
64 bytes from node1 (127.0.1.1): icmp_seq=1 ttl=64 time=0.039 ms<br>
<br>
</blockquote>
<br>
This is problem. Resolving node1 to localhost (127.0.0.1) is simply<br>
wrong. Names you want to use in corosync.conf should resolve to<br>
interface address. I believe other nodes has similar setting (so node2<br>
resolved on node2 is again 127.0.0.1)<br>
<br>
</blockquote>
<br>
Wow! What a shame! How could I miss it... So you're absolutely right,<br>
thanks: that was the cause, an entry in /etc/hosts. On some machines I<br>
removed it manually, but on others - didn't. Now I do it automatically<br>
by sed -i -r "/^.*[[:space:]]$host([[:<u></u>space:]]|\$)/d" /etc/hosts in the<br>
initialization script.<br>
<br>
I apologize for the mess.<br>
<br>
So now I have only one place in corosync.conf where I need to specify a<br>
plain IP address for UDPu: totem.interface.bindnetaddr. If I specify<br>
0.0.0.0 there, I'm having a message "Service engine 'corosync_quorum'<br>
failed to load for reason 'configuration error: nodelist or<br>
quorum.expected_votes must be configured!'" in the logs (BTW it does not<br>
say that I mistaked in bindnetaddr). Is there a way to completely untie<br>
from IP addresses?<br>
</blockquote>
<br></span>
You can just remove whole interface section completely. Corosync will find correct address from nodelist.<br>
<br>
Regards,<br>
Honza<div class="HOEnZb"><div class="h5"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Please try to fix this problem first and let's see if this will solve<br>
issue you are hitting.<br>
<br>
Regards,<br>
Honza<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
root@node1:/etc/corosync# ping -c1 -W100 node2 | grep from<br>
64 bytes from node2 (188.166.54.190): icmp_seq=1 ttl=55 time=88.3 ms<br>
<br>
root@node1:/etc/corosync# ping -c1 -W100 node3 | grep from<br>
64 bytes from node3 (128.199.116.218): icmp_seq=1 ttl=51 time=252 ms<br>
<br>
<br>
With corosync.conf below, nothing works:<br>
...<br>
nodelist {<br>
node {<br>
ring0_addr: node1<br>
}<br>
node {<br>
ring0_addr: node2<br>
}<br>
node {<br>
ring0_addr: node3<br>
}<br>
}<br>
...<br>
Jan 14 10:47:44 node1 corosync[15061]: [MAIN ] Corosync Cluster Engine<br>
('2.3.3'): started and ready to provide service.<br>
Jan 14 10:47:44 node1 corosync[15061]: [MAIN ] Corosync built-in<br>
features: dbus testagents rdma watchdog augeas pie relro bindnow<br>
Jan 14 10:47:44 node1 corosync[15062]: [TOTEM ] Initializing transport<br>
(UDP/IP Unicast).<br>
Jan 14 10:47:44 node1 corosync[15062]: [TOTEM ] Initializing<br>
transmit/receive security (NSS) crypto: aes256 hash: sha1<br>
Jan 14 10:47:44 node1 corosync[15062]: [TOTEM ] The network interface<br>
[a.b.c.d] is now up.<br>
Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded:<br>
corosync configuration map access [0]<br>
Jan 14 10:47:44 node1 corosync[15062]: [QB ] server name: cmap<br>
Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded:<br>
corosync configuration service [1]<br>
Jan 14 10:47:44 node1 corosync[15062]: [QB ] server name: cfg<br>
Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded:<br>
corosync cluster closed process group service v1.01 [2]<br>
Jan 14 10:47:44 node1 corosync[15062]: [QB ] server name: cpg<br>
Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded:<br>
corosync profile loading service [4]<br>
Jan 14 10:47:44 node1 corosync[15062]: [WD ] No Watchdog, try<br>
</blockquote>
modprobe<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<a watchdog><br>
Jan 14 10:47:44 node1 corosync[15062]: [WD ] no resources configured.<br>
Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded:<br>
corosync watchdog service [7]<br>
Jan 14 10:47:44 node1 corosync[15062]: [QUORUM] Using quorum provider<br>
corosync_votequorum<br>
Jan 14 10:47:44 node1 corosync[15062]: [QUORUM] Quorum provider:<br>
corosync_votequorum failed to initialize.<br>
Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine<br>
'corosync_quorum' failed to load for reason 'configuration error:<br>
</blockquote>
nodelist<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
or quorum.expected_votes must be configured!'<br>
Jan 14 10:47:44 node1 corosync[15062]: [MAIN ] Corosync Cluster Engine<br>
exiting with status 20 at service.c:356.<br>
<br>
<br>
But with IP addresses specified in ringX_addr, everything works:<br>
...<br>
nodelist {<br>
node {<br>
ring0_addr: 104.236.71.79<br>
}<br>
node {<br>
ring0_addr: 188.166.54.190<br>
}<br>
node {<br>
ring0_addr: 128.199.116.218<br>
}<br>
}<br>
...<br>
Jan 14 10:48:28 node1 corosync[15155]: [MAIN ] Corosync Cluster Engine<br>
('2.3.3'): started and ready to provide service.<br>
Jan 14 10:48:28 node1 corosync[15155]: [MAIN ] Corosync built-in<br>
features: dbus testagents rdma watchdog augeas pie relro bindnow<br>
Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] Initializing transport<br>
(UDP/IP Unicast).<br>
Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] Initializing<br>
transmit/receive security (NSS) crypto: aes256 hash: sha1<br>
Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] The network interface<br>
[a.b.c.d] is now up.<br>
Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded:<br>
corosync configuration map access [0]<br>
Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: cmap<br>
Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded:<br>
corosync configuration service [1]<br>
Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: cfg<br>
Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded:<br>
corosync cluster closed process group service v1.01 [2]<br>
Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: cpg<br>
Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded:<br>
corosync profile loading service [4]<br>
Jan 14 10:48:28 node1 corosync[15156]: [WD ] No Watchdog, try<br>
</blockquote>
modprobe<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<a watchdog><br>
Jan 14 10:48:28 node1 corosync[15156]: [WD ] no resources configured.<br>
Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded:<br>
corosync watchdog service [7]<br>
Jan 14 10:48:28 node1 corosync[15156]: [QUORUM] Using quorum provider<br>
corosync_votequorum<br>
Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded:<br>
corosync vote quorum service v1.0 [5]<br>
Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: votequorum<br>
Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded:<br>
corosync cluster quorum service v0.1 [3]<br>
Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: quorum<br>
Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] adding new UDPU member<br>
{a.b.c.d}<br>
Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] adding new UDPU member<br>
{e.f.g.h}<br>
Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] adding new UDPU member<br>
{i.j.k.l}<br>
Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] A new membership<br>
(m.n.o.p:80) was formed. Members joined: 1760315215<br>
Jan 14 10:48:28 node1 corosync[15156]: [QUORUM] Members[1]: 1760315215<br>
Jan 14 10:48:28 node1 corosync[15156]: [MAIN ] Completed service<br>
synchronization, ready to provide service.<br>
<br>
<br>
On Mon, Jan 5, 2015 at 6:45 PM, Jan Friesse <<a href="mailto:jfriesse@redhat.com" target="_blank">jfriesse@redhat.com</a>> wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dmitry,<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Sure, in logs I see "adding new UDPU member {IP_ADDRESS}" (so DNS names<br>
are definitely resolved), but in practice the cluster does not work,<br>
</blockquote></blockquote></blockquote>
as I<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
said above. So validations of ringX_addr in corosync.conf would be very<br>
helpful in corosync.<br>
</blockquote>
<br>
that's weird. Because as long as DNS is resolved, corosync works only<br>
with IP. This means, code path is exactly same with IP or with DNS. Do<br>
you have logs from corosync?<br>
<br>
Honza<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On Fri, Jan 2, 2015 at 2:49 PM, Jan Friesse <<a href="mailto:jfriesse@redhat.com" target="_blank">jfriesse@redhat.com</a>><br>
</blockquote></blockquote></blockquote>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Dmitry,<br>
<br>
<br>
No, I meant that if you pass a domain name in ring0_addr, there are<br>
</blockquote></blockquote></blockquote></blockquote>
no<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
errors in logs, corosync even seems to find nodes (based on its<br>
</blockquote></blockquote></blockquote></blockquote></blockquote>
logs),<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
And<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
crm_node -l shows them, but in practice nothing really works. A<br>
</blockquote></blockquote></blockquote></blockquote></blockquote>
verbose<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
error message would be very helpful in such case.<br>
<br>
</blockquote>
<br>
This sounds weird. Are you sure that DNS names really maps to correct<br>
</blockquote></blockquote></blockquote></blockquote>
IP<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
address? In logs there should be something like "adding new UDPU<br>
</blockquote></blockquote></blockquote></blockquote>
member<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
{IP_ADDRESS}".<br>
<br>
Regards,<br>
Honza<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Tuesday, December 30, 2014, Daniel Dehennin <<br>
<a href="mailto:daniel.dehennin@baby-gnu.org" target="_blank">daniel.dehennin@baby-gnu.org</a>><br>
wrote:<br>
<br>
Dmitry Koterov <<a href="mailto:dmitry.koterov@gmail.com" target="_blank">dmitry.koterov@gmail.com</a> <javascript:;>> writes:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Oh, seems I've found the solution! At least two mistakes was in my<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
corosync.conf (BTW logs did not say about any errors, so my<br>
</blockquote></blockquote></blockquote></blockquote></blockquote>
conclusion<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
is<br>
based on my experiments only).<br>
<br>
1. nodelist.node MUST contain only IP addresses. No hostnames! They<br>
<br>
</blockquote>
simply<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
do not work, "crm status" shows no nodes. And no warnings are in<br>
</blockquote></blockquote></blockquote></blockquote></blockquote></blockquote></blockquote>
logs<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
regarding this.<br>
<br>
</blockquote>
<br>
You can add name like this:<br>
<br>
nodelist {<br>
node {<br>
ring0_addr: <public-ip-address-of-the-<u></u>first-machine><br>
name: node1<br>
}<br>
node {<br>
ring0_addr: <public-ip-address-of-the-<u></u>second-machine><br>
name: node2<br>
}<br>
}<br>
<br>
I used it on Ubuntu Trusty with udpu.<br>
<br>
Regards.<br>
<br>
--<br>
Daniel Dehennin<br>
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF<br>
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF<br>
<br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>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>
</blockquote></blockquote></blockquote>
<a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>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>
</blockquote></blockquote>
<a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
</blockquote>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>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>
</blockquote></blockquote></blockquote>
<a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>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>
</blockquote></blockquote>
<a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
</blockquote>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org" target="_blank">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/<u></u>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/<u></u>doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
discuss mailing list<br>
<a href="mailto:discuss@corosync.org" target="_blank">discuss@corosync.org</a><br>
<a href="http://lists.corosync.org/mailman/listinfo/discuss" target="_blank">http://lists.corosync.org/<u></u>mailman/listinfo/discuss</a><br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</div></div></blockquote></div><br></div>