Small difference in PVE installs

[Jacob Watson]

Hello!

So I've been using proxmox for quite the while now and ran across an interesting situation while configuring another system. Before-hand, both systems have been updated and are running the same kernel and pve version (4.15.18-5-pve) and one system is in a cluster with two other machines while the other is by itself.

The issue I am having is that the singular system only shows ">_Shell" while the clustered show ">_ Shell (JS)" and ">_ Shell"
It isn't a problem to me as either solution works fine, but it has bugged me and curiosity got the best of me.
Any ideas as to why or how to fix it are appreciated.

Thanks

 

[dcsapak]

seems your cluster has no current packages, or your browser cache is outdated -> try to clear it and/or upgrade your cluster

to be sure they are the same versions, you can run 'pveversion -v' on each host

 

[Jacob Watson]

Cleared my cache, checked versions on every package (they all matched) and ran update and dist-upgrade on every server. But still no cigar. They are not production servers so if I have to reinstall I wouldn't be too upset. Just trying to avoid if possible.

 

[dcsapak]

can you post your 'pveversions -v' ? are you sure you have the correct repositories configured? https://pve.proxmox.com/wiki/Package_Repositories

 

[Jacob Watson]

Clustered server output.

Spoiler

root@productionpve:~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-5-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-8
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-29
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-35
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1

Second singular server output

Spoiler

root@workbenchpve:~# pveversion -v
proxmox-ve: 5.2-2 (running kernel: 4.15.18-5-pve)
pve-manager: 5.2-9 (running version: 5.2-9/4b30e8f9)
pve-kernel-4.15: 5.2-8
pve-kernel-4.15.18-5-pve: 4.15.18-24
pve-kernel-4.13.13-2-pve: 4.13.13-33
corosync: 2.4.2-pve5
criu: 2.11.1-1~bpo90
glusterfs-client: 3.8.8-1
ksm-control-daemon: 1.2-2
libjs-extjs: 6.0.1-2
libpve-access-control: 5.0-8
libpve-apiclient-perl: 2.0-5
libpve-common-perl: 5.0-38
libpve-guest-common-perl: 2.0-18
libpve-http-server-perl: 2.0-10
libpve-storage-perl: 5.0-29
libqb0: 1.0.1-1
lvm2: 2.02.168-pve6
lxc-pve: 3.0.2+pve1-2
lxcfs: 3.0.2-2
novnc-pve: 1.0.0-2
proxmox-widget-toolkit: 1.0-20
pve-cluster: 5.0-30
pve-container: 2.0-27
pve-docs: 5.2-8
pve-firewall: 3.0-14
pve-firmware: 2.0-5
pve-ha-manager: 2.0-5
pve-i18n: 1.0-6
pve-libspice-server1: 0.12.8-3
pve-qemu-kvm: 2.11.2-1
pve-xtermjs: 1.0-5
qemu-server: 5.0-35
smartmontools: 6.5+svn4324-1
spiceterm: 3.0-5
vncterm: 1.5-3
zfsutils-linux: 0.7.11-pve1~bpo1

As for the server repositories they are all this.

deb http://ftp.debian.org/debian stretch main contrib

# PVE pve-no-subscription repository provided by proxmox.com,
# NOT recommended for production use
deb http://download.proxmox.com/debian/pve stretch pve-no-subscription

# security updates
deb http://security.debian.org stretch/updates main contrib

 

[dcsapak]

can you verify that the file 'https://ip_or_host:8006/pve2/js/pvemanagerlib.js?ver=5.2-9' gets loaded from your webinterface? (via dev console in the browser)

 

[Jacob Watson]

Indeed it does.

"https://10.0.0.151:8006/pve2/js/pvemanagerlib.js?ver=5.2-9"

If this is more hassle than it's worth I'll gladly go ahead and just reinstall though. So don't work yourself to death over this.