[SOLVED] Backups job works on manual launch but never starts automatically

daragon-aptatech

New Member
Jan 6, 2025
4
1
1
Hey !

I have set up a PBS, a daily backup job (which is supposed to run at 3 AM) and could start it manually without any error.
Yet, when it's 3AM, nothing happens. Nothing at all. No error, no logs, nothing. And of course, no backup either.
I checked the `/etc/pve/jobs.cfg` and it seems to me that it is well configured :
vzdump: backup-849d6ecf-fec9
schedule 03:00
enabled 1
mailnotification failure
mailto myemail@email.com
mode snapshot
node 000prxmox01l
notes-template {{guestname}}
prune-backups keep-last=5,keep-monthly=1
storage backups
vmid 100,102,103,104,107,108,109,110,111,115,116,117,119,120,121,200,201,202
The `pvescheduler status` command shows me a `running`, as well as `systemctl status pvescheduler.service` tells me it is active and enabled.
No logs in `journalctl -fu pvescheduler` (just the restart I asked).
pveversion says : `pve-manager/8.1.5/60e01c6ac2325b3f (running kernel: 6.5.13-3-pve)`

I'm running out of ideas...

Do you have anything in mind ?

Thanks in advance !
 
Do you have anything in mind ?
Every backup job generates a "Task Log"-entry, which can be found at the bottom of the browser window. Post the full content of that one....
 
The backup job from Jan 03 is the manual one I started...
Can you find one which is not "OK"? None? (Yes, you stated it does not do that. Just looking for explicit confirmation...)

And just to be sure you're aware of this: a double-click will open a dialog containing details...
 
Yeah, no task is even started, so there's no task with any error... Same in the logs, nothing about a backup job being started...
The only errors I have are about certificates renewing, a few weeks ago, but it's off topic as I have changed my certification method (and it's all working well).
I've set up the job on January the 3rd, and tested with a manual start which is maked as OK (and I do find the backups on my PBS).
That's why I'm a bit lost...
 
pveversion says : `pve-manager/8.1.5/60e01c6ac2325b3f (running kernel: 6.5.13-3-pve)`

To not chase already fixed bugs, I would suggest to update your (whole) environment first, reboot it afterwards and then look further, if still needed at all...
 
  • Like
Reactions: UdoB