From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 62CE81FF13C for ; Thu, 16 Apr 2026 15:33:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 199BC66F1; Thu, 16 Apr 2026 15:33:23 +0200 (CEST) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pbs-devel@lists.proxmox.com, =?UTF-8?q?Michael=20K=C3=B6ppl?= Subject: applied-series: [PATCH proxmox-backup v5 0/3] fix #7400: improve handling of corrupted job statefiles Date: Thu, 16 Apr 2026 15:32:46 +0200 Message-ID: <177634635380.646747.8366693398070096157.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260413132000.49889-1-m.koeppl@proxmox.com> References: <20260413132000.49889-1-m.koeppl@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1776346319703 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.052 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: KNTVWPAPPBRCJ36GWZHQAOIH226BXP4Y X-Message-ID-Hash: KNTVWPAPPBRCJ36GWZHQAOIH226BXP4Y X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 13 Apr 2026 15:19:57 +0200, Michael Köppl wrote: > This patch series fixes a problem [0] 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. > > [...] Applied with Chris R-B, thanks! [1/3] api: move statefile loading into compute_schedule_status commit: b4300f7d8fe264237f7c3084e00669286e17b4b0 and the clippy nit folded into this patch [2/3] fix #7400: api: gracefully handle corrupted job statefiles commit: 9d7f1fa6a84b41baceda9654fc3e9bb7dd386d75 [3/3] fix #7400: proxy: self-heal corrupted job statefiles commit: 76b27e7ce395a2c2f7e1c73b18f3cea0c42fdd46 Best regards, -- Fabian Grünbichler