From: "Michael Köppl" <m.koeppl@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [PATCH proxmox-backup v1 0/2] fix #7400: improve handling of corrupted job statefiles
Date: Tue, 17 Mar 2026 17:07:20 +0100 [thread overview]
Message-ID: <20260317160722.201693-1-m.koeppl@proxmox.com> (raw)
This patch series fixes a problem where an empty or corrupted job state
file (due to I/O error, abrupt shutdown, ...) would cause API endpoints
for listing jobs to return an error, breaking the web UI for users
because they could not view any of their configured jobs of that type.
It would also cause proxmox-backup-proxy to indefinitely skip the jobs
until a user manually triggered it to rewrite the statefile.
1/2 fixes the API layer by catching the load error, logging a warning,
and returning a default JobScheduleStatus. This ensure the API returns
the job list, showing the affected job without its last run status.
2/2 updates the scheduler loop inside the proxy to match the behavior of
a a newly created job, triggering the job at its next internal (which
then rewrites the statefile).
proxmox-backup:
Michael Köppl (2):
fix #7400: api: gracefully handle corrupted job statefiles
fix #7400: proxy: self-heal corrupted job statefiles
src/api2/admin/prune.rs | 17 ++++++++++-------
src/api2/admin/sync.rs | 16 ++++++++++------
src/api2/admin/verify.rs | 17 ++++++++++-------
src/api2/tape/backup.rs | 17 ++++++++++-------
src/bin/proxmox-backup-proxy.rs | 2 +-
5 files changed, 41 insertions(+), 28 deletions(-)
Summary over all repositories:
5 files changed, 41 insertions(+), 28 deletions(-)
--
Generated by murpp 0.9.0
next reply other threads:[~2026-03-17 16:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 16:07 Michael Köppl [this message]
2026-03-17 16:07 ` [PATCH proxmox-backup v1 1/2] fix #7400: api: gracefully handle " Michael Köppl
2026-03-17 16:07 ` [PATCH proxmox-backup v1 2/2] fix #7400: proxy: self-heal " Michael Köppl
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260317160722.201693-1-m.koeppl@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox