Kibana - DIscover - Issue "indexing is not supported on a read-only engine"

Hi,

I have an issue with KIbana Disocver module. I cannot search in my indices. The error I see is : "indexing is not supported on a read-only engine". All my indices are with status green.
I tried running the following commands:

PUT _settings
{
"index": {
"blocks": {
"read_only_allow_delete": "false"
}
}
}

PUT */_settings
{
"index": {
"blocks": {
"write": "false",
"read_only": "false"
}
}
}

Nothing helped.

Here is my cluster setting:

{
"persistent" : {
"action" : {
"auto_create_index" : "true"
},
"cluster" : {
"routing" : {
"allocation" : {
"disk" : {
"watermark" : {
"low" : "90%",
"flood_stage" : "97%",
"high" : "95%"
}
},
"enable" : "primaries"
}
},
"blocks" : {
"read_only" : "false"
}
},
"indices" : {
"recovery" : {
"max_bytes_per_sec" : "90mb"
}
},
"xpack" : {
"monitoring" : {
"elasticsearch" : {
"collection" : {
"enabled" : "false"
}
},
"collection" : {
"enabled" : "true"
},
"history" : {
"duration" : "1d"
}
}
}
},
"transient" : { }
}

Any idea what might be the problem?

PrintScreen with the error.

Regards,

Here are some error logs from kibana.log:

> {"type":"log","@timestamp":"2022-04-27T09:02:05-04:00","tags":["warning","config","deprecation"],"pid":19897,"message":"plugins.scanDirs is deprecated and is no longer used"}
> {"type":"log","@timestamp":"2022-04-27T09:02:05-04:00","tags":["warning","config","deprecation"],"pid":19897,"message":"\"server.defaultRoute\" is deprecated and has been replaced by \"uiSettings.overrides.defaultRoute\". However both key are present, ignoring \"server.defaultRoute\""}
> {"type":"log","@timestamp":"2022-04-27T09:02:05-04:00","tags":["warning","config","deprecation"],"pid":19897,"message":"Config key [monitoring.cluster_alerts.email_notifications.email_address] will be required for email notifications to work in 8.0.\""}
> {"type":"log","@timestamp":"2022-04-27T09:02:10-04:00","tags":["error","plugins","eventLog"],"pid":19897,"message":"error initializing elasticsearch resources: error creating initial index: invalid_alias_name_exception: [invalid_alias_name_exception] Reason: Invalid alias name [.kibana-event-log-7.14.2]: an index or data stream exists with the same name as the alias"}
> {"type":"log","@timestamp":"2022-04-27T09:02:10-04:00","tags":["error","plugins","eventLog"],"pid":19897,"message":"initialization failed, events will not be indexed"}
> {"type":"log","@timestamp":"2022-04-27T09:02:11-04:00","tags":["warning","plugins","reporting"],"pid":19897,"message":"Enabling the Chromium sandbox provides an additional layer of protection."}
> {"type":"log","@timestamp":"2022-04-27T09:05:00-04:00","tags":["error","plugins","wazuh","cron-scheduler"],"pid":19897,"message":"Error: Request failed with status code 401"}
> {"type":"log","@timestamp":"2022-04-27T09:05:00-04:00","tags":["error","plugins","wazuh","cron-scheduler"],"pid":19897,"message":"Error: Request failed with status code 401"}

That looks relevant. Can you try restarting Kibana?

Hi Warkolm!

Yes I did, but it didn't help. I even restarted Elasticsearch service.

Thanks!

Ok, stop Kibana, issue a delete on the .kibana-event-log-7.14.2 index/alias in Elasticsearch and then restart Kibana.

1 Like

Thanks Mark Walkom!

Problem solved. I deleted all the .kibana indices, restarted kibana and unfrozen some system indices and it worked. Additionally I flushed and cleared the cache of all the indices.

1 Like