phantom vzdump job

[alexskysilk]

I have a mystery.

Overnight I got a series of alerts from a cluster (one from each node) that a vzdump job failed with the status of "unable to find vm." I must have left a vzdump task scheduled for it- can remove it without issue, right?

except there is no task listed in backups.

I checked all cron entries- nothing. I did a global grep in etc looking for the vmid- again, nothing.

Where is this job defined and ran? am I losing my mind?

 

[fiona]

Hi,
backup jobs are in /etc/pve/vzdump.cron and since Proxmox VE 7.1 also in /etc/pve/jobs.cfg. If the missing VM's ID really isn't referenced there, please check if there is more than one pvescheduler instance running. If not, see if systemctl reload-or-restart pvescheduler.service helps.

If nothing helps, please post the output of the two mentioned files and pveversion -v.

 

[alexskysilk]

@fiona Thank you for looking into this.

vzdump.cron

# cat /etc/pve/vzdump.cron
# cluster wide vzdump cron schedule
# Automatically generated file - do not edit

PATH="/usr/sbin:/usr/bin:/sbin:/bin"


/etc/pve/jobs.conf does not exist
unit pvescheduler.service does not exist either.

pveversion -v

proxmox-ve: 6.4-1 (running kernel: 5.4.143-1-pve)
pve-manager: 6.4-13 (running version: 6.4-13/9f411e79)
pve-kernel-helper: 6.4-8
pve-kernel-5.4: 6.4-7
pve-kernel-5.4.143-1-pve: 5.4.143-1
pve-kernel-5.4.73-1-pve: 5.4.73-1
pve-kernel-4.15: 5.4-19
pve-kernel-4.15.18-30-pve: 4.15.18-58
ceph: 14.2.22-pve1
ceph-fuse: 14.2.22-pve1
corosync: 3.1.2-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.22-pve1~bpo10+1
libproxmox-acme-perl: 1.1.0
libproxmox-backup-qemu0: 1.1.0-1
libpve-access-control: 6.4-3
libpve-apiclient-perl: 3.1-3
libpve-common-perl: 6.4-4
libpve-guest-common-perl: 3.1-5
libpve-http-server-perl: 3.2-3
libpve-storage-perl: 6.4-1
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4
lxc-pve: 4.0.6-2
lxcfs: 4.0.6-pve1
novnc-pve: 1.1.0-1
openvswitch-switch: 2.12.3-1
proxmox-backup-client: 1.1.13-2
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: 2.6-1
pve-cluster: 6.4-1
pve-container: 3.3-6
pve-docs: 6.4-2
pve-edk2-firmware: 2.20200531-1
pve-firewall: 4.1-4
pve-firmware: 3.3-2
pve-ha-manager: 3.1-1
pve-i18n: 2.3-1
pve-qemu-kvm: 5.2.0-6
pve-xtermjs: 4.7.0-3
qemu-server: 6.4-2
smartmontools: 7.2-pve2
spiceterm: 3.1-1
vncterm: 1.6-2
zfsutils-linux: 2.0.6-pve1~bpo10+1

 

[fiona]

Please note that Proxmox VE 6.x is end-of-life and won't receive any (security) updates anymore. It is highly recommended to upgrade, here is the official guide: https://pve.proxmox.com/wiki/Upgrade_from_6.x_to_7.0

# cat /etc/pve/vzdump.cron
# cluster wide vzdump cron schedule
# Automatically generated file - do not edit

PATH="/usr/sbin:/usr/bin:/sbin:/bin"

So no jobs here. I'd check /var/log/syslog if there are hints around the time the phantom job runs. Is it triggered by cron? If not, I'd check jobs started by systemd timers and other automatic stuff you might have on your system.

/etc/pve/jobs.conf does not exist
unit pvescheduler.service does not exist either.

Yes, as I wrote, they were introduced in Proxmox VE 7.1. Well I guess I didn't explicitly write it for the scheduler..