Oracle Linux 6 server unexpectedly reboots with the following error: corosync[xxxx]: [TOTEM ] A processor failed, forming new configuration.
(Doc ID 2524219.1)
Last updated on MAY 08, 2020
Applies to:
Linux OS - Version Oracle Linux 6.0 and laterLinux x86-64
Symptoms
A server running Oracle Linux 6 unexpectedly rebooted, with the following messages logged from corosync:
From /var/log/messages:
Dec 10 21:06:01 <HOSTNAME> corosync[55603]: [TOTEM ] A processor failed, forming new configuration. Dec 10 21:06:03 <HOSTNAME> corosync[55603]: [QUORUM] Members[1]: 4 Dec 10 21:06:03 <HOSTNAME> corosync[55603]: [TOTEM ] A processor joined or left the membership and a new membership was formed. Dec 10 21:06:03 <HOSTNAME> dlm_controld[55994]: node_history_cluster_remove no nodeid 3 Dec 10 21:06:03 <HOSTNAME> rgmanager[56561]: State change: CLUSTERNODE1-HA DOWN Dec 10 21:06:03 <HOSTNAME> corosync[55603]: [CPG ] chosen downlist: sender r(0) ip(XXX.XXX.XXX.XXX) r(1) ip(XXX.XXX.XXX.XXX) ; members(old:2 left:1) Dec 10 21:06:03 <HOSTNAME> kernel: dlm: closing connection to node 3 Dec 10 21:06:03 <HOSTNAME> corosync[55603]: [MAIN ] Completed service synchronization, ready to provide service. Dec 10 21:06:03 <HOSTNAME> fenced[55966]: fencing node CLUSTERNODE1-HA Dec 10 21:06:03 <HOSTNAME> corosync[55603]: [TOTEM ] Automatically recovered ring 1 Dec 10 21:06:25 <HOSTNAME> fenced[55966]: fence CLUSTERNODE1-HA success
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |