From e59a0edc49eef39a9b50a56f1edbbce6be1e3ff8 Mon Sep 17 00:00:00 2001 From: Otto Moerbeek Date: Tue, 24 Jan 2023 16:52:11 +0100 Subject: [PATCH] rec: do not use "message" as key, it has a special meaning to systemd-journal Fixes #12466 A more fundamental approach would be to make sure to not use keys that have special meaning to systemd-journal in the structured logging backend code. --- pdns/recursordist/secpoll-recursor.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pdns/recursordist/secpoll-recursor.cc b/pdns/recursordist/secpoll-recursor.cc index 91774af85c..0c8d7b869e 100644 --- a/pdns/recursordist/secpoll-recursor.cc +++ b/pdns/recursordist/secpoll-recursor.cc @@ -85,7 +85,7 @@ void doSecPoll(time_t* last_secpoll, Logr::log_t log) g_security_message = security_message; - auto rlog = vlog->withValues("message", Logging::Loggable(g_security_message), "status", Logging::Loggable(security_status)); + auto rlog = vlog->withValues("securitymessage", Logging::Loggable(g_security_message), "status", Logging::Loggable(security_status)); if (g_security_status != 1 && security_status == 1) { SLOG(g_log << Logger::Warning << "Polled security status of version " << pkgv << ", no known issues reported: " << g_security_message << endl, rlog->info(Logr::Notice, "Polled security status of version, no known issues reported")); -- 2.47.2