Bug 1505959 - Fluentd not connected to Elasticsearch
Summary: Fluentd not connected to Elasticsearch
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Logging
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.6.z
Assignee: Noriko Hosoi
QA Contact: Anping Li
URL:
Whiteboard:
: 1508514 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-24 16:31 UTC by Ruben Romero Montes
Modified: 2020-12-14 10:38 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The fluentd input plugins treat the logs as ASCII-8BIT by default. Then, they are converted to UTF-8 to forward to ElasticSearch, where UndefinedConversionError is rarely observed. With this patch, if the environment variable ENABLE_UTF8_FILTER is set to 'true', the incoming logs are treated as UTF-8 and it eliminates the chance of the conversion error.
Clone Of:
Environment:
Last Closed: 2018-04-12 05:59:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1106 0 None None None 2018-04-12 05:59:32 UTC

Description Ruben Romero Montes 2017-10-24 16:31:43 UTC
Description of problem:
Some fluentd pods are not sending logs to fluentd. Using trace loglevel it has been observed that those pods does not show the following message:

 2017-10-24 14:22:26 +0200 [info]: Connection opened to Elasticsearch cluster => {:host=>"logging-es", :port=>9200, :scheme=>"https", :user=>"fluentd", :password=>"obfuscated"}

Version-Release number of selected component (if applicable):
Dockerfile info: /root/buildinfo/Dockerfile-openshift3-logging-fluentd-v3.6.173.0.21-17
"build-date"="2017-09-01T16:15:36.862753"

How reproducible:
Only on customer environment

Actual results:
Some fluentd pods are not sending logs to ES

Expected results:
All fluentd pods should forward logs to ES

Additional info:
See logging-dump output attached (private attachment)

Comment 2 Jeff Cantrill 2017-10-24 17:32:44 UTC
@Noriko please investigate

Comment 4 Ruben Romero Montes 2017-10-25 09:01:57 UTC
If the logging-fluentd:v3.6.173.0.5 images are used the problem is no longer reproducible.

Comment 8 Jeff Cantrill 2018-01-08 16:02:06 UTC
Ruben can you please comment if #c6 resolved the issue?

Comment 9 Ruben Romero Montes 2018-02-02 08:49:56 UTC
(In reply to Jeff Cantrill from comment #8)
> Ruben can you please comment if #c6 resolved the issue?

Using the 0.49 images solved the issue and the customers were suggested to do so. 

P.S. Sorry for the delay. I missed the updates.

Comment 11 Noriko Hosoi 2018-02-23 20:55:13 UTC
*** Bug 1508514 has been marked as a duplicate of this bug. ***

Comment 12 Anping Li 2018-02-25 06:48:47 UTC
Move to verified as no such issue with the image 0.49. Our release image have include the fix.

Comment 15 errata-xmlrpc 2018-04-12 05:59:07 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-2018:1106


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