Schedule jobs fail, but running manually they have no problems

Bradm

New Member
May 21, 2025
1
0
1
Trying to figure out why schedule backup jobs fail. 1 pve server, and 1 pbs server, the pbs server is a vm on a nas (plenty of ram and cpu).

the pve error is this
"
INFO: notified via target `mail-to-root`
TASK ERROR: could not activate storage 'pbs': pbs: error fetching datastores - 500 Can't connect to 192.168.10.19:8007 (Connection timed out)"

the obvious answer is a timeout, but doesn't make since, as it's on a 10gb switch, local. If I launch the backups schedule manually, they finish without errors.
the schedule job runs as midnight.
No other backups, no other servers, simple setup.
The only thing that looks odd is the is the storage weekly review, like it's dropping the connection and then comes back.

2025-05-21_09h01_22.png
pbs is 3.41, no subscription fully updated
pve is 8.4.1, no subscription, fully updated.
 
TASK ERROR: could not activate storage 'pbs': pbs: error fetching datastores - 500 Can't connect to 192.168.10.19:8007 (Connection timed out)"
Looks like PVE fails to communicate with the PBS at some point. And given you showed the disconnects in the storage summary, the first guess would be either duplicate IPs or the VM/NAS not being reachable. Check your network and explore the logs on your NAS and systemd journal on the PBS VM for errors.