After the upgrade to Graylog 4.3.3 from the previous Graylog 4.3.x release, I’m now seeing an error when clicking “Edit Index Set” from within the Index Set Overview.
System / Indices > Indices > Default > Edit Index Set.
t.state is null
Stack Trace:
tKuYkRBm/f/T<@https://graylog.company.com/assets/6e13caea-6379.0a4a09e420f2da7e1b11.js:1:2579
value@https://graylog.company.com/assets/6e13caea-6379.0a4a09e420f2da7e1b11.js:1:4003
Ha@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:804869
Ra@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:804664
Ls@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:840162
Mc@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:831638
mc@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:831561
sc@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:828591
4448/Qo/<@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:780339
4203/exports.unstable_runWithPriority@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:855639
Ko@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:780048
Qo@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:780286
Go@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:780219
nc@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:825376
enqueueSetState@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:784004
2408/y.prototype.setState@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:941707
b/6pmtOr/S/value/this.unsubscribes</<@https://graylog.company.com/assets/app.7ddb9a959f4b4a7857aa.js:2:681862
n@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:949206
6729/o.prototype.emit@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:49834
trigger@https://graylog.company.com/assets/vendor.3b152b3d9c1d8273aa7e.js:2:950087
+UTXcIS+/f</loadRotationStrategies/<@https://graylog.company.com/assets/6e13caea-6379.0a4a09e420f2da7e1b11.js:1:5969
Component Stack:
in f
in Unknown
in Unknown
in ConnectStoresWrapper[Unknown/Anonymous] stores=indexSets,indicesConfigurations
in n
in t
in t
in div
in t
in PageContentLayout__StyledGrid
in s
in div
in PageContentLayout__Container
in E
in t
in t
in div
in App__PageContent
in i
in jt
in div
in App__AppLayout
in m
in an
in t
in t
in o
in t
in it
in Unknown
in ConnectStoresWrapper[Unknown/Anonymous] stores=streams
in _t
in De
in z
in Et
in Rt
in It
in bt
in Pt
in Ot
in c
in Yt
in Lt
in n
in ee
in De
in z
in ge
Please note that clicking “Edit” on the index from the “Indices & Index Sets” page still works correctly.
Our setup is as follows:
3 graylog VMs running Graylog and Mongodb
Centos 7
Graylog 4.3.3+86369d3
openjdk version "1.8.0_332
Nginx reverse proxy in front of Graylog.
HA proxy balancing in front of that.
5 elasticsearch VM nodes
Centos 7
elasticsearch 7.10.0
I just update my Graylog server 4.3.2 → 4.3.3. I restart graylog service and tailed log file. I don’t have Nginx nor 3 GL/Mongo Servers. No errors were show in the log files, But I must mention before I restart Graylog-service my frontend crash after refreshing the browser tab, hence why I restart Graylog services.
Can I ask what have you tried already?
What does Elasticsearch/Graylog log file show?
Did you execute the basic checks (i.e. Firewall, Selinux, permissions, etc…)
Are there any outdated plugins?
At the same time I see another issue. If I create a new Index, it looks like its created ok in Graylog. But in System / Overview I get the following error : “Could not retrieve Elasticsearch cluster health. Fetching Elasticsearch cluster health failed: There was an error fetching a resource: Internal Server Error. Additional information: Couldn’t read Elasticsearch cluster health”
If I check with curl -X GET “localhost:9200/_cluster/health?pretty” it looks like a green status.
But the newly created Index do not work.
Graylog 4.3.3-1
Elasticsearch 7.10.2-1
Can you check if you can create new indexes without getting the same error as me?
If i check indicies with curl http://localhost:9200/_aliases , it is not visible. So it looks like the new index fails to be created in Elasticsearch afaikt.
Now here is the weird part. In System/Indices if I click on the “Edit” button from my example above. I receive this. It seams that if I’m not within the index set I can edit the index.
That’s strange. Having 1000 shards shouldn’t be an issue if your system can handle it. I have 1677 active primary shards and 4998 active shards total. Never had this issue before.
If I had to guess, the issue has to do with the details page again. The Edit Index Set doesn’t work from the index details page, and then the rotate active index doesn’t work from the same page. May be related?
I believe so, For myself its something with the Edit Index Set button. I’m able to rotate the index set but unable, like yourself to edit the index set from that page.
