Bug 1505959 – Fluentd not connected to Elasticsearch

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1505959 - Fluentd not connected to Elasticsearch

Summary:	Fluentd not connected to Elasticsearch

Status:	CLOSED ERRATA

Aliases:	None

Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Logging (Show other bugs)
Sub Component:
Version:	3.6.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high
Target Milestone:	---
Target Release:	3.6.z
Assigned To:	Noriko Hosoi
QA Contact:	Anping Li
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	1508514 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-10-24 12:31 EDT by Ruben Romero Montes
Modified:	2018-04-12 01:59 EDT (History)
CC List:	6 users (show)

See Also:
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.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-04-12 01:59:07 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:1106	None	None	None	2018-04-12 01:59 EDT

Groups: None (edit)

Description Ruben Romero Montes 2017-10-24 12:31:43 EDT

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 13:32:44 EDT

@Noriko please investigate

Comment 4 Ruben Romero Montes 2017-10-25 05:01:57 EDT

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 11:02:06 EST

Ruben can you please comment if #c6 resolved the issue?

Comment 9 Ruben Romero Montes 2018-02-02 03:49:56 EST

(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 15:55:13 EST

*** Bug 1508514 has been marked as a duplicate of this bug. ***

Comment 12 Anping Li 2018-02-25 01:48:47 EST

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 01:59:07 EDT

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.