<div dir="ltr">Yes, now I have the clear experiment. Sorry, I misinformed you about "adding new UDPU member" - when I use DNS names in ringX_addr, I don't see such messages (for now). But, anyway, DNS names in ringX_addr seem not working, and no relevant messages are in default logs. Maybe add some validations for ringX_addr?<div><br></div><div>I'm having resolvable DNS names:</div><div><br></div><div><div>root@node1:/etc/corosync# ping -c1 -W100 node1 | grep from</div><div>64 bytes from node1 (127.0.1.1): icmp_seq=1 ttl=64 time=0.039 ms</div><div><br></div><div>root@node1:/etc/corosync# ping -c1 -W100 node2 | grep from</div><div>64 bytes from node2 (188.166.54.190): icmp_seq=1 ttl=55 time=88.3 ms</div><div><br></div><div>root@node1:/etc/corosync# ping -c1 -W100 node3 | grep from</div><div>64 bytes from node3 (128.199.116.218): icmp_seq=1 ttl=51 time=252 ms</div><div><br></div><div><br></div><div>With corosync.conf below, nothing works:</div><div>...</div><div>nodelist {</div><div> node {</div><div> ring0_addr: node1</div><div> }</div><div> node {</div><div> ring0_addr: node2</div><div> }</div><div> node {</div><div> ring0_addr: node3</div><div> }</div><div>}</div><div>...</div><div>Jan 14 10:47:44 node1 corosync[15061]: [MAIN ] Corosync Cluster Engine ('2.3.3'): started and ready to provide service.</div><div>Jan 14 10:47:44 node1 corosync[15061]: [MAIN ] Corosync built-in features: dbus testagents rdma watchdog augeas pie relro bindnow</div><div>Jan 14 10:47:44 node1 corosync[15062]: [TOTEM ] Initializing transport (UDP/IP Unicast).</div><div>Jan 14 10:47:44 node1 corosync[15062]: [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1</div><div>Jan 14 10:47:44 node1 corosync[15062]: [TOTEM ] The network interface [a.b.c.d] is now up.</div><div>Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded: corosync configuration map access [0]</div><div>Jan 14 10:47:44 node1 corosync[15062]: [QB ] server name: cmap</div><div>Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded: corosync configuration service [1]</div><div>Jan 14 10:47:44 node1 corosync[15062]: [QB ] server name: cfg</div><div>Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]</div><div>Jan 14 10:47:44 node1 corosync[15062]: [QB ] server name: cpg</div><div>Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded: corosync profile loading service [4]</div><div>Jan 14 10:47:44 node1 corosync[15062]: [WD ] No Watchdog, try modprobe <a watchdog></div><div>Jan 14 10:47:44 node1 corosync[15062]: [WD ] no resources configured.</div><div>Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine loaded: corosync watchdog service [7]</div><div>Jan 14 10:47:44 node1 corosync[15062]: [QUORUM] Using quorum provider corosync_votequorum</div><div>Jan 14 10:47:44 node1 corosync[15062]: [QUORUM] Quorum provider: corosync_votequorum failed to initialize.</div><div>Jan 14 10:47:44 node1 corosync[15062]: [SERV ] Service engine 'corosync_quorum' failed to load for reason 'configuration error: nodelist or quorum.expected_votes must be configured!'</div><div>Jan 14 10:47:44 node1 corosync[15062]: [MAIN ] Corosync Cluster Engine exiting with status 20 at service.c:356.</div><div><br></div><div><br></div><div>But with IP addresses specified in ringX_addr, everything works:</div><div>...</div><div>nodelist {</div><div> node {</div><div> ring0_addr: 104.236.71.79</div><div> }</div><div> node {</div><div> ring0_addr: 188.166.54.190</div><div> }</div><div> node {</div><div> ring0_addr: 128.199.116.218</div><div> }</div><div>}</div><div>...</div><div>Jan 14 10:48:28 node1 corosync[15155]: [MAIN ] Corosync Cluster Engine ('2.3.3'): started and ready to provide service.</div><div>Jan 14 10:48:28 node1 corosync[15155]: [MAIN ] Corosync built-in features: dbus testagents rdma watchdog augeas pie relro bindnow</div><div>Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] Initializing transport (UDP/IP Unicast).</div><div>Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] Initializing transmit/receive security (NSS) crypto: aes256 hash: sha1</div><div>Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] The network interface [a.b.c.d] is now up.</div><div>Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded: corosync configuration map access [0]</div><div>Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: cmap</div><div>Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded: corosync configuration service [1]</div><div>Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: cfg</div><div>Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded: corosync cluster closed process group service v1.01 [2]</div><div>Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: cpg</div><div>Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded: corosync profile loading service [4]</div><div>Jan 14 10:48:28 node1 corosync[15156]: [WD ] No Watchdog, try modprobe <a watchdog></div><div>Jan 14 10:48:28 node1 corosync[15156]: [WD ] no resources configured.</div><div>Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded: corosync watchdog service [7]</div><div>Jan 14 10:48:28 node1 corosync[15156]: [QUORUM] Using quorum provider corosync_votequorum</div><div>Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded: corosync vote quorum service v1.0 [5]</div><div>Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: votequorum</div><div>Jan 14 10:48:28 node1 corosync[15156]: [SERV ] Service engine loaded: corosync cluster quorum service v0.1 [3]</div><div>Jan 14 10:48:28 node1 corosync[15156]: [QB ] server name: quorum</div><div>Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] adding new UDPU member {a.b.c.d}</div><div>Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] adding new UDPU member {e.f.g.h}</div><div>Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] adding new UDPU member {i.j.k.l}</div><div>Jan 14 10:48:28 node1 corosync[15156]: [TOTEM ] A new membership (m.n.o.p:80) was formed. Members joined: 1760315215</div><div>Jan 14 10:48:28 node1 corosync[15156]: [QUORUM] Members[1]: 1760315215</div><div>Jan 14 10:48:28 node1 corosync[15156]: [MAIN ] Completed service synchronization, ready to provide service.</div></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 5, 2015 at 6:45 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,<br>
<span class=""><br>
<br>
> 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, as I<br>
> said above. So validations of ringX_addr in corosync.conf would be very<br>
> helpful in corosync.<br>
<br>
</span>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>
<div class="HOEnZb"><div class="h5"><br>
<br>
><br>
> On Fri, Jan 2, 2015 at 2:49 PM, Jan Friesse <<a href="mailto:jfriesse@redhat.com">jfriesse@redhat.com</a>> wrote:<br>
><br>
>> Dmitry,<br>
>><br>
>><br>
>> No, I meant that if you pass a domain name in ring0_addr, there are no<br>
>>> errors in logs, corosync even seems to find nodes (based on its logs), And<br>
>>> crm_node -l shows them, but in practice nothing really works. A verbose<br>
>>> error message would be very helpful in such case.<br>
>>><br>
>><br>
>> This sounds weird. Are you sure that DNS names really maps to correct IP<br>
>> address? In logs there should be something like "adding new UDPU member<br>
>> {IP_ADDRESS}".<br>
>><br>
>> Regards,<br>
>> Honza<br>
>><br>
>><br>
>>> On Tuesday, December 30, 2014, Daniel Dehennin <<br>
>>> <a href="mailto:daniel.dehennin@baby-gnu.org">daniel.dehennin@baby-gnu.org</a>><br>
>>> wrote:<br>
>>><br>
>>> Dmitry Koterov <<a href="mailto:dmitry.koterov@gmail.com">dmitry.koterov@gmail.com</a> <javascript:;>> writes:<br>
>>>><br>
>>>> Oh, seems I've found the solution! At least two mistakes was in my<br>
>>>>> corosync.conf (BTW logs did not say about any errors, so my conclusion<br>
>>>>> is<br>
>>>>> based on my experiments only).<br>
>>>>><br>
>>>>> 1. nodelist.node MUST contain only IP addresses. No hostnames! They<br>
>>>>><br>
>>>> simply<br>
>>>><br>
>>>>> do not work, "crm status" shows no nodes. And no warnings are in logs<br>
>>>>> regarding this.<br>
>>>>><br>
>>>><br>
>>>> You can add name like this:<br>
>>>><br>
>>>> nodelist {<br>
>>>> node {<br>
>>>> ring0_addr: <public-ip-address-of-the-first-machine><br>
>>>> name: node1<br>
>>>> }<br>
>>>> node {<br>
>>>> ring0_addr: <public-ip-address-of-the-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>
>>><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>
>> 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>
> 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>
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>
</div></div></blockquote></div><br></div>