[Pacemaker] Problem during Cluster Upgrade
Andreas Kurz
andreas at hastexo.com
Thu Apr 12 21:08:14 UTC 2012
On 04/11/2012 04:26 PM, Karl Rößmann wrote:
> Hi all,
>
> I'm upgrading a three node cluster from SLES 11 SP1 to SLES SP2 node by
> node.
> the upgrade includes:
> corosync-1.3.3-0.3.1 to corosync-1.4.1-0.13.1
> pacemaker-1.1.5-5.9.11.1 to pacemaker-1.1.6-1.27.26
> kernel 2.6.32.54-0.3-xen to 3.0.13-0.27-xen
>
> After Upgrading the first node and restarting the cluster I get these
> never ending messages on the DC (which is not the updated node)
>
> Apr 11 14:19:26 orion14 corosync[6865]: [TOTEM ] Type of received
> message is wrong... ignoring 6.
> Apr 11 14:19:27 orion14 corosync[6865]: [TOTEM ] Type of received
> message is wrong... ignoring 6.
> Apr 11 14:19:28 orion14 corosync[6865]: [TOTEM ] Type of received
> message is wrong... ignoring 6.
> Apr 11 14:19:29 orion14 corosync[6865]: [TOTEM ] Type of received
> message is wrong... ignoring 6.
>
Any change you are using redundant rings with corosync 1.3? IIRC there
have been protocol changes in corosync 1.4 to support auto-recovery of
rings.
> the updated node is still in STANDBY mode.
> Should I ignore the message and put the mode to ONLINE ?
> I don't want the cluster to crash, there are running services
> on the other two nodes.
> So now I stopped the openais on the updated node: no more messages.
> the other two nodes are still up and working.
Switch your cluster into maintenance-mode and you can safely stop
pacemaker and corosync without affecting your services on all cluster
nodes. Upgrade corosync and pacemaker on all nodes and start it up ...
if cluster membership and initial resource probing looks good -- disable
maintenance-mode
Regards,
Andreas
--
Need help with Pacemaker?
http://www.hastexo.com/now
>
> Any ideas ?
>
> Karl
>
>
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 222 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20120412/9811c55a/attachment-0004.sig>
More information about the Pacemaker
mailing list