<div dir="ltr">thank you <span style="font-size:12.8px">Digimer ,i will try it on centos 7.</span><div><span style="font-size:12.8px">thanks again for the help.</span></div><div><span style="font-size:12.8px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Apr 13, 2016 at 1:00 PM, <span dir="ltr"><<a href="mailto:users-request@clusterlabs.org" target="_blank">users-request@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 Users mailing list submissions to<br>
<a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:users-request@clusterlabs.org">users-request@clusterlabs.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:users-owner@clusterlabs.org">users-owner@clusterlabs.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of Users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: Totem is unable to form a cluster because of an operating<br>
system or network fault (Digimer)<br>
2. HA meetup at OpenStack Summit (Ken Gaillot)<br>
3. Re: HA meetup at OpenStack Summit (Digimer)<br>
4. Re: Totem is unable to form a cluster because of an operating<br>
system or network fault (Jan Friesse)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Tue, 12 Apr 2016 11:46:21 -0400<br>
From: Digimer <<a href="mailto:lists@alteeve.ca">lists@alteeve.ca</a>><br>
To: Cluster Labs - All topics related to open-source clustering<br>
welcomed <<a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a>><br>
Subject: Re: [ClusterLabs] Totem is unable to form a cluster because<br>
of an operating system or network fault<br>
Message-ID: <<a href="mailto:570D184D.6000904@alteeve.ca">570D184D.6000904@alteeve.ca</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
On 12/04/16 07:44 AM, dinor geler wrote:<br>
> Hi ,<br>
> Am trying to configure my sql on ubuntu according to this article :<br>
> <a href="https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-linux-classic-mysql-cluster/" rel="noreferrer" target="_blank">https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-linux-classic-mysql-cluster/</a><br>
><br>
> two node cluster<br>
><br>
><br>
> looking on corosync log :<br>
><br>
><br>
> Apr 12 11:01:09 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:11 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:13 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:16 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:18 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:20 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:22 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:24 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:27 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:29 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:31 corosync [TOTEM ] Totem is unable to form a cluster<br>
> because of an operating system or network fault. The most common cause<br>
> of this message is that the local firewall is configured improperly.<br>
><br>
><br>
><br>
> totem {<br>
> version: 2<br>
> crypto_cipher: none<br>
> crypto_hash: none<br>
> interface {<br>
> ringnumber: 0<br>
> bindnetaddr: 10.1.0.0<br>
> mcastport: 5405<br>
> ttl: 1<br>
> }<br>
> transport: udpu<br>
> }<br>
> logging {<br>
> fileline: off<br>
> to_logfile: yes<br>
> to_syslog: yes<br>
> logfile: /var/log/corosync/corosync.log<br>
> debug: off<br>
> timestamp: on<br>
> logger_subsys {<br>
> subsys: QUORUM<br>
> debug: off<br>
> }<br>
> }<br>
> nodelist {<br>
> node {<br>
> ring0_addr: 10.1.0.6<br>
> nodeid: 1<br>
> }<br>
> node {<br>
> ring0_addr: 10.1.0.7<br>
> nodeid: 2<br>
> }<br>
> }<br>
> quorum {<br>
> provider: corosync_votequorum<br>
> }<br>
><br>
><br>
> If I initiate a tcpdump on node 2 and start either a netcat or nmap I<br>
> see packet arrives to destination host for port 5405 UDP traffic<br>
><br>
><br>
><br>
> I do see Corosync listening on the IP/PORT<br>
><br>
><br>
><br>
><br>
><br>
> root@node-2:/home/dinor# netstat -an | grep -i 5405<br>
><br>
> udp 0 0 <a href="http://10.1.0.7:5405" rel="noreferrer" target="_blank">10.1.0.7:5405</a> <<a href="http://10.1.0.7:5405" rel="noreferrer" target="_blank">http://10.1.0.7:5405</a>><br>
> 0.0.0.0:*<br>
><br>
><br>
><br>
><br>
><br>
> root@node-1:/home/dinor# netstat -an | grep -i 5405<br>
><br>
> udp 0 0 <a href="http://10.1.0.6:5405" rel="noreferrer" target="_blank">10.1.0.6:5405</a> <<a href="http://10.1.0.6:5405" rel="noreferrer" target="_blank">http://10.1.0.6:5405</a>><br>
> 0.0.0.0:*<br>
><br>
><br>
><br>
><br>
><br>
> On node 1 I start a netcat to port 5405 via udp<br>
><br>
><br>
><br>
> netcat -D -4 -u 10.1.0.7 5405<br>
><br>
><br>
><br>
> In here you type some text and hit enter<br>
><br>
><br>
><br>
> On node 1 tcpdump we see data sent to IP 10.1.0.7<br>
><br>
><br>
><br>
> root@node-1:/var/log/corosync# tcpdump -n udp port 5405<br>
><br>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
><br>
> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes<br>
><br>
> 10:08:24.484533 IP 10.1.0.6.44299 > 10.1.0.7.5405: UDP, length 26<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On node 2 tcpdump I see the data arrive<br>
><br>
><br>
><br>
> root@node-2:/var/log/corosync# tcpdump -n udp port 5405<br>
><br>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
><br>
> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes<br>
><br>
> 10:08:24.484892 IP 10.1.0.6.44299 > 10.1.0.7.5405: UDP, length 26<br>
><br>
><br>
><br>
><br>
><br>
> Tested also sending UDP packets from node 2 ? all ok.<br>
><br>
><br>
><br>
> So connectivity seems to be ok.<br>
><br>
><br>
><br>
> Port scanner also shows the port as Open<br>
><br>
><br>
><br>
><br>
><br>
> root@node-1:/home/dinor# nmap -sUV 10.1.0.7 -p 5402-5405<br>
><br>
><br>
><br>
> Starting Nmap 5.21 ( <a href="http://nmap.org" rel="noreferrer" target="_blank">http://nmap.org</a> ) at 2016-04-12 10:31 UTC<br>
><br>
> Nmap scan report for node-2 (10.1.0.7)<br>
><br>
> Host is up (0.00060s latency).<br>
><br>
> PORT STATE SERVICE VERSION<br>
><br>
> 5402/udp closed unknown<br>
><br>
> 5403/udp closed unknown<br>
><br>
> 5404/udp closed unknown<br>
><br>
> *5405/udp open|filtered unknown*<br>
><br>
> MAC Address: 12:34:56:78:9A:BC (Unknown)<br>
><br>
><br>
><br>
> Service detection performed. Please report any incorrect results at<br>
> <a href="http://nmap.org/submit/" rel="noreferrer" target="_blank">http://nmap.org/submit/</a> .<br>
><br>
> Nmap done: 1 IP address (1 host up) scanned in 79.07 seconds<br>
><br>
><br>
><br>
><br>
><br>
> There is no FW and no selinux enabled<br>
><br>
><br>
> help appreciated.<br>
<br>
They disable stonith, so I question the entire tutorial... Suggesting<br>
using ssh for fencing shows a real flawed understanding.<br>
<br>
If you install CentOS 7 instead of Ubuntu, you will be able to follow<br>
the Cluster from Scratch tutorial on Clusterlabs.org website. It is<br>
written and maintained by the Pacemaker author and includes 'pcs' that<br>
will configure the base cluster for you.<br>
<br>
--<br>
Digimer<br>
Papers and Projects: <a href="https://alteeve.ca/w/" rel="noreferrer" target="_blank">https://alteeve.ca/w/</a><br>
What if the cure for cancer is trapped in the mind of a person without<br>
access to education?<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Tue, 12 Apr 2016 18:09:35 -0500<br>
From: Ken Gaillot <<a href="mailto:kgaillot@redhat.com">kgaillot@redhat.com</a>><br>
To: Cluster Labs - All topics related to open-source clustering<br>
welcomed <<a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a>><br>
Subject: [ClusterLabs] HA meetup at OpenStack Summit<br>
Message-ID: <<a href="mailto:570D802F.8030503@redhat.com">570D802F.8030503@redhat.com</a>><br>
Content-Type: text/plain; charset=utf-8<br>
<br>
Hi everybody,<br>
<br>
The upcoming OpenStack Summit is April 25-29 in Austin, Texas (US). Some<br>
regular ClusterLabs contributors are going, so I was wondering if anyone<br>
would like to do an informal meetup sometime during the summit.<br>
<br>
It looks like the best time would be that Wednesday, either lunch (at<br>
the venue) or dinner (offsite). It might also be possible to reserve a<br>
small (10-person) meeting room, or just meet informally in the expo hall.<br>
<br>
Anyone interested? Preferences/conflicts?<br>
--<br>
Ken Gaillot <<a href="mailto:kgaillot@redhat.com">kgaillot@redhat.com</a>><br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 12 Apr 2016 19:39:25 -0400<br>
From: Digimer <<a href="mailto:lists@alteeve.ca">lists@alteeve.ca</a>><br>
To: <a href="mailto:kgaillot@redhat.com">kgaillot@redhat.com</a>, Cluster Labs - All topics related to<br>
open-source clustering welcomed <<a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a>><br>
Subject: Re: [ClusterLabs] HA meetup at OpenStack Summit<br>
Message-ID: <<a href="mailto:570D872D.50009@alteeve.ca">570D872D.50009@alteeve.ca</a>><br>
Content-Type: text/plain; charset=windows-1252<br>
<br>
On 12/04/16 07:09 PM, Ken Gaillot wrote:<br>
> Hi everybody,<br>
><br>
> The upcoming OpenStack Summit is April 25-29 in Austin, Texas (US). Some<br>
> regular ClusterLabs contributors are going, so I was wondering if anyone<br>
> would like to do an informal meetup sometime during the summit.<br>
><br>
> It looks like the best time would be that Wednesday, either lunch (at<br>
> the venue) or dinner (offsite). It might also be possible to reserve a<br>
> small (10-person) meeting room, or just meet informally in the expo hall.<br>
><br>
> Anyone interested? Preferences/conflicts?<br>
<br>
Informal meet-up, or to try and get work done?<br>
<br>
--<br>
Digimer<br>
Papers and Projects: <a href="https://alteeve.ca/w/" rel="noreferrer" target="_blank">https://alteeve.ca/w/</a><br>
What if the cure for cancer is trapped in the mind of a person without<br>
access to education?<br>
<br>
<br>
<br>
------------------------------<br>
<br>
Message: 4<br>
Date: Wed, 13 Apr 2016 09:19:37 +0200<br>
From: Jan Friesse <<a href="mailto:jfriesse@redhat.com">jfriesse@redhat.com</a>><br>
To: Cluster Labs - All topics related to open-source clustering<br>
welcomed <<a href="mailto:users@clusterlabs.org">users@clusterlabs.org</a>><br>
Subject: Re: [ClusterLabs] Totem is unable to form a cluster because<br>
of an operating system or network fault<br>
Message-ID: <<a href="mailto:570DF309.4050900@redhat.com">570DF309.4050900@redhat.com</a>><br>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed<br>
<br>
> Hi ,<br>
> Am trying to configure my sql on ubuntu according to this article :<br>
> <a href="https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-linux-classic-mysql-cluster/" rel="noreferrer" target="_blank">https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-linux-classic-mysql-cluster/</a><br>
><br>
> two node cluster<br>
><br>
><br>
> looking on corosync log :<br>
><br>
><br>
> Apr 12 11:01:09 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:11 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:13 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:16 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:18 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:20 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:22 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:24 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:27 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:29 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
> Apr 12 11:01:31 corosync [TOTEM ] Totem is unable to form a cluster because<br>
> of an operating system or network fault. The most common cause of this<br>
> message is that the local firewall is configured improperly.<br>
><br>
><br>
><br>
> totem {<br>
> version: 2<br>
> crypto_cipher: none<br>
> crypto_hash: none<br>
> interface {<br>
> ringnumber: 0<br>
> bindnetaddr: 10.1.0.0<br>
> mcastport: 5405<br>
> ttl: 1<br>
> }<br>
> transport: udpu<br>
> }<br>
> logging {<br>
> fileline: off<br>
> to_logfile: yes<br>
> to_syslog: yes<br>
> logfile: /var/log/corosync/corosync.log<br>
> debug: off<br>
> timestamp: on<br>
> logger_subsys {<br>
> subsys: QUORUM<br>
> debug: off<br>
> }<br>
> }<br>
> nodelist {<br>
> node {<br>
> ring0_addr: 10.1.0.6<br>
> nodeid: 1<br>
> }<br>
> node {<br>
> ring0_addr: 10.1.0.7<br>
> nodeid: 2<br>
> }<br>
> }<br>
> quorum {<br>
> provider: corosync_votequorum<br>
> }<br>
><br>
><br>
> If I initiate a tcpdump on node 2 and start either a netcat or nmap I see<br>
> packet arrives to destination host for port 5405 UDP traffic<br>
><br>
><br>
><br>
> I do see Corosync listening on the IP/PORT<br>
><br>
><br>
><br>
><br>
><br>
> root@node-2:/home/dinor# netstat -an | grep -i 5405<br>
><br>
> udp 0 0 <a href="http://10.1.0.7:5405" rel="noreferrer" target="_blank">10.1.0.7:5405</a> 0.0.0.0:*<br>
><br>
><br>
><br>
><br>
><br>
><br>
> root@node-1:/home/dinor# netstat -an | grep -i 5405<br>
><br>
> udp 0 0 <a href="http://10.1.0.6:5405" rel="noreferrer" target="_blank">10.1.0.6:5405</a> 0.0.0.0:*<br>
><br>
><br>
><br>
><br>
><br>
> On node 1 I start a netcat to port 5405 via udp<br>
><br>
><br>
><br>
> netcat -D -4 -u 10.1.0.7 5405<br>
><br>
><br>
><br>
> In here you type some text and hit enter<br>
><br>
><br>
><br>
> On node 1 tcpdump we see data sent to IP 10.1.0.7<br>
><br>
><br>
><br>
> root@node-1:/var/log/corosync# tcpdump -n udp port 5405<br>
><br>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
><br>
> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes<br>
><br>
> 10:08:24.484533 IP 10.1.0.6.44299 > 10.1.0.7.5405: UDP, length 26<br>
><br>
><br>
><br>
><br>
><br>
><br>
><br>
> On node 2 tcpdump I see the data arrive<br>
><br>
><br>
><br>
> root@node-2:/var/log/corosync# tcpdump -n udp port 5405<br>
><br>
> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode<br>
><br>
> listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes<br>
><br>
> 10:08:24.484892 IP 10.1.0.6.44299 > 10.1.0.7.5405: UDP, length 26<br>
><br>
><br>
><br>
><br>
><br>
> Tested also sending UDP packets from node 2 ? all ok.<br>
><br>
><br>
><br>
> So connectivity seems to be ok.<br>
><br>
><br>
><br>
> Port scanner also shows the port as Open<br>
><br>
><br>
><br>
><br>
><br>
> root@node-1:/home/dinor# nmap -sUV 10.1.0.7 -p 5402-5405<br>
><br>
><br>
><br>
> Starting Nmap 5.21 ( <a href="http://nmap.org" rel="noreferrer" target="_blank">http://nmap.org</a> ) at 2016-04-12 10:31 UTC<br>
><br>
> Nmap scan report for node-2 (10.1.0.7)<br>
><br>
> Host is up (0.00060s latency).<br>
><br>
> PORT STATE SERVICE VERSION<br>
><br>
> 5402/udp closed unknown<br>
><br>
> 5403/udp closed unknown<br>
><br>
> 5404/udp closed unknown<br>
><br>
> *5405/udp open|filtered unknown*<br>
><br>
> MAC Address: 12:34:56:78:9A:BC (Unknown)<br>
><br>
><br>
><br>
> Service detection performed. Please report any incorrect results at<br>
> <a href="http://nmap.org/submit/" rel="noreferrer" target="_blank">http://nmap.org/submit/</a> .<br>
><br>
> Nmap done: 1 IP address (1 host up) scanned in 79.07 seconds<br>
><br>
><br>
><br>
><br>
><br>
> There is no FW and no selinux enabled<br>
><br>
><br>
> help appreciated.<br>
<br>
You can try to adjust mtu (token.netmtu) to some smaller value. If it<br>
doesn't help, please paste more lines from corosync.log (20 lines saying<br>
about "totem unable ..." really doesn't help) + your network<br>
configuration (output of ip/ifconfig).<br>
<br>
Regards,<br>
Honza<br>
<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
> <a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" rel="noreferrer" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" rel="noreferrer" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" rel="noreferrer" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
<br>
<br>
<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
Users mailing list<br>
<a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
<a href="http://clusterlabs.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
<br>
<br>
End of Users Digest, Vol 15, Issue 18<br>
*************************************<br>
</blockquote></div><br></div>