Re: [Linux-HA] Option 3 : corosync + cpg + cman + mcp
Did you make sure to use different values for nodename: on both nodes?
Its an easy cutpaste error to make.
Otherwise it looks pretty sane. What do the logs say?
On Thu, Dec 16, 2010 at 1:46 PM, Alain.Moulle alain.mou...@bull.net wrote:
Hi,
I'm trying to make working the Option 3, but it does not start .
I have two nodes, the network indicated in ringnumber 0 of
corosync.conf is working fine.
Moreover, these two nodes were working fine with option 1 corosync, and
pacemaker,
so I just change the corosync.conf in adding the revords
cluster/clusternodescman ,
service/corosync_man and quorum/quorum_cman , then I execute on both nodes :
service corosync start
= ok on both nodes
service pacemaker start
= ok on both nodes
and 60s later, crm_mon displays on node chili2 :
Last updated: Thu Dec 16 13:39:37 2010
Stack: cman
Current DC: NONE
1 Nodes configured, unknown expected votes
0 Resources configured.
Online: [ chili2 ]
and on node chili3 :
Last updated: Thu Dec 16 13:40:10 2010
Current DC: NONE
0 Nodes configured, unknown expected votes
0 Resources configured.
so it seems that chili2 does not enter in the cluster, but I can't
find the reason ...
Below are some infos about configuration.
I think I miss an option somewhere but where ...?
Thanks if you have any idea.
Alain
cib.xml on chili2:
cat /var/lib/heartbeat/crm/cib.xml
cib epoch=4 num_updates=0 admin_epoch=0
validate-with=pacemaker-1.2 cib-last-written=Thu Dec 16 12:03:44
2010 crm_feature_set=3.0.2
configuration
crm_config
cluster_property_set id=cib-bootstrap-options
nvpair id=cib-bootstrap-options-dc-version name=dc-version
value=1.1.2-f059ec7ced7a86f18e5490b67ebf4a0b963bccfe/
nvpair id=cib-bootstrap-options-cluster-infrastructure
name=cluster-infrastructure value=cman/
/cluster_property_set
/crm_config
nodes
node id=chili2 uname=chili2 type=normal/
/nodes
resources/
constraints/
/configuration
status/
cib.xml on chili3 :
cib epoch=0 num_updates=0 admin_epoch=0
validate-with=pacemaker-1.2 cib-last-written=Thu Dec 16 12:02:22 2010
configuration
crm_config/
nodes/
resources/
constraints/
/configuration
status/
_corosync.conf add-ons versus the corosync.conf used with option 1 :_
cluster {
name : HA
clusternodes {
clusternode {
votes: 1
nodeid: 1
name: chili2
}
clusternode {
votes: 1
nodeid: 2
name: chili3
}
}
cman {
expected_votes: 2
cluster_id: 1
nodename: chili2
two-node: 1
max_queued: 10
}
}
service {
name: corosync_cman
ver: 0
}
quorum {
provider: quorum_cman
}
_and other records remain the same:_
aisexec {
user: root
group: root
}
totem {
version: 2
token: 5000
token_retransmits_before_loss_const: 20
join: 1000
consensus: 7500
vsftype: none
max_messages: 20
secauth: off
threads: 0
clear_node_high_bit: yes
rrp_mode : active
interface {
ringnumber: 0
bindnetaddr: 16.2.0.0
mcastaddr: 226.1.1.1
mcastport: 5405
}
}
logging {
fileline: off
to_syslog: yes
to_stderr: no
syslog_facility: daemon
debug: on
timestamp: on
}
amf {
mode: disabled
}
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Option 3 : corosync + cpg + cman + mcp
Hi Andrew, no because I have no lsb script pacemaker installed on RHEL6 with my package : pacemaker-1.1.2-2 Does that mean that to configure Option 3, there is a pacemaker release minimum that is more recent then the 1.1.2-2 ? Thanks Alain ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Option 3 : corosync + cpg + cman + mcp
On Wed, Dec 8, 2010 at 3:13 PM, Alain.Moulle alain.mou...@bull.net wrote: Hi Andrew, no because I have no lsb script pacemaker installed on RHEL6 with my package : pacemaker-1.1.2-2 Does that mean that to configure Option 3, there is a pacemaker release minimum that is more recent then the 1.1.2-2 ? Yes. GA should have had -7 or -8 Thanks Alain ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems ___ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
[Linux-HA] Option 3 : corosync + cpg + cman + mcp
Hi,
I'm trying to make a configuration with Option 3, to avoid problems with
corosync I had
with Option 0 (corosync + pacemaker plugin v0) . By the way, I tried the
option 2 but
corosync did not start, but as the future is option 4 (not yet available
if I well understand)
I choose to adopt option 3 for now.
With option 3, as it does not start , I would like to know if my
corosync.conf is correct (see below)
because I replace pacemaker by corosync_cman in the service record,
but how does it
know that it must work with pacemaker now ?
Thanks for help.
(Recall : I'm on RHEL6 with : corosync-1.2.3-21 cman-3.0.12-1
pacemaker-1.1.2-2)
Alain
/_corosync.conf :_/
aisexec {
user: root
group: root
}
cluster {
name: MYCLUSTER
clusternodes {
clusternode {
votes: 1
nodeid: 1
name: node0
}
clusternode {
votes: 1
nodeid: 2
name: node1
}
}
cman {
expected_votes: 2
cluster_id: 1
nodename: node0
two_node: 1
max_queued: 10
}
}
service {
name: corosync_cman
ver: 0
}
quorum {
provider:quorum_cman
}
totem {
version: 2
# How long before declaring a token lost (ms)
token: 5000
# How many token retransmits before forming a new configuration
token_retransmits_before_loss_const: 20
# How long to wait for join messages in the membership protocol (ms)
join: 1000
# How long to wait for consensus to be achieved before starting
a new round of membership configuration (ms)
consensus: 7500
# Turn off the virtual synchrony filter
vsftype:none
# Number of messages that may be sent by one processor on
receipt of the token
max_messages: 20
# Disable encryption
secauth:off
# How many threads to use for encryption/decryption
threads:0
# Limit generated nodeids to 31-bits (positive signed integers)
clear_node_high_bit: yes
# Optionally assign a fixed node id (integer)
# nodeid: 1
# rrp_mode : set to active but automatically reset to none if
only one network interface
#could be set alternatively to passive with 2
network interfaces
rrp_mode : active
interface {
ringnumber: 0
# The following three values need to be set based on
your environment
bindnetaddr: 18.20.0.0
mcastaddr: 230.1.1.2
mcastport: 5405
}
}
logging {
fileline: off
to_syslog: yes
to_stderr: no
syslog_facility: daemon
debug: on
timestamp: on
}
amf {
mode: disabled
}
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Re: [Linux-HA] Option 3 : corosync + cpg + cman + mcp
On Tue, Dec 7, 2010 at 9:29 AM, Alain.Moulle alain.mou...@bull.net wrote:
Hi,
I'm trying to make a configuration with Option 3, to avoid problems with
corosync I had
with Option 0 (corosync + pacemaker plugin v0) . By the way, I tried the
option 2 but
corosync did not start, but as the future is option 4 (not yet available
if I well understand)
I choose to adopt option 3 for now.
With option 3, as it does not start , I would like to know if my
corosync.conf is correct (see below)
because I replace pacemaker by corosync_cman in the service record,
but how does it
know that it must work with pacemaker now ?
Are you running /etc/init.d/pacemaker start ?
Thanks for help.
(Recall : I'm on RHEL6 with : corosync-1.2.3-21 cman-3.0.12-1
pacemaker-1.1.2-2)
Alain
/_corosync.conf :_/
aisexec {
user: root
group: root
}
cluster {
name: MYCLUSTER
clusternodes {
clusternode {
votes: 1
nodeid: 1
name: node0
}
clusternode {
votes: 1
nodeid: 2
name: node1
}
}
cman {
expected_votes: 2
cluster_id: 1
nodename: node0
two_node: 1
max_queued: 10
}
}
service {
name: corosync_cman
ver: 0
}
quorum {
provider:quorum_cman
}
totem {
version: 2
# How long before declaring a token lost (ms)
token: 5000
# How many token retransmits before forming a new configuration
token_retransmits_before_loss_const: 20
# How long to wait for join messages in the membership protocol (ms)
join: 1000
# How long to wait for consensus to be achieved before starting
a new round of membership configuration (ms)
consensus: 7500
# Turn off the virtual synchrony filter
vsftype: none
# Number of messages that may be sent by one processor on
receipt of the token
max_messages: 20
# Disable encryption
secauth: off
# How many threads to use for encryption/decryption
threads: 0
# Limit generated nodeids to 31-bits (positive signed integers)
clear_node_high_bit: yes
# Optionally assign a fixed node id (integer)
# nodeid: 1
# rrp_mode : set to active but automatically reset to none if
only one network interface
# could be set alternatively to passive with 2
network interfaces
rrp_mode : active
interface {
ringnumber: 0
# The following three values need to be set based on
your environment
bindnetaddr: 18.20.0.0
mcastaddr: 230.1.1.2
mcastport: 5405
}
}
logging {
fileline: off
to_syslog: yes
to_stderr: no
syslog_facility: daemon
debug: on
timestamp: on
}
amf {
mode: disabled
}
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
___
Linux-HA mailing list
Linux-HA@lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
