Repository navigation
Replies: 1 comment
|
What you're describing is intended behavior, not a bug. Everyone would like a program shaped around their own needs, and I'm trying to accommodate that as much as I can, but within certain boundaries. 99% of people never check for updates and never update. Every ProxSave release brings improvements and bug fixes, so keeping it up to date always matters. We all know how important a backup is, and we want to deliver the highest possible quality and reliability, which means frequent releases. You're treating warnings as backup problems, and that's not accurate. If something went wrong with a backup, you would get an error, not a warning. A warning can come from an available update, or from copying the backup to secondary paths. An update could potentially contain critical fixes, so it's important that it gets flagged clearly and unambiguously. The Healthchecks integration lets you filter this and tailor notifications to your own needs. When running the daemon without Healthchecks, you should check not only the result reported in the email but also that the email actually arrives. If the daemon or your server ran into a problem, no notification would be sent at all. With Healthchecks, this gap is covered too. In short, a warning is a heads-up: it means the main backup completed successfully but something deserves your attention. An error means the backup failed. |
Uh oh!
There was an error while loading. Please reload this page.
ProxSave runs the nightly configuration backup on our Proxmox VE host in daemon mode. The report goes out by email. Healthchecks is disabled.
#334 was fixed in v0.42.1 for the Healthchecks result. The same case still exists for the backup report and the exit code when Healthchecks is not used.
What happens:
WARNING, the warning count is 1, and the run exits with code 1.Report from 2026-10-31:
A new release is not a backup problem. The report answers one question: is the backup good. When every release turns the report yellow, WARNING stops meaning "check the backup". People learn to ignore it, and a real warning gets lost in the noise.
We update on purpose. We read the release notes for the whole version range, then plan the change. A new release does not change that plan, so it should not change the backup status.
Request:
UPDATE_NOTICE=info|warning|off.Environment: ProxSave v0.44.0, Proxmox VE 9.2 on Debian 13,
proxsave-daemon, email notification,HEALTHCHECK_ENABLED=false.All reactions