Hello,
About the nodes.
<node id="3232236029" uname="noeud1.xxxx.fr"/>
<node id="4261521600" uname="noeud2.xxxx.fr"/>
I have this in corosync.
Membership information
----------------------
Nodeid Votes Name
3232236029 1 noeud1.xxxx.fr (local)
4261521600 1 noeud2.xxxx.fr
So what is this ?
<node id="-33445696" uname="noeud2.xxxx.fr" type="normal"/>
<node id="-1062731267" uname="noeud1.xxxx.fr" type="normal"/>
Best regards.
Francis
On 08/23/2013 11:18 AM, Francis SOUYRI wrote:
Hello,
For a long time I used heartbeat/drbd for 2 nodes clusters with Fedora,
I used the internal crm of heartbeat not pacemaker.
I planned to upgrade from the fc17 to the fc18, but on fc18 heartbeat is
obsolete and I have to change to corosync/pacemaker.
For information the heartbeat fc17 package work fine on fc18 and the
cluster with a node fc17 and the other fc18 (without the firewall
activated by default !!!) work perfectly (The final configuration is to
have the both node in fc18).
But the corosync/pacemaker do not work with a fc17 node and a fc18 node.
I have these packages.
drbd-pacemaker-8.4.2-1.fc17.i686
pacemaker-libs-1.1.7-2.fc17.i686
pacemaker-1.1.7-2.fc17.i686
corosync-2.3.0-1.fc17.i686
corosynclib-2.3.0-1.fc17.i686
pacemaker-cli-1.1.7-2.fc17.i686
pacemaker-cluster-libs-1.1.7-2.fc17.i686
pacemaker-libs-1.1.9-0.1.70ad9fa.git.fc18.i686
pacemaker-1.1.9-0.1.70ad9fa.git.fc18.i686
drbd-pacemaker-8.4.2-1.fc18.i686
pacemaker-cluster-libs-1.1.9-0.1.70ad9fa.git.fc18.i686
pacemaker-cli-1.1.9-0.1.70ad9fa.git.fc18.i686
corosynclib-2.3.1-1.fc18.i686
corosync-2.3.1-1.fc18.i686
The corosync config :
totem {
version: 2
secauth: off
cluster_name: cluster
interface {
ringnumber: 0
bindnetaddr: 192.168.1.0
ttl: 1
}
transport: udpu
}
nodelist {
node {
ring0_addr: noeud1.xxxx.fr
}
node {
ring0_addr: noeud2.xxxx.fr
}
}
quorum {
provider: corosync_votequorum
}
logging {
to_syslog: yes
debug: off
}
A short time after starting pacemaker I have this.
FC18 node:
Corosync Nodes:
noeud1.xxxx.fr noeud2.xxxx.fr
Pacemaker Nodes:
noeud1.xxxx.fr noeud1.xxxx.fr noeud2.xxxx.fr noeud2.xxxx.fr
<node id="-33445696" uname="noeud2.xxxx.fr" type="normal"/>
<node id="-1062731267" uname="noeud1.xxxx.fr" type="normal"/>
<node id="3232236029" uname="noeud1.xxxx.fr"/>
<node id="4261521600" uname="noeud2.xxxx.fr"/>
Why four nodes ?!? What are the nodes 3232236029 and 4261521600 ?
FC17 node:
Corosync Nodes:
noeud1.xxxx.fr noeud2.xxxx.fr
Pacemaker Nodes:
noeud1.xxxx.fr noeud2.xxxx.fr
<node id="-33445696" uname="noeud2.xxxx.fr" type="normal"/>
<node id="-1062731267" uname="noeud1.xxxx.fr" type="normal"/>
On the FC17 I have some messages like this "error: cib_perform_op:
Discarding update with feature set '3.0.7' greater than our own '3.0.6'".
On the FC18 "warning: cib_process_replace: Replacement 0.5.4 from
noeud2.xxxx.fr not applied to 0.9.0: current epoch is greater than the
replacement"
Pacemaker 1.1.7 and 1.1.9 are not compatible ?
Best regards.
Francis
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
