Error: pve 6.2 - unable to read tail

[Ubanna]

Hi everyone, I'm a newbie and would appreciate your help. I was trying to create a VM when the server crashed and had this error log.

Error: unable to read tail(got 0byte)

We had to force reboot the server which killed a lot of processes. The VM we were trying to create had heavy specs which one with similar spec already exists. We are not sure what exactly caused the crashed. But we are trying to investigate. Also, we set proxmox to auto-upgrade.

What we are trying to find out is what triggered the crash. Could it be insufficient system resource or auto-upgrade? And the logs has really not been helpful or perhaps we aren't looking in the right places.

 

[Moayad]

Hi,

Please provide your Proxmox version pveversion -v

 

[Ubanna]

Proxmox VE 6.2-11

Thanks

 

[Moayad]

Please post the full output to help better

 

[Ubanna]

proxmox-ve: 6.2-1 (running kernel: 5.4.55-1-pve)
pve-manager: 6.2-11 (running version: 6.2-11/22fb4983)
pve-kernel-5.4: 6.2-5
pve-kernel-helper: 6.2-5
pve-kernel-5.4.55-1-pve: 5.4.55-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.4
libpve-access-control: 6.1-2
libpve-apiclient-perl: 3.0-3
libpve-common-perl: 6.2-1
libpve-guest-common-perl: 3.1-2
libpve-http-server-perl: 3.0-6
libpve-storage-perl: 6.2-6
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
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.2-10
pve-cluster: 6.1-8
pve-container: 3.1-13
pve-docs: 6.2-5
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-2
pve-firmware: 3.1-2
pve-ha-manager: 3.0-9
pve-i18n: 2.1-3
pve-qemu-kvm: 5.0.0-13
pve-xtermjs: 4.7.0-2
qemu-server: 6.2-14
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.4-pve1

 

[Moayad]

Please consider upgrading your host to the latest version by doing apt update && apt dist-upgrade, then check if the error occurs again