ERROR: Null indexSetId

[montyz (Monty Zukowski)]

I’m running graylog on kubernetes. Recently, possibly after restarting graylog, I see a notification on the streams page:

Loading streams failed with status:
 Error: cannot GET http://a8ba988a526e211e789b50a378a96246-1950688295.us-east-1.elb.amazonaws.com:9000/api/streams (500)

And on graylog I see stacktraces like

2017-05-31 16:28:21,780 ERROR: org.graylog2.shared.rest.exceptionmappers.AnyExceptionClassMapper - Unhandled exception in REST resource
java.lang.NullPointerException: Null indexSetId
	at org.graylog2.rest.resources.streams.responses.$AutoValue_StreamResponse.<init>($AutoValue_StreamResponse.java:90) ~[graylog.jar:?]
	at org.graylog2.rest.resources.streams.responses.AutoValue_StreamResponse.<init>(AutoValue_StreamResponse.java:19) ~[graylog.jar:?]
	at org.graylog2.rest.resources.streams.responses.StreamResponse.create(StreamResponse.java:116) ~[graylog.jar:?]
	at org.graylog2.rest.resources.streams.StreamResource.streamToResponse(StreamResource.java:479) ~[graylog.jar:?]
...

Any ideas of what do do to fix this? Google hasn’t been much help here. I’m running graylog from the docker container, version 2.2.3

Thanks,

Monty

[jan (Jan Doberstein)]

Hej @montyz

is that:

http://a8ba988a526e211e789b50a378a96246-1950688295.us-east-1.elb.amazonaws.com:9000

your configured REST API and can Graylog itself reach this?

[montyz (Monty Zukowski)]

Yes and yes. The funny thing is that is also was fully working. And that url gives a result, http://a8ba988a526e211e789b50a378a96246-1950688295.us-east-1.elb.amazonaws.com:9000/api/streams returns

{"type":"ApiError","message":"Null indexSetId"}