Re: [Pacemaker] pacemaker/corosync on CentOS 6.4/6.5 node offline after update
On 25 Feb 2014, at 2:18 am, Leon Fauster wrote: > Am 24.02.2014 um 12:53 schrieb fatcha...@gmx.de: >> >> so the only solution is to migrate from openais to cman ? Is there a less >> painful way? > > the "supported" solution is with cman, it does not mean that other stacks do > not > work, (to use your wording) there are just more "painful". > > Check the howtos, there are straight forward ... > Not a bad place to start: http://clusterlabs.org/doc/en-US/Pacemaker/1.1-plugin/html/Clusters_from_Scratch/_adding_cman_support.html 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
Re: [Pacemaker] pacemaker/corosync on CentOS 6.4/6.5 node offline after update
Am 24.02.2014 um 12:53 schrieb fatcha...@gmx.de: > > so the only solution is to migrate from openais to cman ? Is there a less > painful way? the "supported" solution is with cman, it does not mean that other stacks do not work, (to use your wording) there are just more "painful". Check the howtos, there are straight forward ... -- LF ___ 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
Re: [Pacemaker] pacemaker/corosync on CentOS 6.4/6.5 node offline after update
Hi Andrew, so the only solution is to migrate from openais to cman ? Is there a less painful way ? Kind regards fatcharly Gesendet: Donnerstag, 20. Februar 2014 um 23:54 Uhr Von: "Andrew Beekhof" An: "The Pacemaker cluster resource manager" Betreff: Re: [Pacemaker] pacemaker/corosync on CentOS 6.4/6.5 node offline after update On 21 Feb 2014, at 3:11 am, fatcha...@gmx.de wrote: > Hi, > > Im using a pacemaker/corosync 2 node cluster on an CentOS 6.4 to provide a loadbalancer-service via pound. > After a update with yum the updatet node is not able to work in the cluster again. > > Here is the cmr_mon and some facts about the updatet node powerpound: > > Linux powerpound 2.6.32-431.5.1.el6.x86_64 #1 SMP Wed Feb 12 00:41:43 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux > pacemaker-1.1.10-14.el6_5.2.x86_64 > corosync-1.4.1-17.el6.x86_64 > > crm_mon: > Last updated: Thu Feb 20 16:50:38 2014 > Last change: Thu Feb 20 16:50:37 2014 via crmd on powerpound > Stack: classic openais (with plugin) Quite possibly a bug/change in the plugin above. Did you not see the very noisy error about not using said plugin? > Current DC: powerpound - partition with quorum > Version: 1.1.10-14.el6_5.2-368c726 > 2 Nodes configured, 2 expected votes > 7 Resources configured > > Node pilotpound: UNCLEAN (offline) > Node powerpound: standby > > > And here some facts about not patched/updatet node pilotpound: > > Linux pilotpound 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed Aug 28 17:19:38 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > pacemaker-1.1.8-7.el6.x86_64 > corosync-1.4.1-15.el6_4.1.x86_64 > > crm_mon: > Last updated: Thu Feb 20 16:50:38 2014 > Last change: Thu Feb 20 16:50:37 2014 via crmd on powerpound > Stack: classic openais (with plugin) > Current DC: pilotpound - partition with quorum > Version: 1.1.10-14.el6_5.2-368c726 > 2 Nodes configured, 2 expected votes > 7 Resources configured. > > Node powerpound: OFFLINE (standby) > Online: [ pilotpound ] > HA_IP_1 (ocf::heartbeat:IPaddr2): Started pilotpound > HA_IP_2 (ocf::heartbeat:IPaddr2): Started pilotpound > HA_IP_3 (ocf::heartbeat:IPaddr2): Started pilotpound > HA_IP_4 (ocf::heartbeat:IPaddr2): Started pilotpound > HA_IP_5 (ocf::heartbeat:IPaddr2): Started pilotpound > Clone Set: pingclone [ping-gateway] > Started: [ pilotpound ] > Stopped: [ ping-gateway:1 ] > > > > > > Any help would be appreciated > > thanks in advance > > fatcharly > > > ___ > 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 ___ 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
Re: [Pacemaker] pacemaker/corosync on CentOS 6.4/6.5 node offline after update
On 21 Feb 2014, at 3:11 am, fatcha...@gmx.de wrote: > Hi, > > Im using a pacemaker/corosync 2 node cluster on an CentOS 6.4 to provide a > loadbalancer-service via pound. > After a update with yum the updatet node is not able to work in the cluster > again. > > Here is the cmr_mon and some facts about the updatet node powerpound: > > Linux powerpound 2.6.32-431.5.1.el6.x86_64 #1 SMP Wed Feb 12 00:41:43 UTC > 2014 x86_64 x86_64 x86_64 GNU/Linux > pacemaker-1.1.10-14.el6_5.2.x86_64 > corosync-1.4.1-17.el6.x86_64 > > crm_mon: > Last updated: Thu Feb 20 16:50:38 2014 > Last change: Thu Feb 20 16:50:37 2014 via crmd on powerpound > Stack: classic openais (with plugin) Quite possibly a bug/change in the plugin above. Did you not see the very noisy error about not using said plugin? > Current DC: powerpound - partition with quorum > Version: 1.1.10-14.el6_5.2-368c726 > 2 Nodes configured, 2 expected votes > 7 Resources configured > > Node pilotpound: UNCLEAN (offline) > Node powerpound: standby > > > And here some facts about not patched/updatet node pilotpound: > > Linux pilotpound 2.6.32-358.18.1.el6.x86_64 #1 SMP Wed Aug 28 17:19:38 UTC > 2013 x86_64 x86_64 x86_64 GNU/Linux > pacemaker-1.1.8-7.el6.x86_64 > corosync-1.4.1-15.el6_4.1.x86_64 > > crm_mon: > Last updated: Thu Feb 20 16:50:38 2014 > Last change: Thu Feb 20 16:50:37 2014 via crmd on powerpound > Stack: classic openais (with plugin) > Current DC: pilotpound - partition with quorum > Version: 1.1.10-14.el6_5.2-368c726 > 2 Nodes configured, 2 expected votes > 7 Resources configured. > > Node powerpound: OFFLINE (standby) > Online: [ pilotpound ] > HA_IP_1 (ocf::heartbeat:IPaddr2): Started pilotpound > HA_IP_2 (ocf::heartbeat:IPaddr2): Started pilotpound > HA_IP_3 (ocf::heartbeat:IPaddr2): Started pilotpound > HA_IP_4 (ocf::heartbeat:IPaddr2): Started pilotpound > HA_IP_5 (ocf::heartbeat:IPaddr2): Started pilotpound > Clone Set: pingclone [ping-gateway] > Started: [ pilotpound ] > Stopped: [ ping-gateway:1 ] > > > > > > Any help would be appreciated > > thanks in advance > > fatcharly > > > ___ > 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
