From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com, Michal Fox <me@dualfroz.com>
Subject: applied: [PATCH manager] fix #4986: jobs: do not get stuck if the task log is missing
Date: Tue, 6 Oct 2026 14:41:29 +0200 [thread overview]
Message-ID: <179129048526.513195.3926366735136520416.b4-ty@proxmox.com> (raw)
In-Reply-To: <20261003153820.7-1-me@dualfroz.com>
On Sat, 03 Oct 2026 15:38:20 +0000, Michal Fox wrote:
> When the scheduler checks whether the last run of a job has finished,
> it dies if the task log of that run does not exist. The job is then
> skipped with 'could not update job state, skipping - no such task' on
> every iteration, so it never runs again until its state file is
> cleaned up manually.
>
> The task log can be gone, for example after a crash. If the task is
> not running anymore, treat it as stopped with an error status instead,
> so that the job gets scheduled again, like Proxmox Backup Server does
> since commit 48fbce07 ("fix #4895: scheduled jobs: ignore task-log not
> found error").
>
> [...]
Applied, thanks! I switched to using PVE::File::file_exists() for the
existence check and also made the scheduler issue an explicit warning.
[1/1] fix #4986: jobs: do not get stuck if the task log is missing
commit: ac0c87dd37115e3046cbfa5756f2a02fc659e8cd
prev parent reply other threads:[~2026-10-06 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-03 15:38 [PATCH manager] fix #4986: jobs: do not get stuck if the task log is missing Michal Fox
2026-10-06 12:41 ` Fiona Ebner [this message]
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=179129048526.513195.3926366735136520416.b4-ty@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=me@dualfroz.com \
--cc=pve-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