[ClusterLabs] corosync just listening on 127.0.0.1

Christine Caulfield ccaulfie at redhat.com
Mon Jul 4 03:26:16 EDT 2016


On 01/07/16 18:31, Lentes, Bernd wrote:
> Hi,
> 
> i'm currently establishing a two-node cluster and i'm playing around with it.
> I have two nodes, both have a bond-device. It is intended for DRBD, MySQL replication and the inter-cluster-communication.
> Each bond has a private IP-address (192.168.100.xxx).
> 
> This is my setup:
> 
> sunhb58820-2:/etc/corosync # ifconfig
> bond1     Link encap:Ethernet  HWaddr 28:80:23:A3:F0:23
>           inet addr:192.168.100.20  Bcast:192.168.100.255  Mask:255.255.255.0
>           inet6 addr: fe80::2a80:23ff:fea3:f023/64 Scope:Link
>           UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
>           RX packets:56053 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:53217 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>           RX bytes:4589704 (4.3 Mb)  TX bytes:4219706 (4.0 Mb)
> 
> eth0      Link encap:Ethernet  HWaddr 68:B5:99:C2:4A:37
>           inet addr:146.107.235.161  Bcast:146.107.235.255  Mask:255.255.255.0
>           inet6 addr: fe80::6ab5:99ff:fec2:4a37/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:5433800 errors:0 dropped:723509 overruns:0 frame:0
>           TX packets:26076 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:509817106 (486.1 Mb)  TX bytes:6132823 (5.8 Mb)
>           Interrupt:17
> 
> 
> sunhb58820-2:/etc/corosync # route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 0.0.0.0         146.107.235.1   0.0.0.0         UG    0      0        0 eth0
> 127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo
> 146.107.235.0   0.0.0.0         255.255.255.0   U     0      0        0 eth0
> 169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth0
> 192.168.100.0   0.0.0.0         255.255.255.0   U     0      0        0 bond1
> 
> 
> The bond-devices from the two nodes are directly connected to each other.
> Replication and DRBD is working fine already.
> 
> This is my corosync.conf:
> 
> ...
>         interface {
> 
>                 ringnumber: 0
>                 bindnetaddr: 192.168.1.0
>                 mcastport: 5406
>                 # mcastaddr: 239.255.1.1
> 
>                 member {
>                         memberaddr: 192.168.100.10
>                 }
>                 member {
>                         memberaddr: 192.168.100.20
>                 }
>         }

I'm intrigued as to where you got that syntax for corosync.conf from,
because it's nothing like what it should be :)

Try this (outside of the interface stanza).

nodelist {
    node {
        ring0_addr: 192.168.100.10
        nodeid: 10
    }

    node {
        ring0_addr: 192.168.100.20
        nodeid: 1
    }


man corosync.conf has more details

Chrissie



>         transport: udpu
> 
>         # interface {
>         #       bindnetaddr: 192.168.100.0
>         #       # mcastaddr: 225.94.1.1
>         #       broadcast: yes
>         #       mcastport: 5406
>         #       ringnumber: 0
>         # }
> ...
> 






More information about the Users mailing list