Bug 1652407
| Summary: | Getting "Kibana returning Courier Fetch Error" while accessing kibana | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Miheer Salunke <misalunk> |
| Component: | Logging | Assignee: | Jeff Cantrill <jcantril> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Anping Li <anli> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 3.9.0 | CC: | aos-bugs, jcantril, rkant, rkshirsa, rmeggins, vcorrea |
| Target Milestone: | --- | ||
| Target Release: | 3.9.z | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-02-20 14:29:29 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: | |||
In #c4 we did ask for: > [2018-11-03 00:03:12,478][WARN ][rest.suppressed ] path: /_bulk, > params: {} > com.fasterxml.jackson.core.JsonParseException: Invalid UTF-8 start byte 0x92 > at [Source: [B@ffa8004; line: 1, column: 132] > at > com.fasterxml.jackson.core.JsonParser._constructError(JsonParser.java:1702) > > I can only imagine this is coming from either the ES nodes trying to seed itself or the multi-tenant plugin attempting to read/write the ACL documents and there being an issue. We would require the entire stack trace to know the source. Also, are they able to get ANY requests through via Kibana? Maybe the seeding failed. You could try to reseed the permissions: oc exec -c elasticsearch $pod -- es_seed_acl