Description of problem: The fluentd couldn't forward logs to remote rsyslog server. Both in method rsyslog and rsyslog_buffered. Logs can be sent to my rsyslog server from rsyslog client. Version-Release number of selected component (if applicable): image: quay.io/openshift/origin-logging-fluentd:latest imageID: quay.io/openshift/origin-logging-fluentd@sha256:6e42d1047fb3c9cbf2e6e0723f071112ec8cc33b9835cbbc6efb65a96848e7d6 How reproducible: Always Steps to Reproduce: 1. Workaround to OLM #create catalogsource pod. echo 'apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: qe-app-registry namespace: openshift-marketplace spec: sourceType: grpc image: docker.io/anli/csc:upstream' | oc create -f - 2. Deploy cluster-logging. note: subscript to qe-app-registry 3. Set clusterlogging to unmanged status 4. Create rsyslog server on same cluster. 4.1. https://github.com/openshift-qe/v3-testfiles/blob/master/logging/rsyslogserver/01_createsa.sh 4.2. https://github.com/openshift-qe/v3-testfiles/blob/master/logging/rsyslogserver/02_creatersyslogserver.sh 5. Conifure fluentd to send logs to rsyslog server 5.a https://github.com/openshift-qe/v3-testfiles/blob/master/logging/rsyslogserver/03_out_buffer_rsyslog_updateds.sh 5.b https://github.com/openshift-qe/v3-testfiles/blob/master/logging/rsyslogserver/03_out_rsyslog_updateds.sh 6. check the output on rsyslog server Actual results: No output in the rsyslog server Expected results: Additional info:
Created attachment 1658204 [details] configuration and Logs when use out_rsyslog
Created attachment 1658205 [details] configuration and Logs when use out_rsyslog_bufferred
This is unrelated, at least initially, to ipv6. Logforwarding changes clobbers legacy rsyslog
Anping -- The two files you attached are identical. Did you post the syslog_buffered file twice? Michael
Yes, The configuration and Logs when use out_rsyslog is wrong. Please ignore it.
Verified on quay.io/openshift/origin-cluster-logging-operator:latest on IPv6 Verified on openshift/ose-cluster-logging-operator:v4.4.0
*** Bug 1812918 has been marked as a duplicate of this bug. ***
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:0581