syslog showing corosync errors

[davlaw]

Since updating over the past week or so, I have had 2 kernel panics, each on different servers. Per suggestion under another topic I have updated again and below are listed my current versions. Not having enough time after this last update the jury is still out on that one. But I have noticed these corosync errors listed in the syslog. Not sure there is any relationship between either of these issues but I'm wondering/concerned about the fact that there are no mention of "Members Left" or "Members Joined" in these errors that are logged. What is triggering the failure?


syslog

Jun 26 08:22:37 proliant01 corosync[3407]:   [TOTEM ] A processor failed, forming new configuration.
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] CLM CONFIGURATION CHANGE
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] New Configuration:
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] #011r(0) ip(10.10.0.200)
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] #011r(0) ip(10.10.0.201)
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] #011r(0) ip(10.10.0.202)
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] #011r(0) ip(10.10.0.204)
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] Members Left:
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] Members Joined:
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] CLM CONFIGURATION CHANGE
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] New Configuration:
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] #011r(0) ip(10.10.0.200)
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] #011r(0) ip(10.10.0.201)
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] #011r(0) ip(10.10.0.202)
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] #011r(0) ip(10.10.0.204)
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] Members Left:
Jun 26 08:22:37 proliant01 corosync[3407]:   [CLM   ] Members Joined:
Jun 26 08:22:37 proliant01 corosync[3407]:   [TOTEM ] A processor joined or left the membership and a new membership was formed.
Jun 26 08:22:37 proliant01 corosync[3407]:   [CPG   ] chosen downlist: sender r(0) ip(10.10.0.200) ; members(old:4 left:0)
Jun 26 08:22:37 proliant01 corosync[3407]:   [MAIN  ] Completed service synchronization, ready to provide service.

pveversion -v

proxmox-ve-2.6.32: 3.2-129 (running kernel: 2.6.32-30-pve)
pve-manager: 3.2-4 (running version: 3.2-4/e24a91c1)
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-27-pve: 2.6.32-121
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-16-pve: 2.6.32-82
pve-kernel-2.6.32-25-pve: 2.6.32-113
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-23-pve: 2.6.32-109
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.5-1
pve-cluster: 3.0-12
qemu-server: 3.1-16
pve-firmware: 1.1-3
libpve-common-perl: 3.0-18
libpve-access-control: 3.0-11
libpve-storage-perl: 3.0-19
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-6
vzctl: 4.0-1pve5
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-8
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1

 

[tom]

without the full log its impossible to see more. check the full syslog for the reason.