<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
Last night I upgraded our cluster to version 3.4 (no subscription).
During this same time period, we rebooted several of the nodes in
order to install some 10G networking cards.<br>
Everything seemed to go well, however at some point after all the
nodes were upgraded (and a few of them were rebooted), I noticed
that all the other nodes were showing up red in the web gui.<br>
<br>
Using pvecm I am able to see that the Quorum status is listed as
'Activity blocked'.<br>
<br>
root@proxmox13:~# pvecm status<br>
Version: 6.2.0<br>
Config Version: 25<br>
Cluster Name: ProxmoxVE2<br>
Cluster Id: 33252<br>
Cluster Member: Yes<br>
Cluster Generation: 1208<br>
Membership state: Cluster-Member<br>
Nodes: 1<br>
Expected votes: 19<br>
Total votes: 1<br>
Node votes: 1<br>
Quorum: 10 Activity blocked<br>
Active subsystems: 1<br>
Flags: <br>
Ports Bound: 0 <br>
Node name: proxmox13<br>
Node ID: 12<br>
Multicast addresses: 239.192.129.102 <br>
Node addresses: 172.31.2.48 <br>
<br>
<br>
Here are the version details:<br>
<br>
root@proxmox13:~# pveversion -v<br>
proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-26-pve)<br>
pve-manager: 3.4-1 (running version: 3.4-1/3f2d890e)<br>
pve-kernel-2.6.32-20-pve: 2.6.32-100<br>
pve-kernel-2.6.32-37-pve: 2.6.32-147<br>
pve-kernel-2.6.32-26-pve: 2.6.32-114<br>
lvm2: 2.02.98-pve4<br>
clvm: 2.02.98-pve4<br>
corosync-pve: 1.4.7-1<br>
openais-pve: 1.1.4-3<br>
libqb0: 0.11.1-2<br>
redhat-cluster-pve: 3.2.0-2<br>
resource-agents-pve: 3.9.2-4<br>
fence-agents-pve: 4.0.10-2<br>
pve-cluster: 3.0-16<br>
qemu-server: 3.3-20<br>
pve-firmware: 1.1-3<br>
libpve-common-perl: 3.0-24<br>
libpve-access-control: 3.0-16<br>
libpve-storage-perl: 3.0-31<br>
pve-libspice-server1: 0.12.4-3<br>
vncterm: 1.1-8<br>
vzctl: 4.0-1pve6<br>
vzprocps: 2.0.11-2<br>
vzquota: 3.1-2<br>
pve-qemu-kvm: 2.1-12<br>
ksm-control-daemon: 1.1-1<br>
glusterfs-client: 3.5.2-1<br>
<br>
<br>
Might someone suggest the best way to get the cluster back into a
healthy state?<br>
<br>
Thanks in advance,<br>
<br>
Shain<br>
<br>
<div class="moz-signature">-- <br>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title></title>
<span class="Apple-style-span" style="border-collapse: separate;
color: rgb(0, 0, 0); font-family: Times; font-style: normal;
font-variant: normal; font-weight: normal; letter-spacing:
normal; line-height: normal; orphans: 2; text-indent: 0px;
text-transform: none; white-space: normal; widows: 2;
word-spacing: 0px; font-size: medium;"><span
class="Apple-style-span" style="font-family: 'Times New
Roman'; font-size: 16px;"><sub><font size="3" face="Arial"><span
style="font-size: 12pt; font-family: Arial;"><img
alt="NPR" moz-do-not-send="true"
src="file:///Users/smiley/Pictures/npr_log_small.jpg"
align="top" width="40" height="13"> </span></font></sub><font
color="gray" size="1" face="Arial"><span style="font-size:
9pt; font-family: Arial; color: gray;">| Shain Miley|
Manager of Systems and Infrastructure, Digital Media |
<a class="moz-txt-link-abbreviated" href="mailto:smiley@npr.org">smiley@npr.org</a> | p: 202-513-3649</span></font></span></span>
</div>
</body>
</html>