Corosync pacemaker crm status show DC : none and offline

corosyncpacemaker

i'm new to corosync and pacemaker and try to build cluster by using vm node1 & node2. here is the /etc/corosync/corosync.conf

# Please read the corosync.conf.5 manual page
compatibility: whitetank

totem {
    version: 2
    secauth: off
    interface {
        member {
            memberaddr: 192.168.1.101
        }
        member {
            memberaddr: 192.168.1.102
        }
        ringnumber: 0
        bindnetaddr: 192.168.1.100
        mcastport: 5405
        ttl: 1
    }
    transport: udpu
}

logging {
    fileline: off
    to_logfile: yes
    to_syslog: yes
    #logfile: /var/log/cluster/corosync.log
    debug: off
    timestamp: on
    logger_subsys {
        subsys: AMF
        debug: off
    }
}

the crm status:

[root@node1 ~]# crm status
Last updated: Wed Oct 29 04:41:37 2014
Last change: Wed Oct 29 01:29:10 2014 via crmd on node1
Stack: classic openais (with plugin)
Current DC: NONE
1 Nodes configured, 2 expected votes
0 Resources configured


Node node1: UNCLEAN (offline)

i follow this tutorial, http://www.tokiwinter.com/clustering-with-drbd-corosync-and-pacemaker/, but my status seems my setting is not successful

anyone can help?

————-update—————-

corosync-1.4.1-17.e16_5.1.86_64
pacemaker-1.1.10-14.el6_5.3.x86_64

[root@node1 ~]# cat /etc/hosts
127.0.0.1    node1 localhost
::1        localhost6.localdomain6 localhost6
192.168.1.101    node1.mycluster.org node1
192.168.1.102   node2.mycluster.org node2
[root@node1 ~]# cat /etc/sysconfig/network
NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=node1

Best Answer

In my configuration I use bindnetaddr with the ip address for each host.

For example:

node1: bindnetaddr: 192.168.1.101

node2: bindnetaddr: 192.168.1.102

Edit:

bindnetaddr
his is normally the network address of the interface to bind to. This ensures that you can use identical instances of this configuration file across all your cluster nodes, without having to modify this option.

However, if you have multiple physical network interfaces configured for the same subnet, then the network address alone is not sufficient to identify the interface Corosync should bind to. In that case, configure the host address of the interface.

Related Topic