Search results

Thanks! I have metrics from the PVE machines, I'm going to throw this into the mix and see what it's doing. Also going to space out my jobs, and see what that does...

Also the datastore backups_ceph does not exist any more.. I've removed the verify job.. With your question on the "trigger event" this is a good suspect!

It starts out with a backup job at midnight: root@pbs:/var/log# journalctl --since=today Mar 27 00:00:00 pbs proxmox-backup-proxy[111567]: unable to start datastore verification job v-9206d00d-24cb - no such datastore 'backup_ceph' Mar 27 00:00:00 pbs proxmox-backup-proxy[111567]: rotated access...

I've been running into this same thing, pretty much the exact same setup as well.. except, I'm only using S3 for a sync endpoint. I'm running latest 4.1.4. I have monit running in the background, an it picks up that the api is not responding and eventually restarts it.. but a bunch of backups fail.