This bug has been copied from bug #588500 and has been proposed to be backported to 5.3 z-stream (EUS).
Recovered successfully with 687 messages: Nov 1 10:08:41 z2 openais[9796]: [TOTEM] The token was lost in the OPERATIONAL state. Nov 1 10:08:41 z2 openais[9796]: [TOTEM] Receive multicast socket recv buffer size (320000 bytes). Nov 1 10:08:41 z2 openais[9796]: [TOTEM] Transmit multicast socket send buffer size (262142 bytes). Nov 1 10:08:41 z2 openais[9796]: [TOTEM] entering GATHER state from 2. Nov 1 10:09:01 z2 openais[9796]: [TOTEM] entering GATHER state from 11. Nov 1 10:09:01 z2 openais[9796]: [TOTEM] Creating commit token because I am the rep. Nov 1 10:09:01 z2 openais[9796]: [TOTEM] Saving state aru c2f7 high seq received c5ba Nov 1 10:09:01 z2 openais[9796]: [TOTEM] Storing new sequence id for ring 84 Nov 1 10:09:01 z2 openais[9796]: [TOTEM] entering COMMIT state. Nov 1 10:09:01 z2 openais[9796]: [TOTEM] entering RECOVERY state. Nov 1 10:09:01 z2 openais[9796]: [TOTEM] position [0] member 10.15.89.15: Nov 1 10:09:01 z2 openais[9796]: [TOTEM] previous ring seq 128 rep 10.15.89.14 Nov 1 10:09:01 z2 openais[9796]: [TOTEM] aru c2f7 high delivered c2f7 received flag 0 Nov 1 10:09:01 z2 openais[9796]: [TOTEM] position [1] member 10.15.89.16: Nov 1 10:09:01 z2 openais[9796]: [TOTEM] previous ring seq 128 rep 10.15.89.14 Nov 1 10:09:01 z2 openais[9796]: [TOTEM] aru c2f7 high delivered c2f7 received flag 0 Nov 1 10:09:01 z2 openais[9796]: [TOTEM] position [2] member 10.15.89.17: Nov 1 10:09:01 z2 openais[9796]: [TOTEM] previous ring seq 128 rep 10.15.89.14 Nov 1 10:09:01 z2 openais[9796]: [TOTEM] aru c2f7 high delivered c2f7 received flag 0 Nov 1 10:09:01 z2 openais[9796]: [TOTEM] copying all old ring messages from c2f8-c5ba. Nov 1 10:09:01 z2 openais[9796]: [TOTEM] Originated 687 messages in RECOVERY. [...] openais-0.80.3-22.el5_3.16
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2010-0828.html
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Previously, an abort signal caused the cluster to exit if more then 500 messages were originated in the RECOVERY state. This update resolves this issue and behaves as expected in the RECOVERY state.