System update error

evanonym0us

New Member
Nov 10, 2021
23
0
1
Did you have finished the broken Upgrade already?

If not, try it with apt --fix-broken install
username@server:~$ sudo apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
 

Neobin

Active Member
Apr 29, 2021
293
91
28
To get an overview of your current state, what's the actual output of apt update && apt full-upgrade and pveversion -v? (Please each in code-tags.)
 

evanonym0us

New Member
Nov 10, 2021
23
0
1
To get an overview of your current state, what's the actual output of apt update && apt full-upgrade and pveversion -v? (Please each in code-tags.)
apt update && apt full-upgrade:
Code:
Get:1 http://security.debian.org/debian-security bullseye-security InRelease [44.1 kB]
Get:2 http://security.debian.org/debian-security bullseye-security/main amd64 Packages [146 kB]
Hit:3 http://ftp.debian.org/debian bullseye InRelease                                   
Get:4 http://ftp.debian.org/debian bullseye-updates InRelease [39.4 kB]
Hit:5 http://download.proxmox.com/debian/pve bullseye InRelease     
Fetched 229 kB in 1s (250 kB/s)       
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

pveversion -v:
Code:
proxmox-ve: 7.2-1 (running kernel: 5.15.35-1-pve)
pve-manager: 7.2-3 (running version: 7.2-3/c743d6c1)
pve-kernel-5.15: 7.2-3
pve-kernel-helper: 7.2-3
pve-kernel-5.13: 7.1-9
pve-kernel-5.4: 6.4-7
pve-kernel-5.15.35-1-pve: 5.15.35-2
pve-kernel-5.15.30-2-pve: 5.15.30-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
pve-kernel-5.4.143-1-pve: 5.4.143-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: 0.8.36+pve1
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.22-pve2
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.2.0-1
libpve-access-control: 7.1-8
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.1-6
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-1
libpve-storage-perl: 7.2-2
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 4.0.12-1
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.1.8-1
proxmox-backup-file-restore: 2.1.8-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.4-10
pve-cluster: 7.2-1
pve-container: 4.2-1
pve-docs: 7.2-2
pve-edk2-firmware: 3.20210831-2
pve-firewall: 4.2-5
pve-firmware: 3.4-2
pve-ha-manager: 3.3-4
pve-i18n: 2.7-1
pve-qemu-kvm: 6.2.0-5
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-2
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.4-pve1
 

evanonym0us

New Member
Nov 10, 2021
23
0
1
I'm sorry for posting again, but I'm still having issues with my installation. Does anyone have any possible solutions?
 

evanonym0us

New Member
Nov 10, 2021
23
0
1
I'm sorry for posting again, but I'm still having issues with my installation. Does anyone have any possible solutions?
The server is randomly shutting down VMs and starting them back up. I have no idea why it's doing this. The web interface is still not loading at all.
 

mijanek

Active Member
Sep 3, 2013
86
6
28
I would suggest, you check all logfiles for issues. Hopefully you didn‘t have deleted any neccessary resources or folders in your var dir.
 

evanonym0us

New Member
Nov 10, 2021
23
0
1
I have an update:
Code:
user@server:~$ sudo systemctl restart pve-cluster
Job for pve-cluster.service failed because the control process exited with error code.
See "systemctl status pve-cluster.service" and "journalctl -xe" for details.
user@server:~$ sudo systemctl status pve-cluster.service
● 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 Fri 2022-05-13 07:49:36 EDT; 18s ago
    Process: 33163 ExecStart=/usr/bin/pmxcfs (code=exited, status=255/EXCEPTION)
        CPU: 9ms

May 13 07:49:36 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 5.
May 13 07:49:36 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
May 13 07:49:36 server systemd[1]: pve-cluster.service: Start request repeated too quickly.
May 13 07:49:36 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 13 07:49:36 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
May 13 07:49:44 server systemd[1]: pve-cluster.service: Start request repeated too quickly.
May 13 07:49:44 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 13 07:49:44 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
 

evanonym0us

New Member
Nov 10, 2021
23
0
1
Code:
May 13 04:32:35 server systemd[1]: Starting The Proxmox VE cluster filesystem...
May 13 04:32:35 server pmxcfs[22541]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:35 server pmxcfs[22541]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:35 server pmxcfs[22541]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:35 server pmxcfs[22541]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:35 server pmxcfs[22541]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:35 server pmxcfs[22541]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:35 server systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 13 04:32:35 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 13 04:32:35 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
May 13 04:32:35 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 1.
May 13 04:32:35 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
May 13 04:32:35 server systemd[1]: Starting The Proxmox VE cluster filesystem...
May 13 04:32:35 server pmxcfs[22545]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:35 server pmxcfs[22545]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:35 server pmxcfs[22545]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:35 server pmxcfs[22545]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:35 server pmxcfs[22545]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:35 server pmxcfs[22545]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:35 server systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 13 04:32:35 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 13 04:32:35 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
May 13 04:32:36 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 2.
May 13 04:32:36 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
May 13 04:32:36 server systemd[1]: Starting The Proxmox VE cluster filesystem...
May 13 04:32:36 server pmxcfs[22550]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:36 server pmxcfs[22550]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:36 server pmxcfs[22550]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:36 server pmxcfs[22550]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:36 server pmxcfs[22550]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:36 server pmxcfs[22550]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:36 server systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 13 04:32:36 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 13 04:32:36 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
May 13 04:32:36 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 3.
May 13 04:32:36 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
May 13 04:32:36 server systemd[1]: Starting The Proxmox VE cluster filesystem...
May 13 04:32:36 server pmxcfs[22551]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:36 server pmxcfs[22551]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:36 server pmxcfs[22551]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:36 server pmxcfs[22551]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:36 server pmxcfs[22551]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:36 server pmxcfs[22551]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:36 server systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
May 13 04:32:36 server systemd[1]: pve-cluster.service: Failed with result 'exit-code'.
May 13 04:32:36 server systemd[1]: Failed to start The Proxmox VE cluster filesystem.
May 13 04:32:36 server systemd[1]: pve-cluster.service: Scheduled restart job, restart counter is at 4.
May 13 04:32:36 server systemd[1]: Stopped The Proxmox VE cluster filesystem.
May 13 04:32:36 server systemd[1]: Starting The Proxmox VE cluster filesystem...
May 13 04:32:36 server pmxcfs[22552]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:36 server pmxcfs[22552]: [database] crit: unable to set WAL mode: disk I/O error#010
May 13 04:32:36 server pmxcfs[22552]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:36 server pmxcfs[22552]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:36 server pmxcfs[22552]: [main] crit: memdb_open failed - unable to open database '/var/lib/pve-cluster/config.db'
May 13 04:32:36 server pmxcfs[22552]: [main] notice: exit proxmox configuration filesystem (-1)
May 13 04:32:36 server systemd[1]: pve-cluster.service: Control process exited, code=exited, status=255/EXCEPTION
 

evanonym0us

New Member
Nov 10, 2021
23
0
1
Code:
Filesystem            Size  Used Avail Use% Mounted on
udev                   48G     0   48G   0% /dev
tmpfs                 9.5G  967M  8.5G  11% /run
/dev/mapper/pve-root   57G   57G     0 100% /
tmpfs                  48G     0   48G   0% /dev/shm
tmpfs                 5.0M     0  5.0M   0% /run/lock
/dev/sdh1             549G  151G  370G  29% /mnt/proxmox4
/dev/sdg1             223G   99G  122G  45% /mnt/proxmox3
/dev/md0              1.1T  153G  963G  14% /mnt/backups
/dev/sda2             511M  324K  511M   1% /boot/efi
/dev/sdf1             559G  449G  107G  81% /mnt/proxmox2
tmpfs                 9.5G     0  9.5G   0% /run/user/1000

I had 20Gb of free space and now it's full again. Something is sucking up space. If I get a bigger SSD can I expand the partition or something?
 

mijanek

Active Member
Sep 3, 2013
86
6
28
There is one think which is wondering me, the screenshot shows me an single node configuration, so why are you starting cluster service? Was you intending to build up cluster?
Bigger spce does not solve your problem, it will just give you more time until it will went full..
I guess some misconfiguration is leading to your problem and flood the logfiles. If you solve this problem, you will don‘t have any space issues.
 

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 your own in 60 seconds.

Buy now!