OpenVZ machine causes Blade crash [message #43952] |
Wed, 02 November 2011 19:30 |
daxcurson
Messages: 1 Registered: November 2011 Location: Buenos Aires
|
Junior Member |
|
|
Hello,
We are seeing strange errors in the logs when we activate an OpenVZ machine:
Nov 2 16:07:22 bablade02 kernel: [ 751.271134] warning: `vzctl' uses 32-bit capabilities (legacy support in use)
Nov 2 16:07:22 bablade02 kernel: [ 751.273295] CT: 102: started
Nov 2 16:07:27 bablade02 corosync[2175]: [TOTEM ] Retransmit List: 4c
Nov 2 16:07:27 bablade02 corosync[2175]: [TOTEM ] Retransmit List: 4c 4d
Nov 2 16:07:27 bablade02 corosync[2175]: [TOTEM ] Retransmit List: 4c 4d 4e
Nov 2 16:07:27 bablade02 corosync[2175]: [TOTEM ] Retransmit List: 4c 4d 4e 4f
Nov 2 16:07:27 bablade02 corosync[2175]: [TOTEM ] Retransmit List: 4c 4d 4e 4f 50
Nov 2 16:07:27 bablade02 corosync[2175]: [TOTEM ] Retransmit List: 4c 4d 4e 4f 50
Nov 2 16:07:27 bablade02 corosync[2175]: [TOTEM ] Retransmit List: 4c 4d 4e 4f 50
We still don't know what those errors are. Retransmit list is mentioned in the manual as caused by possible delays in transmission but we know that we don't have any.
Wizards of OpenVZ, do you know this error? The shared storage is connected by two SAS cables to each of our IBM Bladecenter blades.
Kernel version (uname -a): Linux bablade01 2.6.32-042stab037.1 #1 SMP Fri Sep 16 22:18:06 MSD 2011 x86_64 x86_64 x86_64 GNU/Linux
Distribution: CentOS 6
OpenVZ tools version: vzctl version 3.0.29.3
Greetings,
AgustÃn
|
|
|