From: Gabriel Goller <g.goller@proxmox.com>
To: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] [PATCH proxmox 1/2] worker_task: always print the result message to the syslog
Date: Wed, 3 Sep 2025 16:13:45 +0200 [thread overview]
Message-ID: <20250903141349.268228-2-g.goller@proxmox.com> (raw)
In-Reply-To: <20250903141349.268228-1-g.goller@proxmox.com>
When a worker-task ends it prints a result line. This line is written
directly to the tasklog file, because we want to bypass tracing (to
avoid this line getting filtered). Force this line into the syslog as
well by always printing it to stderr, which will end up in syslog. This
means that regardless of the task's result (failure or success) or the
tracing filtering, the last line will always be printed to syslog.
Suggested-by: Friedrich Weber <f.weber@proxmox.com>
Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
---
proxmox-rest-server/src/worker_task.rs | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/proxmox-rest-server/src/worker_task.rs b/proxmox-rest-server/src/worker_task.rs
index a3a65add5ce8..6840938bdb2a 100644
--- a/proxmox-rest-server/src/worker_task.rs
+++ b/proxmox-rest-server/src/worker_task.rs
@@ -1026,9 +1026,7 @@ impl WorkerTask {
match LogContext::current() {
Some(context) => {
context.log_unfiltered(&state.result_text());
- if result.is_err() {
- eprintln!("{}", &state.result_text());
- }
+ eprintln!("{}", &state.result_text());
}
None => error!("error writing task result to the tasklog"),
}
--
2.47.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2025-09-03 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 14:13 [pbs-devel] [PATCH proxmox{, -backup} 0/3] Always print workertask start and end logs to syslog Gabriel Goller
2025-09-03 14:13 ` Gabriel Goller [this message]
2025-09-03 14:13 ` [pbs-devel] [PATCH proxmox 2/2] worker_task: print worker starting message and upid Gabriel Goller
2025-09-03 14:13 ` [pbs-devel] [PATCH proxmox-backup 1/1] prune: add upid to workertask log_result function Gabriel Goller
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=20250903141349.268228-2-g.goller@proxmox.com \
--to=g.goller@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