Skip to content

New version notice turns a successful backup report into WARNING and exit 1 (Healthchecks disabled) #346

Closed

Description

@brjppru

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:

  • The backup completes. All files are in the archive. Both copies are written. There are no errors.
  • A newer ProxSave release is available.
  • The report title becomes WARNING, the warning count is 1, and the run exits with code 1.

Report from 2026-10-31:

⚠️ DUAL BACKUP REPORT - WARNING
  Local:     19/- backups (679.10 GB free)
  Secondary: 19/- backups (3.38 TB free)
  Included Files: 1044
  Missing Files: 0
  Errors: 0
  Warnings: 1
  - [WARNING] New ProxSave version 0.45.0 (current 0.44.0). (count: 1)
Exit Code: 1

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:

  1. Base the report status, the warning count and the exit code only on the backup run.
  2. Show an available update as an info line in the report, not as a warning. A separate notice is also fine.
  3. Optional: a setting for this, for example UPDATE_NOTICE=info|warning|off.

Environment: ProxSave v0.44.0, Proxmox VE 9.2 on Debian 13, proxsave-daemon, email notification, HEALTHCHECK_ENABLED=false.

Activity

  1. tis24dev commented on Oct 31, 2026

    @tis24dev
    Owner

    Hi, thanks for your reply.
    Let's move this discussion to the forum so we can explore it further.

  2. Repository owner locked and limited conversation to collaborators on Oct 31, 2026
  3. converted this issue into a discussion #348 on Oct 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions