Project

General

Profile

Bug #47078

cephadm: ForwardToSyslog=yes (aka really huge syslog)

Added by Sebastian Wagner over 3 years ago. Updated almost 2 years ago.

Status:
Need More Info
Priority:
Normal
Assignee:
-
Category:
cephadm (binary)
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

ForwardToSyslog=yes is default in man distros.

Which means, we have a chain here:

container's stdout -> systemd service -> journald -> really huge syslog

Which means every log message of every container ends up in /var/log/syslog or something similar.

The Problem is explained here: https://github.com/DataDog/datadog-agent/issues/1606#issuecomment-382384062

Q: is this still the case?

Is there any other way to disable ForwardToSyslog for our services? If we could find a way to disable this behavior for our
containers, we should be fine.

History

#1 Updated by Sebastian Wagner over 3 years ago

  • Description updated (diff)

#5 Updated by Sebastian Wagner over 3 years ago

  • Status changed from New to In Progress

#6 Updated by Sebastian Wagner over 3 years ago

  • Status changed from In Progress to Need More Info

#7 Updated by Sebastian Wagner about 3 years ago

  • Priority changed from Urgent to Normal

#8 Updated by Sebastian Wagner almost 3 years ago

  • Category set to cephadm (binary)

#9 Updated by Redouane Kachach Elhichou almost 2 years ago

As of today (May 5th 2022), it doesn't seem to be any practical solution to this issue. The only candidate is still journald namespaces but unfortunately this feature is not yet available on modern RHEL distros (AFAIK).

Also available in: Atom PDF