Invalid UTF-8 start byte in logging stack in OCP 3

Solution Unverified - Updated -

Issue

  • Getting UTF-8 character errors:

    [2018-08-28 22:44:50,914][WARN ][rest.suppressed          ] path: /_bulk, params: {}
    com.fasterxml.jackson.core.JsonParseException: Invalid UTF-8 start byte 0x92
    at [Source: [B@387a6030; line: 1, column: 113]
    at com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1702)
    
  • This causes Fluentd to report a service unavailable when connecting to Elasticsearch in the EFK logging stack

Environment

  • Red Hat OpenShift container Platform
    • 3

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content