I cannot logon the web interface, but I can login to server thru SSH.

firewood0188

Member
Mar 23, 2020
14
0
21
44
The server is working fine in serval months. Today, I want to login thru the web interface as usual. But it cannot. I login thru SSH and check the log and see this error message.
1608263519023.png

I search the info in this proxmox and try the following command.

~ systemctl restart pvedaemon.service
~ systemctl restart pveproxy.service

Still no luck.

Type "journalctl -u -pve-cluster"
I got this error.

1608263640264.png

How can I fix it?
 
I have ran into the perhaps the same issue after upgrading Firefox yesterday to 84.0 (from 83.0+build2-0ubuntu0.20.10.1 to 84.0+build3-0ubuntu0.20.10.1) on Ubuntu Groovy.

Logging in via the web UI results in the form getting stuck with "Please wait...":

1608280542382.png

Checking in the dev tools of browser, I can see that no request is made when I submit the form. From the console of the browser, I can see this error logged when I submit the form though:

1608280621281.png

Running latest Proxmox packages (the server was also rebooted to make sure):

Code:
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: 3.0.4-pve1
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: 1.16-pve1
libproxmox-acme-perl: 1.0.7
libproxmox-backup-qemu0: 1.0.2-1
libpve-access-control: 6.1-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.3-2
libpve-guest-common-perl: 3.1-3
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-3
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.3-1
lxcfs: 4.0.3-pve3
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.0-1
proxmox-backup-client: 1.0.6-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.4-3
pve-cluster: 6.2-1
pve-container: 3.3-2
pve-docs: 6.3-1
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-3
pve-firmware: 3.1-3
pve-ha-manager: 3.1-1
pve-i18n: 2.2-2
pve-qemu-kvm: 5.1.0-7
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-2
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

Tried disabling all extensions in browser with no difference. It doesn't seem to be a server side issue, no errors are logged. I cleared the local data in my browser as well with no success.

It's working fine for me in Chrome though.
 
Also verified the same issue occurs for older Proxmox releases, I tested various releases from 5.2 upwards. The only difference is the line numbers of the file causing the error change. From 5.2:

1608281733709.png
 
Can you please also try to open a Private Browser by click Ctrl+Shift+P and try to login to Proxmox VE?
 
@firewood0188
Please provide also the output of commands cat /etc/hosts and systemctl status pvedaemon.service


@6675636b
I guess the issue from one of the plugins on your Firefox browser!! or clearing the cache?
 
Hi,

Did you reboot your node after upgrading?

Still the same output of systemctl status pvedaemon.service command?
 
hi again,

Could you try the following commands:

Bash:
systemctl stop pve-cluster
rm -f /var/lib/pve-cluster/.pmxcfs.lockfile
systemctl start pve-cluster

If that not help post the output of systemctl status pvedaemon pve-cluster pveproxy
 
Can you check your config.db

SQL:
sqlite3 /var/lib/pve-cluster/config.db
analyze;
PRAGMA integrity_check;

if it's ok should print OK in SQLite, also try to restart pve-cluster and post the output of journalctl.

Bash:
systemctl reset-failed pve-cluster
systemctl restart pve-cluster
journalctl -u pve-cluster --since "5min ago"

Hope that helps.
 
After tying SQL command, the error came out.
1608780276724.png


After restart pve-cluster, the journalctl is that

1608780373886.png


There is some error in the database.
 
Also verified the same issue occurs for older Proxmox releases, I tested various releases from 5.2 upwards. The only difference is the line numbers of the file causing the error change. From 5.2:

View attachment 22104

As a follow up from this problem, it is related to this bug report:

https://bugzilla.mozilla.org/show_bug.cgi?id=1683299

As a work around, go to "about:config" and raise the limit for "dom.storage.default_quota" (I doubled it from the default 5mb to 10mb).
 
After tying SQL command, the error came out.
View attachment 22296


After restart pve-cluster, the journalctl is that

View attachment 22297


There is some error in the database.
The pmxcfs database is malformed!
You will have to restore it from a backup!
If you do not have a backup your last resort will be trying recover the database (e.g. https://stackoverflow.com/questions/18259692/how-to-recover-a-corrupt-sqlite3-database/57872238#57872238)
Anyway make sure to do this without the pve-cluster.service running
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!