Proxmox web interface timeout 30 min after server boots

w41g87

New Member
Dec 25, 2019
1
0
1
26
Visiting web interface 30 min after server boots shows server times out.
Rebooting the server enables me to access web interface temporarily, and after 30 min the problem comes back.
I first checked the pve-cluster service

Code:
root@pve:/mnt# systemctl status pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-12-25 14:55:23 EST; 52min ago
  Process: 1375 ExecStart=/usr/bin/pmxcfs (code=exited, status=0/SUCCESS)
 Main PID: 1383 (pmxcfs)
    Tasks: 7 (limit: 4915)
   Memory: 49.0M
   CGroup: /system.slice/pve-cluster.service
           └─1383 /usr/bin/pmxcfs

Dec 25 14:55:22 pve systemd[1]: Starting The Proxmox VE cluster filesystem...
Dec 25 14:55:23 pve systemd[1]: Started The Proxmox VE cluster filesystem.
Dec 25 15:38:47 pve pmxcfs[1383]: [database] crit: commit transaction failed: disk I/O error#010
Dec 25 15:38:47 pve pmxcfs[1383]: [database] crit: rollback transaction failed: cannot rollback - no transaction is active#010

Restarting pve-cluster service simply fails and when I checked the service status again it shows:

Code:
root@pve:/mnt# systemctl status pve-cluster
● pve-cluster.service - The Proxmox VE cluster filesystem
   Loaded: loaded (/lib/systemd/system/pve-cluster.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2019-12-25 15:50:39 EST; 1min 31s ago
  Process: 11006 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)

Dec 25 15:50:39 pve systemd[1]: pve-cluster.service: Service RestartSec=100ms expired, scheduling restart.
Dec 25 15:50:39 pve systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
Dec 25 15:50:39 pve systemd[1]: Stopped The Proxmox VE cluster filesystem.
Dec 25 15:50:39 pve systemd[1]: pve-cluster.service: Start request repeated too quickly.
Dec 25 15:50:39 pve systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
Dec 25 15:50:39 pve systemd[1]: Failed to start The Proxmox VE cluster filesystem.
 
I had similar problem too. In my case this was because one of the virtual machines periodically tried to get IP-address from DHCP via WiFi. WiFi router rejected those requests but eventually gave up and assigned IP-address to virtual machine therefore host-proxmox lost the connection. Try to shutdown virtual machines and watch for a while. Or temportary disable bridges at /etc/network/interfaces.
 

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!