No web GUI after upgrade from 9.0.11 to 9.1.6

K

Kordian

Renowned Member
Mar 31, 2018
38
0
71
53
Hello,
I had this issue already when upgrading from 8 to 9. Now it is there again.
When I try accessing the GUI I get these errors:
Uncaught SyntaxError: missing } after property list proxmoxlib.js:750:2note: { opened at line 42, column 29proxmoxlib.js:42:29
Uncaught TypeError: can't access property "defaultText", Proxmox.Utils is undefined
<anonymous> https://xxxxxxxxxx:8006/pve2/js/pvemanagerlib.js?ver=9.1.6:2094
pvemanagerlib.js:2094:13
XHRGET
https://xxxxxxxxx:8006/PVE/StdWorkspace.js?_dc=1772539176756
[HTTP/1.1 500 no such file '/PVE/StdWorkspace.js' 2ms]

XML-Verarbeitungsfehler: Syntax-Fehler
Adresse: https://xxxxxxxxxx:8006/PVE/StdWorkspace.js?_dc=1772539176756
Zeile Nr. 1, Spalte 1: StdWorkspace.js:1:1
Uncaught TypeError: c is not a constructor
ExtJS 2
<anonymous> https://xxxxxxxxxxxxx:8006/#v1:0:18:4::::::::45
ExtJS 15
ext-all.js:3:8

The last time it was this damn proxmox-widget-toolkit and its proxmoxlib.js file. At this occasion I replaced this file with one from the previous working version and that did the trick.
Now it does not help anymore.
I have a cluster of 3 nodes, two are not working anymore, one that has not been upgraded still shows the gui.
Would really appreciate help. I know there are many different solutions here and none is working at the moment. Tried this:

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

as well as reinstalling the pve manager and the widget toolkit.

Thank you in advance!
 
Hi @Kordian ,
99% of similarly reported issues were related to community script hack to remove subscription reminder on login.

Recent versions of the hack implement a bash script hook that executes automatically and pulls/patches the files after upgrade in the background.

Users reporting similar symptoms had their systems "patched" with incompatible patches and broken.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: Johannes S
have the same issue
used PVE post install script from helper script, but i guess pve 9.1.6 update broke with that script
removed all lines in /usr/local/bin/pve-remove-nag.sh file so it doesn't break pve when updating
reinstalled pve-manager and proxmox-widget-toolkit and restarted pveproxy pvestatd and pvedaemon but didn't work
what am'i missing ,
what is the solution or i'm i condemned to reinstall all (can't think this is the only solution)

please help!
 
Hi @Charrat, welcome to the forum.

Other users in your situation reported that they were able to restore functionality once the automated patching was removed, and proper packages were reinstalled. So it seems like that should be a possibility for you. There are multiple threads discussing recovery steps, have you reviewed them all, or at least some?

You may want to look into "debsums" command, which may need to be installed.

Finally, have you fully refreshed your browser?

If all else fails, you may want to reach out to the authors of the helper-scripts, or proceed with reinstallation.

Cheers.

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
  • Like
Reactions: Johannes S
@Charrat , I seem to remember that in similar cases, harmful repositories occurred to be added by these khe-khe-...helper scripts.
So just in case, check what is below /etc/apt/
 
  • Like
Reactions: Johannes S
Hello,
Coming back to my original post. I have no patching of my clusters. Neither anything special installed. The only thing is the proxmox-widget-toolkit, which -correct me if I am wrong - is an official proxmox tool.
Therefore I think tha case is strictly for the widget guys, and the result is incredible to me.
Apart from the cluster (which is running since 8.something version, so used for quite some time) I recently installed a fresh 8 proxmox and upgraded it to 9 version. The upgrade from 9.0.11 to 9.1.6 on this single machine worked without problems.
So what I did, was I took the proxmoxlib.js file from this single machine, deleted the file on the faulty cluster machines and created a new file with the content from the working single machine.
Result - it is now working.
And here comes the "incredible" part: the content of the file was actually IDENTICAL on both faulty and working machines.
Therefore I am unable to explain what is actually wrong with the proxmoxlib.js file and proxmox-widget-toolkit.
But, since it is a permanent issue on both my clusters, can some programmer of the toolkit and the damn proxmoxlib.js file look at the issue and solve it? PLEASE!
I know there are many people having exactly the same problem and clearly proxmoxlib.js is the issue.
Thank you very much in advance!
 
Last edited:
This file is often altered by post-install- or nag screen scripts. These tools are NOT official are you sure you didn't use one of these? Issues caused by inofficial scripts should be filed at the developer of that scripts.

Personally I avoid these things
 
The next time the errors Shows up run
debsums -c in a console. This would show whether any file from a Debian package was altered
 
Well, since I found a solution, what is the point???
The culprit is the proxmoxlib.js within the proxmox-widget-toolkit.
Secondly, are you expecting me to run another upgrade with the knowledge of the future problem on a production cluster?
Sorry, but are you the programmer of the file?
 
There are a few scripts like that. Not all of them have the same name.

But you’re right, of course – the snippet does solve the ‘problem’.
 
  • Like
Reactions: Johannes S
Johannes S said:
The next time the errors Shows up run
debsums -c in a console. This would show whether any file from a Debian package was altered
Click to expand...
Doesn't seem to work....

Bash: 
root@Froto:~# debsums -c
-bash: debsums: command not found
root@Froto:~# apt install debsums
The following packages were automatically installed and are no longer required:
  proxmox-headers-6.17.13-2-pve  proxmox-kernel-6.17.13-2-pve-signed
Use 'apt autoremove' to remove them.

Installing:
  debsums

Installing dependencies:
  libfile-fnmatch-perl

Summary:
  Upgrading: 0, Installing: 2, Removing: 0, Not Upgrading: 0
  Download size: 51.5 kB
  Space needed: 154 kB / 180 GB available

Continue? [Y/n]
Get:1 http://deb.debian.org/debian trixie/main amd64 libfile-fnmatch-perl amd64 0.02-3+b4 [10.3 kB]
Get:2 http://deb.debian.org/debian trixie/main amd64 debsums all 3.0.2.3 [41.2 kB]
Fetched 51.5 kB in 0s (122 kB/s)
Selecting previously unselected package libfile-fnmatch-perl.
(Reading database ... 174293 files and directories currently installed.)
Preparing to unpack .../libfile-fnmatch-perl_0.02-3+b4_amd64.deb ...
Unpacking libfile-fnmatch-perl (0.02-3+b4) ...
Selecting previously unselected package debsums.
Preparing to unpack .../debsums_3.0.2.3_all.deb ...
Unpacking debsums (3.0.2.3) ...
Setting up libfile-fnmatch-perl (0.02-3+b4) ...
Setting up debsums (3.0.2.3) ...
Processing triggers for man-db (2.13.1-1) ...
Removing subscription nag from UI...
root@Froto:~# debsums -c
/lib/modules/6.17.13-2-pve/modules.alias
/lib/modules/6.17.13-2-pve/modules.alias.bin
/lib/modules/6.17.13-2-pve/modules.dep
/lib/modules/6.17.13-2-pve/modules.dep.bin
/lib/modules/6.17.13-2-pve/modules.symbols.bin
/lib/modules/6.17.13-3-pve/modules.alias
/lib/modules/6.17.13-3-pve/modules.alias.bin
/lib/modules/6.17.13-3-pve/modules.dep
/lib/modules/6.17.13-3-pve/modules.dep.bin
/lib/modules/6.17.13-3-pve/modules.symbols.bin
/lib/modules/7.0.0-1-rc6-pve/modules.alias
/lib/modules/7.0.0-1-rc6-pve/modules.alias.bin
/lib/modules/7.0.0-1-rc6-pve/modules.dep
/lib/modules/7.0.0-1-rc6-pve/modules.dep.bin
/lib/modules/7.0.0-1-rc6-pve/modules.symbols.bin

It does not show the file that the Nag remover modified.
 
Thanks, this confirms that indeed at the moment you don't have a widget file altered by a script, so everything should be ok. Now I know you already said this, but in the past we had some users here, who somehow forgot that they had something which messed up their install. I just wanted to be sure ;)
If the error occurs again (you said it happens from time to time on all your machines) the file will show up in the debsums -c output if some tool or person messed with the widget files. I understand correctly that at the moment you don't have the issue anymore?
 
Once again: does any of you know the guys that programmed the proxmoxlib.js within the proxmox-widget-toolkit?
Please stick to the subject of this post.
Thank you in advance!
 
Last edited:
This file is not static but is generated during the build process (see makefile in https://git.proxmox.com/?p=proxmox-...0e41aea8ed7f6954cb65ff83def0e81c19cea;hb=HEAD ) The developers who participated at that part can be found in the git history at https://git.proxmox.com/?p=proxmox-...0e41aea8ed7f6954cb65ff83def0e81c19cea;hb=HEAD

I doubt however that your error is anything for the developers since after all at the moment the issue can not be reproduced and other reports I'm aware of all envolved the usage of some helper-script/nag screeen removal. I also find your demanding tone quite off-putting. If you don't want any attempt to help just say it and I will ignore you in the future.
 
  • Like
Reactions: Ernst T.
Johannes S said:
This file is not static but is generated during the build process (see makefile in https://git.proxmox.com/?p=proxmox-...0e41aea8ed7f6954cb65ff83def0e81c19cea;hb=HEAD ) The developers who participated at that part can be found in the git history at https://git.proxmox.com/?p=proxmox-...0e41aea8ed7f6954cb65ff83def0e81c19cea;hb=HEAD

I doubt however that your error is anything for the developers since after all at the moment the issue can not be reproduced and other reports I'm aware of all envolved the usage of some helper-script/nag screeen removal. I also find your demanding tone quite off-putting. If you don't want any attempt to help just say it and I will ignore you in the future.
Click to expand...
I totally cannot understand you and your "I am the God" statements.
I will give you an example: who gave you the right to claim this:
"the issue can not be reproduced"
The fact is I am capable of reproducing the issue at any time and cannot understand how a person can write such thing.
I am totally stunned by your statements here (which all give absolutely no solution, by the way - not my opinion, see posts above) and therefore I totally do not know how to provide unoffensive answer to a person with "I am the God" attitude.
I know the problem.
I found the solution.
Not because "I am the God, and you are not"!
The solution is stupid.
Nevertheless it is efficient and 100% solves the problem.
I am not seeking somebody to constantly prove me wrong and producing false statements.
I am seeking somebody being able to explain why my solution works and provide appropriate adjustments to the upgrade process for the future. Not because "I am the God", but that hundreds of Proxmox users have EXACTLY the same problem. Otherwise with the next upgrade the same happens.
If you are somehow unable to understand, that nobody here is your enemy, but your false statements like "the issue can not be reproduced" cannot be tolerated, sorry. Have a nice day.
 
Last edited:
You must log in or register to reply here.
Top Bottom
Back