Something went wrong” Errors Due to Elasticsearch Index Corruption
Applies to
- NetApp Console Classification 1.45.0 and above
- Elastic search container error
- On-premises NETAPP Console Agent (all supported versions)
- Environments where an older Classification VM is re-attached to a new Agent
Issue
After migrating or reattaching an existing NETAPP Console Classification (DataSense) VM to a new Agent, the following symptoms are observed:
The Classification dashboard in Agent fails to load, showing “Something went wrong” errors and UI also reports “Agent waiting to initialize.”
All containers appear to be running, but functionality is impaired.
Log output from the DataSense VM and containers includes:
logv1.0|2025-09-03 16:32:06,147|INFO|ds_logger|waitfor|344|11|None|waitfor_344|Checking readiness of [elasticsearch]INFO:elastic_transport.transport:GET http://elasticsearch:9200/_cat/indices?format=json [status:200 duration:0.010s]logv1.0|2025-09-03 16:32:06,158|ERROR|ds_logger|waitfor|46|11|None|waitfor_46|Service [elasticsearch] is not ready:ESIndex "directories-v47" is not healthy...logv1.0|2025-09-03 16:00:15,181|ERROR|ds_logger|elastic_search_api|1570|13|None|10cea15c6d24673c|Failed to fetch total scanned size!
Elasticsearch container logs show the main index (e.g., directories-v47) in a red/unhealthy state.
