I'm suddenly facing this error:
Whenever I try to look into the index page on my installation
It constantly throws out the following error in the kibana.log file:
[2022-01-04T15:24:05.114-03:00][ERROR][http] TypeError: Cannot read property 'aliases' of undefined at <redacted path>\Kibana\x-pack\plugins\index_management\server\lib\fetch_indices.js:46:39 at Array.map (<anonymous>) at fetchIndicesCall <redacted path>\Kibana\x-pack\plugins\index_management\server\lib\fetch_indices.js:44:18) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:93:5) at fetchIndices (<redacted path>\Kibana\x-pack\plugins\index_management\server\lib\fetch_indices.js:66:19) at <redacted path>\Kibana\x-pack\plugins\index_management\server\routes\api\indices\register_reload_route.js:44:23 at Router.handle (<redacted path>\Kibana\src\core\server\http\router\router.js:163:30) at handler (<redacted path>\Kibana\src\core\server\http\router\router.js:124:50) at exports.Manager.execute (<redacted path>\Kibana\node_modules\@hapi\hapi\lib\toolkit.js:60:28) at Object.internals.handler (<redacted path>\Kibana\node_modules\@hapi\hapi\lib\handler.js:46:20) at exports.execute <redacted path>\Kibana\node_modules\@hapi\hapi\lib\handler.js:31:20) at Request._lifecycle (<redacted path>\Kibana\node_modules\@hapi\hapi\lib\request.js:370:32) at Request._execute <redacted path>\Kibana\node_modules\@hapi\hapi\lib\request.js:279:9)
I recently updated the 3 Elasticsearch Nodes I have in the installation from version 7.13.2 to 7.16.1 to mitigate the log4j2 vulnerability but I kept Kibana on 7.13.2 since the patch notes says the newer versions of kibana don't let you use legacy visualizations anymore (Why is there a need to make things incompatible i'll never know)
I hadn't entered this page on the last few months so i'm unsure when this started happening, I discovered it when I changed the main lifecycle policy of my indexes to no longer freeze them and went to see if the old ones had become unfrozen.
I really don't know what caused it and I don't want to propagate this issue to my production environment. Has anyone encountered this before or knows any way to fix it?