Kibana_task_manger_2 cannot be deleted

I need help, please. I tried the following comand:
// curl -XDELETE 'http://localhost:9200/.kibana_task_manager_2' --header "content-type: application/JSON" -u elastic -p

and I get the following response:

curl: (52) Empty reply from server

< Feb 28 14:00:52 kibana[1058]: {"type":"log","@timestamp":"2020-02-28T14:00:52Z","tags":["info","savedobjects-service"],"pid":1058,"message":"Starting saved objects migrations"}
Feb 28 14:00:52 kibana[1058]: {"type":"log","@timestamp":"2020-02-28T14:00:52Z","tags":["info","savedobjects-service"],"pid":1058,"message":"Creating index .kibana_task_manager_2."}
Feb 28 14:00:52 kibana[1058]: {"type":"log","@timestamp":"2020-02-28T14:00:52Z","tags":["warning","savedobjects-service"],"pid":1058,"message":"Unable to connect to Elasticsearch. Error: [resource_already_exists_exception] index [.kibana_task_manager_2/g8bjExgTS1286AKdfmIp8Q] already exists, with { index_uuid="g8bjExgTS1286AKdfmIp8Q" & index=".kibana_task_manager_2" }"}
Feb 28 14:00:52 kibana[1058]: {"type":"log","@timestamp":"2020-02-28T14:00:52Z","tags":["warning","savedobjects-service"],"pid":1058,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana_task_manager_2 and restarting Kibana."} />

IF the original .kibana index still exists, and there is a message telling you another instance is still running - try deleting the .kibana_1 and .kibana_2 if it exists. Then restart Kibana and provide the logs there, and additionally any logs from Elasticsearch. I presume something is failing along the way. I guess this is the problem.

More info on similar issue can be found here:


This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.