help appreciated am totally stuck.
On Tue, Apr 12, 2016 at 4:22 PM, <[email protected]> wrote: > Send Users mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://clusterlabs.org/mailman/listinfo/users > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Users digest..." > > > Today's Topics: > > 1. Totem is unable to form a cluster because of an operating > system or network fault (dinor geler) > 2. Re: getting "Totem is unable to form a cluster" error > (Lars Ellenberg) > 3. Re: getting "Totem is unable to form a cluster" error > (Jan Pokorn?) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 12 Apr 2016 14:44:40 +0300 > From: dinor geler <[email protected]> > To: [email protected] > Subject: [ClusterLabs] Totem is unable to form a cluster because of an > operating system or network fault > Message-ID: > < > caeu-psknxqbbyzbwqrppfljpzfj9wxzepjwkz0metdfoave...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi , > Am trying to configure my sql on ubuntu according to this article : > > https://azure.microsoft.com/en-in/documentation/articles/virtual-machines-linux-classic-mysql-cluster/ > > two node cluster > > > looking on corosync log : > > > Apr 12 11:01:09 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:11 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:13 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:16 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:18 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:20 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:22 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:24 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:27 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:29 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > Apr 12 11:01:31 corosync [TOTEM ] Totem is unable to form a cluster because > of an operating system or network fault. The most common cause of this > message is that the local firewall is configured improperly. > > > > totem { > version: 2 > crypto_cipher: none > crypto_hash: none > interface { > ringnumber: 0 > bindnetaddr: 10.1.0.0 > mcastport: 5405 > ttl: 1 > } > transport: udpu > } > logging { > fileline: off > to_logfile: yes > to_syslog: yes > logfile: /var/log/corosync/corosync.log > debug: off > timestamp: on > logger_subsys { > subsys: QUORUM > debug: off > } > } > nodelist { > node { > ring0_addr: 10.1.0.6 > nodeid: 1 > } > node { > ring0_addr: 10.1.0.7 > nodeid: 2 > } > } > quorum { > provider: corosync_votequorum > } > > > If I initiate a tcpdump on node 2 and start either a netcat or nmap I see > packet arrives to destination host for port 5405 UDP traffic > > > > I do see Corosync listening on the IP/PORT > > > > > > root@node-2:/home/dinor# netstat -an | grep -i 5405 > > udp 0 0 10.1.0.7:5405 0.0.0.0:* > > > > > > > root@node-1:/home/dinor# netstat -an | grep -i 5405 > > udp 0 0 10.1.0.6:5405 0.0.0.0:* > > > > > > On node 1 I start a netcat to port 5405 via udp > > > > netcat -D -4 -u 10.1.0.7 5405 > > > > In here you type some text and hit enter > > > > On node 1 tcpdump we see data sent to IP 10.1.0.7 > > > > root@node-1:/var/log/corosync# tcpdump -n udp port 5405 > > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > > listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes > > 10:08:24.484533 IP 10.1.0.6.44299 > 10.1.0.7.5405: UDP, length 26 > > > > > > > > On node 2 tcpdump I see the data arrive > > > > root@node-2:/var/log/corosync# tcpdump -n udp port 5405 > > tcpdump: verbose output suppressed, use -v or -vv for full protocol decode > > listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes > > 10:08:24.484892 IP 10.1.0.6.44299 > 10.1.0.7.5405: UDP, length 26 > > > > > > Tested also sending UDP packets from node 2 ? all ok. > > > > So connectivity seems to be ok. > > > > Port scanner also shows the port as Open > > > > > > root@node-1:/home/dinor# nmap -sUV 10.1.0.7 -p 5402-5405 > > > > Starting Nmap 5.21 ( http://nmap.org ) at 2016-04-12 10:31 UTC > > Nmap scan report for node-2 (10.1.0.7) > > Host is up (0.00060s latency). > > PORT STATE SERVICE VERSION > > 5402/udp closed unknown > > 5403/udp closed unknown > > 5404/udp closed unknown > > *5405/udp open|filtered unknown* > > MAC Address: 12:34:56:78:9A:BC (Unknown) > > > > Service detection performed. Please report any incorrect results at > http://nmap.org/submit/ . > > Nmap done: 1 IP address (1 host up) scanned in 79.07 seconds > > > > > > There is no FW and no selinux enabled > > > help appreciated. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://clusterlabs.org/pipermail/users/attachments/20160412/184f5189/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Tue, 12 Apr 2016 15:03:35 +0200 > From: Lars Ellenberg <[email protected]> > To: [email protected] > Subject: Re: [ClusterLabs] getting "Totem is unable to form a cluster" > error > Message-ID: <[email protected]> > Content-Type: text/plain; charset=iso-8859-1 > > On Mon, Apr 11, 2016 at 08:23:03AM +0200, Jan Friesse wrote: > > ... > >>> bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state > UP > >>> link/ether 74:e6:e2:73:e5:61 brd ff:ff:ff:ff:ff:ff > >>> inet 10.150.20.91/24 brd 10.150.20.55 scope global bond0 > >>> inet 192.168.150.12/22 brd 192.168.151.255 scope global > bond0:cluster > >>> inet6 fe80::76e6:e2ff:fe73:e561/64 scope link > >>> valid_lft forever preferred_lft forever > >> > >> This is ifconfig output? I'm just wondering how you were able to set > >> two ipv4 addresses (in this format, I would expect another interface > >> like bond0:1 or nothing at all)? > ... > > No, it is "ip addr show" output. > > > RHEL 6: > > > > # tunctl -p > > Set 'tap0' persistent and owned by uid 0 > > > > # ip addr add 192.168.7.1/24 dev tap0 > > # ip addr add 192.168.8.1/24 dev tap0 > > # ifconfig tap0 > > tap0 Link encap:Ethernet HWaddr 22:95:B1:85:67:3F > > inet addr:192.168.7.1 Bcast:0.0.0.0 Mask:255.255.255.0 > > BROADCAST MULTICAST MTU:1500 Metric:1 > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:500 > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > # ip addr add 192.168.7.1/24 dev tap0 > # ip addr add 192.168.8.1/24 dev tap0 label tap0:jan > # ip addr show dev tap0 > > And as long as you actually use those "label"s, > you then can even see these with "ifconfig tap0:jan". > > > -- > : Lars Ellenberg > : LINBIT | Keeping the Digital World Running > : DRBD -- Heartbeat -- Corosync -- Pacemaker > : R&D, Integration, Ops, Consulting, Support > > DRBD? and LINBIT? are registered trademarks of LINBIT > > > > ------------------------------ > > Message: 3 > Date: Tue, 12 Apr 2016 15:17:51 +0200 > From: Jan Pokorn? <[email protected]> > To: Cluster Labs - All topics related to open-source clustering > welcomed <[email protected]> > Subject: Re: [ClusterLabs] getting "Totem is unable to form a cluster" > error > Message-ID: <[email protected]> > Content-Type: text/plain; charset="us-ascii" > > On 12/04/16 15:03 +0200, Lars Ellenberg wrote: > > On Mon, Apr 11, 2016 at 08:23:03AM +0200, Jan Friesse wrote: > > > > ... > >>>> bond0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state > UP > >>>> link/ether 74:e6:e2:73:e5:61 brd ff:ff:ff:ff:ff:ff > >>>> inet 10.150.20.91/24 brd 10.150.20.55 scope global bond0 > >>>> inet 192.168.150.12/22 brd 192.168.151.255 scope global > bond0:cluster > >>>> inet6 fe80::76e6:e2ff:fe73:e561/64 scope link > >>>> valid_lft forever preferred_lft forever > >>> > >>> This is ifconfig output? I'm just wondering how you were able to set > >>> two ipv4 addresses (in this format, I would expect another interface > >>> like bond0:1 or nothing at all)? > > ... > > > > No, it is "ip addr show" output. > > > >> RHEL 6: > >> > >> # tunctl -p > >> Set 'tap0' persistent and owned by uid 0 > >> > >> # ip addr add 192.168.7.1/24 dev tap0 > >> # ip addr add 192.168.8.1/24 dev tap0 > >> # ifconfig tap0 > >> tap0 Link encap:Ethernet HWaddr 22:95:B1:85:67:3F > >> inet addr:192.168.7.1 Bcast:0.0.0.0 Mask:255.255.255.0 > >> BROADCAST MULTICAST MTU:1500 Metric:1 > >> RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > >> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > >> collisions:0 txqueuelen:500 > >> RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > > # ip addr add 192.168.7.1/24 dev tap0 > > # ip addr add 192.168.8.1/24 dev tap0 label tap0:jan > > # ip addr show dev tap0 > > > > And as long as you actually use those "label"s, > > you then can even see these with "ifconfig tap0:jan". > > Further reading: http://inai.de/2008/02/19 > > -- > Jan (Poki) > -------------- next part -------------- > A non-text attachment was scrubbed... > Name: not available > Type: application/pgp-signature > Size: 819 bytes > Desc: not available > URL: < > http://clusterlabs.org/pipermail/users/attachments/20160412/eca021cb/attachment.sig > > > > ------------------------------ > > _______________________________________________ > Users mailing list > [email protected] > http://clusterlabs.org/mailman/listinfo/users > > > End of Users Digest, Vol 15, Issue 16 > ************************************* >
_______________________________________________ Users mailing list: [email protected] http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
