SOLVED! Error "Request to Elasticsearch failed: "Bad Request"" after upgrading ES to 5.5.1

Elastic Stack Elasticsearch
1

Hello,

I'm new in this forum and not very familiar with Elasticsearch and Kibana.
After upgrading our Elasticsearch-system to 5.5.1 I get the following error-message in Kibana when I try to access the "winlogbeat-*"-data:

Request to Elasticsearch failed: "Bad Request"

Error: Request to Elasticsearch failed: "Bad Request"
KbnError@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:83:18295
RequestFailure@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:83:19044
DocSendToEsProvider/</<@https://kibana-test.example.com/bundles/kibana.bundle.js?v=15405:27:23337
processQueue@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:38:23621
scheduleProcessQueue/<@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:38:23888
$RootScopeProvider/this.$get</Scope.prototype.$eval@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:39:4607
$RootScopeProvider/this.$get</Scope.prototype.$digest@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:39:2343
$RootScopeProvider/this.$get</Scope.prototype.$apply@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:39:5026
done@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:37:25016
completeRequest@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:37:28702
createHttpBackend/</xhr.onload@https://kibana-test.example.com/bundles/commons.bundle.js?v=15405:37:29634

But I am able to access the "filebeat-*"-data without any problems.

Can anyone help me, please?

Thank you!

2

Hi

Didi you fix this problem ?

I have the same issue.

Thanks

3

Hi,

I may have the same problem. Has any of you managed to resolve it yet?

4

Hi,

the problem still exists.
I suppose that I have to re-initialize the index of the "winlogbeat"-data due to the fact that my "filebeat"-data does not have this problem.
But before I will do that I hope that an EL-specialist tell me wether this will solve the problem or do more harm.

5

I solved it by deleting (sigh) my kibana index.

6

@ch07077555 Can you describe how you have done this?

THX!

7

Sure, I followed the docs from https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-delete-index.html :slight_smile:

8

Ok... this solved the problem... but deleted the complete data of the index also.

9

Because I need the historical "winlogbeat"-data, I've restored my data from backup and try to solve the problem without deleting the index.
I've refreshed the "winlogbeat"-index also without any success.

Anyone an idea?

10

After upgrading to version 5.5.2 I can access the "winlogbeat"-historical-data.
SOLVED!

11

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.