<span>nodename</span> showing up in front of everything

M

mikewich

New Member
Feb 27, 2026
18
1
3
we ran into a weird issue. when we came in this morning and checked our main cluster node, we get <span> in front of everything in the GUI. reset browser cache and still there. tried apt reset via shell and still no go. anyone ever run into this before?

1773064899406.png
 
here are steps I have taken:
rebooted nodes01 (main node)
ran api reset commands on node01
when I log into node02 or 03 no issues. only 01 and it is the main cluster node.
 
Hi!

Could you try force refreshing the web interface with Ctrl+F5 or Ctrl+Shift+R? Which version of pve-manager is running on the node?
 
dakralex said:
Hi!

Could you try force refreshing the web interface with Ctrl+F5 or Ctrl+Shift+R? Which version of pve-manager is running on the node?
Click to expand...
Hey Dakralex,
Running 9.1.6 (latest patched) and the 2 options you proposed did not work.
 
Last edited:
Hey, maybe you could share your:


Code: 
journalctl --unit pveproxy --boot

Maybe we find some errors in there...
 
Saron said:
Hey, maybe you could share your:


Code: 
journalctl --unit pveproxy --boot

Maybe we find some errors in there...
Click to expand...
root@node01:~# journalctl --unit pveproxy --boot
Mar 09 08:32:35 node01 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Mar 09 08:33:01 node01 pveproxy[2747]: Using '/etc/pve/local/pveproxy-ssl.pem' as certi>
Mar 09 08:33:01 node01 pveproxy[2888]: starting server
Mar 09 08:33:01 node01 pveproxy[2888]: starting 3 worker(s)
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2889 started
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2890 started
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2891 started
Mar 09 08:33:01 node01 systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Mar 09 08:36:39 node01 systemd[1]: Stopping pveproxy.service - PVE API Proxy Server...
Mar 09 08:36:40 node01 pveproxy[2888]: received signal TERM
Mar 09 08:36:40 node01 pveproxy[2888]: server closing
Mar 09 08:36:40 node01 pveproxy[2890]: worker exit
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2890 finished
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2891 finished
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2889 finished
Mar 09 08:36:40 node01 pveproxy[2888]: server stopped
Mar 09 08:36:41 node01 pveproxy[4913]: got inotify poll request in wrong process - disa>
Mar 09 08:36:41 node01 pveproxy[4912]: got inotify poll request in wrong process - disa>
Mar 09 08:36:41 node01 pveproxy[4912]: worker exit
Mar 09 08:36:41 node01 pveproxy[4913]: worker exit
Mar 09 08:36:41 node01 systemd[1]: pveproxy.service: Deactivated successfully.
Mar 09 08:36:41 node01 systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Mar 09 08:36:41 node01 systemd[1]: pveproxy.service: Consumed 2.617s CPU time, 409M mem>
Mar 09 08:36:42 node01 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
lines 1-24...skipping...
Mar 09 08:32:35 node01 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Mar 09 08:33:01 node01 pveproxy[2747]: Using '/etc/pve/local/pveproxy-ssl.pem' as certi>
Mar 09 08:33:01 node01 pveproxy[2888]: starting server
Mar 09 08:33:01 node01 pveproxy[2888]: starting 3 worker(s)
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2889 started
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2890 started
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2891 started
Mar 09 08:33:01 node01 systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Mar 09 08:36:39 node01 systemd[1]: Stopping pveproxy.service - PVE API Proxy Server...
Mar 09 08:36:40 node01 pveproxy[2888]: received signal TERM
Mar 09 08:36:40 node01 pveproxy[2888]: server closing
Mar 09 08:36:40 node01 pveproxy[2890]: worker exit
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2890 finished
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2891 finished
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2889 finished
Mar 09 08:36:40 node01 pveproxy[2888]: server stopped
Mar 09 08:36:41 node01 pveproxy[4913]: got inotify poll request in wrong process - disa>
Mar 09 08:36:41 node01 pveproxy[4912]: got inotify poll request in wrong process - disa>
Mar 09 08:36:41 node01 pveproxy[4912]: worker exit
Mar 09 08:36:41 node01 pveproxy[4913]: worker exit
Mar 09 08:36:41 node01 systemd[1]: pveproxy.service: Deactivated successfully.
Mar 09 08:36:41 node01 systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Mar 09 08:36:41 node01 systemd[1]: pveproxy.service: Consumed 2.617s CPU time, 409M mem>
Mar 09 08:36:42 node01 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Mar 09 08:36:43 node01 pveproxy[4942]: Using '/etc/pve/local/pveproxy-ssl.pem' as certi>
Mar 09 08:36:43 node01 pveproxy[4943]: starting server
Mar 09 08:36:43 node01 pveproxy[4943]: starting 3 worker(s)
Mar 09 08:36:43 node01 pveproxy[4943]: worker 4944 started
Mar 09 08:36:43 node01 pveproxy[4943]: worker 4945 started
Mar 09 08:36:43 node01 pveproxy[4943]: worker 4946 started
Mar 09 08:36:43 node01 systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Mar 09 08:43:54 node01 systemd[1]: Stopping pveproxy.service - PVE API Proxy Server...
Mar 09 08:43:55 node01 pveproxy[4943]: received signal TERM
lines 1-33...skipping...
Mar 09 08:32:35 node01 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Mar 09 08:33:01 node01 pveproxy[2747]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
Mar 09 08:33:01 node01 pveproxy[2888]: starting server
Mar 09 08:33:01 node01 pveproxy[2888]: starting 3 worker(s)
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2889 started
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2890 started
Mar 09 08:33:01 node01 pveproxy[2888]: worker 2891 started
Mar 09 08:33:01 node01 systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Mar 09 08:36:39 node01 systemd[1]: Stopping pveproxy.service - PVE API Proxy Server...
Mar 09 08:36:40 node01 pveproxy[2888]: received signal TERM
Mar 09 08:36:40 node01 pveproxy[2888]: server closing
Mar 09 08:36:40 node01 pveproxy[2890]: worker exit
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2890 finished
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2891 finished
Mar 09 08:36:40 node01 pveproxy[2888]: worker 2889 finished
Mar 09 08:36:40 node01 pveproxy[2888]: server stopped
Mar 09 08:36:41 node01 pveproxy[4913]: got inotify poll request in wrong process - disabling inotify
Mar 09 08:36:41 node01 pveproxy[4912]: got inotify poll request in wrong process - disabling inotify
Mar 09 08:36:41 node01 pveproxy[4912]: worker exit
Mar 09 08:36:41 node01 pveproxy[4913]: worker exit
Mar 09 08:36:41 node01 systemd[1]: pveproxy.service: Deactivated successfully.
Mar 09 08:36:41 node01 systemd[1]: Stopped pveproxy.service - PVE API Proxy Server.
Mar 09 08:36:41 node01 systemd[1]: pveproxy.service: Consumed 2.617s CPU time, 409M memory peak.
Mar 09 08:36:42 node01 systemd[1]: Starting pveproxy.service - PVE API Proxy Server...
Mar 09 08:36:43 node01 pveproxy[4942]: Using '/etc/pve/local/pveproxy-ssl.pem' as certificate for the web interface.
Mar 09 08:36:43 node01 pveproxy[4943]: starting server
Mar 09 08:36:43 node01 pveproxy[4943]: starting 3 worker(s)
Mar 09 08:36:43 node01 pveproxy[4943]: worker 4944 started
Mar 09 08:36:43 node01 pveproxy[4943]: worker 4945 started
Mar 09 08:36:43 node01 pveproxy[4943]: worker 4946 started
Mar 09 08:36:43 node01 systemd[1]: Started pveproxy.service - PVE API Proxy Server.
Mar 09 08:43:54 node01 systemd[1]: Stopping pveproxy.service - PVE API Proxy Server...
Mar 09 08:43:55 node01 pveproxy[4943]: received signal TERM
Mar 09 08:43:55 node01 pveproxy[4943]: server closing
Mar 09 08:43:55 node01 pveproxy[4945]: worker exit
Mar 09 08:43:55 node01 pveproxy[4944]: worker exit
Mar 09 08:43:55 node01 pveproxy[4943]: worker 4945 finished
Mar 09 08:43:55 node01 pveproxy[4943]: worker 4944 finished
Mar 09 08:43:55 node01 pveproxy[4943]: worker 4946 finished
 
What did pveupdate; pveupgrade say? If incognito mode/different browser doesn't help either can you check this?
Bash: 
apt install -y debsums
debsums -as
 
Last edited:
Impact said:
What did pveupdate; pveupgrade say? If incognito mode/different browser doesn't help either can you check this?
Bash: 
apt install -y debsums
debsums -as
Click to expand...
Your System is up-to-date for the "pveupdate; pveupgrade"

ran the other commands and still not fixed. this is only happening on the main 1 node. the other 2 if you log in do not have this issue. very strange.
 
The command doesn't fix anything but report changed files. The idea was that you share the command outputs.
 
Last edited:
command 'apt-get update' failed: exit code 100
Starting system upgrade: apt-get dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
libpython3.13 libsqlite3-mod-ceph python3-cheroot python3-cherrypy3 python3-dateutil
python3-jaraco.collections python3-legacy-cgi python3-logutils python3-natsort python3-packaging
python3-pecan python3-portend python3-simplegeneric python3-tempora python3-webob python3-werkzeug
python3-zc.lockfile sudo
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Your System is up-to-date
 
node 01 is the main cluster node. can that be transferred to another node and then we can rebuild node 01? just asking as a last resort thing here. good thing this is our poc environment.
 
Impact said:
What about the debsums -as output?
Also this doesn't look good and is exactly why the output is so important

apt update might give us a hint what's wrong.
Click to expand...
apt update
Hit:1 http://deb.debian.org/debian trixie InRelease
Hit:2 http://deb.debian.org/debian trixie-updates InRelease
Hit:3 http://security.debian.org/debian-security trixie-security InRelease
Hit:4 http://download.proxmox.com/debian/ceph-squid trixie InRelease
Err:5 https://enterprise.proxmox.com/debian/pve trixie InRelease
401 Unauthorized [IP: 66.70.154.82 443]
Error: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/trixie/InRelease 401 Unauthorized [IP: 66.70.154.82 443]
Error: The repository 'https://enterprise.proxmox.com/debian/pve trixie InRelease' is not signed.
Notice: Updating from such a repository can't be done securely, and is therefore disabled by default.
Notice: See apt-secure(8) manpage for repository creation and user configuration details.
Warning: Target Packages (pve-enterprise/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.sources:1 and /etc/apt/sources.list.d/pve-enterprise.sources:2
Warning: Target Packages (pve-enterprise/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.sources:1 and /etc/apt/sources.list.d/pve-enterprise.sources:2
Warning: Target Translations (pve-enterprise/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/pve-enterprise.sources:1 and /etc/apt/sources.list.d/pve-enterprise.sources:2
root@txprx01n01:~#
 
Impact said:
Well that expalins it. Disable the enterprise and configure the no-subscription repos, then try apt update && apt dist-upgrade again.
There should be absolutely no errors or warnings. Please don't quote every message.
Click to expand...
pt update; apt dist-upgrade
bash: pt: command not found
The following packages were automatically installed and are no longer required:
libpython3.13 python3-dateutil python3-natsort python3-simplegeneric python3-zc.lockfile
libsqlite3-mod-ceph python3-jaraco.collections python3-packaging python3-tempora sudo
python3-cheroot python3-legacy-cgi python3-pecan python3-webob
python3-cherrypy3 python3-logutils python3-portend python3-werkzeug
Use 'apt autoremove' to remove them.

Summary:
Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0
 
You must log in or register to reply here.
Top Bottom
Back