On 26/08/2013, at 7:48 PM, Francis SOUYRI <francis.sou...@apec.fr> wrote:
> Hello Andrew, > > About your document > "http://blog.clusterlabs.org/blog/2013/mixing-pacemaker-versions/"; > > > 1. stop the cluster on both nodes > 2. on both nodes, run: > > CIB_file=/path/to/cib.xml cibadmin -M -X '<cib crm_feature_set="3.0.7"/>' > > 3. start node1 and wait until it is elected as the DC > 4. start node2 > > How can I execute the command "cibadmin -M -X '<cib > crm_feature_set="3.0.6"/>'" when the cluster is stopped ? cibadmin is clever enough to talk directly to the contents of CIB_file > > I started fc18 node, execute "cibadmin -M -X '<cib > crm_feature_set="3.0.6"/>'", started fc17 node, now the nodes talk but I have > this. > > on FC18: > <nodes> > <node id="-1062731267" uname="noeud1.apec.fr" type="normal"/> > <node id="-33445696" uname="noeud2.apec.fr" type="normal"/> > <node id="3232236029" uname="noeud1.apec.fr"/> > <node id="4261521600" uname="noeud2.apec.fr"/> > <node id="1" uname="noeud1.apec.fr"/> > <node id="2" uname="noeud2.apec.fr"/> > </nodes> > > on FC17: > <nodes> > <node id="-1062731267" uname="noeud1.apec.fr" type="normal"/> > <node id="-33445696" uname="noeud2.apec.fr" type="normal"/> > <node id="2" uname="noeud2.apec.fr" type="normal"/> > <node id="1" uname="noeud1.apec.fr" type="normal"/> > </nodes> > > The nodes have two networks, 192.168.1.0/24 for external communication and > 10.1.1.0/24 with bonding for drbd. Corosync used 192.168.1.0 with udpu. > > Best regards. > > Francis > > On 08/26/2013 01:42 AM, Andrew Beekhof wrote: >> >> On 23/08/2013, at 7:18 PM, Francis SOUYRI <francis.sou...@apec.fr> 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 ? >> >> The same as the other two but stored as %u (unsigned int) instead of %d >> (signed int). >> This was a bug in older versions, you can work around it by specifying a >> (small) nodeid in corosync.conf >> >>> >>> 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 ? >> >> This should provide some more information: >> http://blog.clusterlabs.org/blog/2013/mixing-pacemaker-versions/ >> >> > > > _______________________________________________ > 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
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ 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
