PVE GUI Summary loads reports drops
- Thread starter mokaz
- Start date
It looks like the RRD might have some trouble writing. Do you see any abnormalities in the syslogs?
Additionally, please post the current version you are running
Additionally, please post the current version you are running
pveversion -v.Hi there, FYI
Aside of some mounted remote storage appearing / disappearing due to underneath updates/reboots nothing alarming in the syslogs..
I think though it's due the above mention, disappearing mount points, though why?
Aside of some mounted remote storage appearing / disappearing due to underneath updates/reboots nothing alarming in the syslogs..
I think though it's due the above mention, disappearing mount points, though why?
Code:
vanderleyen@PVE:~# pveversion -v
proxmox-ve: 7.2-1 (running kernel: 5.15.60-1-pve)
pve-manager: 7.2-11 (running version: 7.2-11/b76d3178)
pve-kernel-helper: 7.2-12
pve-kernel-5.15: 7.2-11
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.60-1-pve: 5.15.60-1
pve-kernel-5.15.39-3-pve: 5.15.39-3
pve-kernel-5.15.39-1-pve: 5.15.39-1
pve-kernel-5.15.35-2-pve: 5.15.35-5
pve-kernel-5.15.35-1-pve: 5.15.35-3
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-4-pve: 5.13.19-9
pve-kernel-5.13.19-3-pve: 5.13.19-7
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 15.2.15-pve1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx3
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve1
libproxmox-acme-perl: 1.4.2
libproxmox-backup-qemu0: 1.3.1-1
libpve-access-control: 7.2-4
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.2-2
libpve-guest-common-perl: 4.1-2
libpve-http-server-perl: 4.1-3
libpve-storage-perl: 7.2-9
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.0-3
lxcfs: 4.0.12-pve1
novnc-pve: 1.3.0-3
proxmox-backup-client: 2.2.6-1
proxmox-backup-file-restore: 2.2.6-1
proxmox-mini-journalreader: 1.3-1
proxmox-widget-toolkit: 3.5.1
pve-cluster: 7.2-2
pve-container: 4.2-2
pve-docs: 7.2-2
pve-edk2-firmware: 3.20220526-1
pve-firewall: 4.2-6
pve-firmware: 3.5-3
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-3
pve-xtermjs: 4.16.0-1
qemu-server: 7.2-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.7.1~bpo11+1
vncterm: 1.7-1
zfsutils-linux: 2.1.5-pve1The rrd data should be written to a file in
/var. If you did not set this folder to be replaced by a mounted partition I don't see a strong reason why they should be connected. It is very peculiar, though.What kind of storages are you experiencing this "disappearing mount points" with, are you using some kind of network storage? Do you still see the storages/partitions in
lsblk? What happens if you try to mount them again, what is the output of mount -a?Hi there Daniel,
Yes all the local storage on the PVE node is "always" there.
Every VMs are running from local SSD backend.
/var is on local storage (not subject to issues/outage at all)
The storage that was dissappearing at the time the SS has been taken were PBS and/or NFS mounts.
Mounts used exclusively for backup purposes and dissapearing while changing underneath network properties etc..
I suspect this to be related somehow though. Now that everything is back in shape, the GUI graphics are all aligned.
Thanks,
cheers,
m.
Yes all the local storage on the PVE node is "always" there.
Every VMs are running from local SSD backend.
/var is on local storage (not subject to issues/outage at all)
The storage that was dissappearing at the time the SS has been taken were PBS and/or NFS mounts.
Mounts used exclusively for backup purposes and dissapearing while changing underneath network properties etc..
I suspect this to be related somehow though. Now that everything is back in shape, the GUI graphics are all aligned.
Thanks,
cheers,
m.