Pacemaker/Corosync/LinuxHA

Hi,
I am trying to configure pacemaker and corosync on cluster of 2 servers for failover purposes. I have installed pacemaker and corosync on both servers and I have used the corosync-keygen command to create the authkey and copied it to the passive server. I can also ping from node 1 to node 2 and have added each hostname to the respective hosts file. This setup will be used to host an Asterisk server. Pacemaker fails to start and even if I start corosync first.

Node1 = 192.168.1.113
Node1 = 192.168.1.114
VirtualIP = 192.168.1.115

The following is my /etc/corosync/corosync.conf script

compatibility: whitetank
totem {
version: 2
token: 3000
token_retransmits_before_loss_const: 10
join: 60
consensus: 3600
vsftype: none
max_messages: 20
secauth: off
threads: 0
clear_node_high_bit: yes
rrp_mode: none
interface {
ringnumber: 0
bindnetaddr: 192.168.1.0
mcastaddr: 224.0.0.1
mcastport: 5405
ttl: 1
}
}

logging {
fileline: off
to_stderr: no
to_logfile: yes
to_syslog: yes
syslog_facility: daemon
logfile: /var/log/cluster/corosync.log
debug: off
timestamp: on
logger_subsys {
subsys: AMF
debug: off
tags: enter|leave|trace1|trace2|trace3|trace4|trace6
}
}

amf {
mode: disabled
}

[root@node1 corosync]# crm_verify -L -V
Live CIB query failed: connection failed

Thank you.

couple of things to start with

I guessing theis is a typo
Node1 = 192.168.1.113
Node1 = 192.168.1.114 <<<<

and also have the firewall enabled or disabled ? make sure for testing its disabled. also make sure selinux is disabled

[quote=“ianplain”]couple of things to start with

I guessing theis is a typo
Node1 = 192.168.1.113
Node1 = 192.168.1.114 <<<<

and also have the firewall enabled or disabled ? make sure for testing its disabled. also make sure selinux is disabled[/quote]

Thank you for your reply. Yes there is a typo I meant node2 = 192.168.1.114, the firewall is disabled and selinux is also disabled. pacemaker still fails to start

lists.linux-foundation.org/pipe … 13312.html
might be of interest.