Maybe it is similar to this report? Rebooting the node resolved it but it's still unclear what caused it.
Hi,
If you haven't rebooted yet, can you post the output of
Please also post the output of
did you modify the job before it started happening? Was it a newly created job? Do you have a cluster or is this a stand-alone node?
If you haven't rebooted yet, can you post the output of
ps aux | grep pvescheduler?Please also post the output of
pveversion -v and part of /var/log/syslog around the time the issue started happening.
I created a standard backup job each then changed the time from 21:00 to 18:00 and got mon ...fri 18:00. This is a standalone node.
root@prox3 ~ # ps aux | grep pvescheduler
root 1558 0.0 0.0 329404 99116 ? Ss Aug28 0:19 pvescheduler
root 1463053 0.0 0.0 6180 728 pts/0 S+ 10:01 0:00 grep pvescheduler
But I returned again to the standard task and the problem was gone.
proxmox-ve: 7.2-1 (running kernel: 5.15.39-4-pve)
pve-manager: 7.2-7 (running version: 7.2-7/d0dd0e85)
pve-kernel-5.15: 7.2-9
pve-kernel-helper: 7.2-9
pve-kernel-5.15.39-4-pve: 5.15.39-4
ceph-fuse: 14.2.21-1
corosync: 3.1.5-pve2
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx3
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-8
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.5-1
proxmox-backup-file-restore: 2.2.5-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-5
pve-firmware: 3.5-1
pve-ha-manager: 3.4.0
pve-i18n: 2.7-2
pve-qemu-kvm: 7.0.0-2
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/var/log/syslog
There is nothing in the logs related to the backup.
root@prox3 ~ # cat /var/lib/pve-manager/jobs/vzdump-backup-ea1da398-ddf2.json
{"state":"stopped","upid":"UPID:prox3:00074AEB:02550BD8:63111D52:vzdump::root@pam:","msg":"OK","updated":1662153427}