summaryrefslogtreecommitdiff
path: root/src/journal-remote
diff options
context:
space:
mode:
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-05-31 12:11:48 +0200
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>2021-05-31 19:29:07 +0200
commit23b8aa648d1d8cb1209ddd521989aa47f9344f68 (patch)
tree46adb1abc388ddf415dc0152190f16b21af160a8 /src/journal-remote
parenta88f9dbae2cbd2af6016e7f4dab5b7a0771491c6 (diff)
downloadsystemd-23b8aa648d1d8cb1209ddd521989aa47f9344f68.tar.gz
journal-remote: downgrade messages about input data to warnings
Those are unexpected, so a user-visible message seems appropriate. But they are not our errors, and to some extent we can recover from them, so "warning" seems more appropriate than "error".
Diffstat (limited to 'src/journal-remote')
-rw-r--r--src/journal-remote/journal-remote-parse.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/journal-remote/journal-remote-parse.c b/src/journal-remote/journal-remote-parse.c
index 7bc349c304..2ece329251 100644
--- a/src/journal-remote/journal-remote-parse.c
+++ b/src/journal-remote/journal-remote-parse.c
@@ -74,7 +74,7 @@ int process_source(RemoteSource *source, bool compress, bool seal) {
&source->importer.boot_id,
compress, seal);
if (r == -EBADMSG) {
- log_error_errno(r, "Entry is invalid, ignoring.");
+ log_warning_errno(r, "Entry is invalid, ignoring.");
r = 0;
} else if (r < 0)
log_error_errno(r, "Failed to write entry of %zu bytes: %m",