Bug 1505959
| Summary: | Fluentd not connected to Elasticsearch | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ruben Romero Montes <rromerom> |
| Component: | Logging | Assignee: | Noriko Hosoi <nhosoi> |
| Status: | CLOSED ERRATA | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.6.0 | CC: | aos-bugs, jcantril, pdwyer, pportant, rmeggins, rromerom |
| Target Milestone: | --- | ||
| Target Release: | 3.6.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| 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 05:59:07 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
@Noriko please investigate If the logging-fluentd:v3.6.173.0.5 images are used the problem is no longer reproducible. Ruben can you please comment if #c6 resolved the issue? (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. *** Bug 1508514 has been marked as a duplicate of this bug. *** Move to verified as no such issue with the image 0.49. Our release image have include the fix. 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 |
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)