You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Since this Graylog Helm chart does not support v5.0.0 yet, we deployed it alongside MongoDB 5.0.0 and OpenSearch 2.0.1 by overriding the image tag.
The cluster comes up online and we are able to log in to Graylog. The System > Overview also mentions that the cluster state is green. But as soon as we add an input to Graylog, and send a message, the pod logs throw indexing exceptions.
Caught exception during bulk indexing: ElasticsearchException{message=ElasticsearchException[An error occurred: ]; nested: IOException[Unable to parse response body for Response{requestLine=POST /_bulk?timeout=1m HTTP/1.1, host=http://opensearch-cluster-master:9200, response=HTTP/1.1 200 OK}]; nested: NullPointerException;, errorDetails=[]}, retrying ( attempt #23). - {}
Describe the bug
Since this Graylog Helm chart does not support v5.0.0 yet, we deployed it alongside MongoDB 5.0.0 and OpenSearch 2.0.1 by overriding the image tag.
The cluster comes up online and we are able to log in to Graylog. The System > Overview also mentions that the cluster state is green. But as soon as we add an input to Graylog, and send a message, the pod logs throw indexing exceptions.
Version of Helm and Kubernetes:
Helm Version:
Kubernetes Version:
Which version of the chart: 2.2.0
What happened: Messages were not being indexed and throwing exceptions in the pod logs.
What you expected to happen: Messages should be displayed in the Graylog homepage
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know:
A longer investigation has been added as a bug in the Graylog github issue
Graylog2/graylog2-server#14236
The text was updated successfully, but these errors were encountered: