Quantcast
Channel: Proxmox Support Forum
Viewing all articles
Browse latest Browse all 171621

PVE 3.2 : no split button for console on one node

$
0
0
Hi,

I have a four nodes cluster. It was updated recently to pVE 3.2. On node 1, I cannot connect on VMs with spice. On the three other nodes, It is working fine. I can even connect on VMs on this node with Spice from other nodes.

On this node, I have no option 'Console viewer' in web interface. So I have no split button for console on that node. I have a split button on all other nodes. So it seems that something was not upgraded correctly on this node. But with pveversion, I don't see any difference between packages available on different nodes. VNC is working fine, and I already rebooted the server. I don't see anything special in the logs.
Any idea ?

Code:

root@srv-virt1# pveversion -v
proxmox-ve-2.6.32: 3.2-121 (running kernel: 2.6.32-27-pve)
pve-manager: 3.2-1 (running version: 3.2-1/1933730b)
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-95
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-26-pve: 2.6.32-114
pve-kernel-2.6.32-18-pve: 2.6.32-88
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-15
pve-firmware: 1.1-2
libpve-common-perl: 3.0-14
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-1pve4
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.7-4
ksm-control-daemon: 1.1-1
glusterfs-client: 3.4.2-1


Viewing all articles
Browse latest Browse all 171621

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>