[SOLVED] Backup of VM crashing VM on random days

Crakila

Member
Oct 5, 2018
4
0
21
32
Ireland
Hey everyone.

I have a VM on my Proxmox that is crashing due to backups.
Specifically and only VM 106 that seems to crash.

It seems to be out of memory but can someone confirm if this is RAM or Storage related? and can someone confirm if OOM is on the VM side or the Proxmox side?
It _shouldn't_ be storage related because the backup is going to storage which appears to have plenty of space (Using 1.2TB out of 1.7TB total)

Config
Code:
#Owner%3A Neil
#IP%3A 136.243.186.150 - hosting.exodondesign.com
boot: dcn
bootdisk: scsi0
cores: 4
ide2: none,media=cdrom
memory: 10240
name: Neil
net0: virtio=5E:9B:D7:02:E9:1B,bridge=vmbr1
numa: 0
ostype: l26
scsi0: storage:106/vm-106-disk-0.qcow2,cache=writeback,size=128G
scsihw: virtio-scsi-pci
smbios1: uuid=4ef14297-0f7d-4b34-a7a1-648998e404b7
sockets: 1
vga: qxl
vmgenid: 02a16512-1adb-4a65-a6b9-2cc22b8e5f50
#qmdump#map:scsi0:drive-scsi0:storage:qcow2:

pveversion -v

Code:
proxmox-ve: 6.3-1 (running kernel: 5.3.18-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.3: 6.1-6
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.3.18-3-pve: 5.3.18-3
pve-kernel-5.3.18-2-pve: 5.3.18-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
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-4
libpve-http-server-perl: 3.1-1
libpve-storage-perl: 6.3-4
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.6-pve1
novnc-pve: 1.1.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-8
pve-xtermjs: 4.7.0-3
qemu-server: 6.3-3
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 0.8.5-pve1

Any help would be appreciated and happy to provide anything else to help try and resolve this.
 

Attachments

  • proxmox_backup_log_27_04_2022.txt
    27 KB · Views: 10
  • proxmox_syslog.txt
    22.3 KB · Views: 13
Last edited:
Your PVE syslogs shows that the KVM process got killed by OOM so sounds like your PVE host is running out of RAM. According to he log you also ran out of swap. You could check the nodes RAM utilization graphs to see if it is near to 100% back then when you ran that backup.
 
  • Like
Reactions: Crakila
Your PVE syslogs shows that the KVM process got killed by OOM so sounds like your PVE host is running out of RAM. According to he log you also ran out of swap. You could check the nodes RAM utilization graphs to see if it is near to 100% back then when you ran that backup.
Yes, it looks like I never considered given the overall PVE host any RAM to do any tasks... Killed one of the other VM's and it's been backing up ok since. Will keep an eye over the next few days to see if it happens again. Thanks :)
 

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!