Bug 1800809 - Could not forward logs to rsyslog server
Summary: Could not forward logs to rsyslog server
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 4.3.0
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ---
: 4.3.z
Assignee: Jeff Cantrill
QA Contact: Anping Li
URL:
Whiteboard:
Depends On: 1799024 1812918 1824003
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-02-07 22:09 UTC by Jeff Cantrill
Modified: 2020-04-15 03:04 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1799024
Environment:
Last Closed: 2020-03-24 14:33:06 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift cluster-logging-operator pull 365 0 None closed [release-4.3] Bug 1800809: Enable legacy syslog support 2021-01-12 09:24:45 UTC
Red Hat Knowledge Base (Solution) 4962201 0 None None None 2020-04-03 14:26:49 UTC
Red Hat Product Errata RHBA-2020:0858 0 None None None 2020-03-24 14:33:30 UTC

Comment 3 Anping Li 2020-03-15 10:44:02 UTC
Verified in 4.3.7

Comment 4 Anping Li 2020-03-15 10:49:18 UTC
From 4.3.7, we need use a new method to enable fluentd send logs to external syslog server

1) create a configmap named syslog

echo '<store>
     @type syslog
     remote_syslog rsyslogserver.openshift-logging.svc.cluster.local
     port 514
     hostname $hostname
     remove_tag_prefix tag
     tag_key ident,systemd.u.SYSLOG_IDENTIFIER
     facility local0
     severity info
     use_record true
     payload_key message
</store>' >syslog.conf
oc create configmap syslog --from-file=syslog.conf -n openshift-logging

2) restart fluentd pod
oc delete pod --selector logging-infra=fluentd


For more detail, refer to https://docs.openshift.com/container-platform/4.3/logging/config/cluster-logging-log-forwarding.html.

Comment 6 errata-xmlrpc 2020-03-24 14:33:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0858


Note You need to log in before you can comment on or make changes to this bug.