[Solved] After update from 9.1.6 to 9.2.3, Nothing shows under Datacenter

[ravem0n]

Hello,

First time poster, long time lurker. I recently updated from 9.1.6 to 9.2.3 and pretty much everything under my Datacenter disappeared.


but oddly enough my vms and lxc do run and start. its just through the ui it's just blank.

I've reset my certificates back to default and attempted to restart my services but no luck.

Not sure what else to do.

 

[bbgeek17]

Hi @ravem0n , welcome to the forum.

Have you checked the Console of the browser for errors? Have you previously run any scripts that may have modified the code?

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[ravem0n]

Oh did not think to look there.

I do see this:

Uncaught TypeError: Cannot read properties of undefined (reading 'node')
at constructor.initComponent (pvemanagerlib.js?ver=9.2.3:33990:68)
at constructor (ext-all.js?ver=7.0.0:22:560804)
at new constructor (ext-all.js?ver=7.0.0:22:102290)
at Object.widget (ext-all.js?ver=7.0.0:22:116236)
at ctor.create (ext-all.js?ver=7.0.0:22:212679)
at constructor.lookupComponent (ext-all.js?ver=7.0.0:22:1230147)
at constructor.prepareItems (ext-all.js?ver=7.0.0:22:1235133)
at constructor.add (ext-all.js?ver=7.0.0:22:1225047)
at constructor.initItems (ext-all.js?ver=7.0.0:22:1229519)
at constructor.initItems (ext-all.js?ver=7.0.0:22:1412385)

And this one as well

Failed to load resource: the server responded with a status of 424 (node is not in a cluster, no join info available!)

I don't know why it says it's not in a cluster...... it was always a stand alone with makes this odd.

 

[bbgeek17]

I would review the upgrade logs/output, if still available, for any errors.
I would then reboot the server and closely review the logs starting from fresh boot, both journalctl and /var/log/pve/*
I would also run:
- dpkg -V
- apt install debsums && debsums -c

Cheers

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Impact]

I have some docs about finding modified system/package files here. Bbgeek17 already explained it though. This tends to happen when running helper scripts. Especially the anti nag portion.
To revert what the anti nag script did you can try this

rm -f /etc/apt/apt.conf.d/no-nag-script
apt install --reinstall pve-manager proxmox-widget-toolkit
systemctl restart pvedaemon pveproxy

I would not rely on informational messages a script puts out after it encounters such an error.

 

[ravem0n]

I found the issue. When I updated proxmox, it also updated the truenas proxmox plugin which changed a ton of options on one of my mounts.

Pretty much reran the configurator for my iscsi mount and it fixed it.

Thanks for all the help all!