# Another Kibana instance appears to be migrating the index

**URL:** <https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index/165708>\
**Category:** Kibana\
**Created:** [January 25, 2019, 7:19am UTC](https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index/165708 "2019-01-25T07:19:39Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![walkexk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/walkexk/32/35973_2.png) [@walkexk](https://discuss.elastic.co/u/walkexk)\
**Post date:** [January 25, 2019, 7:19am UTC](https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index/165708/1 "2019-01-25T07:19:39Z")

</div>

i restart kibana,and i got the error log:"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\_1 and restarting Kibana."  
i tried curl -XDELETE [http://localhost:9200/.kibana\_1](http://localhost:9200/.kibana_1), it didn't work  
all version of logstash elasticsearch kibana are 6.5.4  
i have the basic license, so don't support security.  
i tried curl -X PUT [http://localhost:9200/\_all/\_settings](http://localhost:9200/_all/_settings) -H 'Content-Type: application/json' -d'{ "index.blocks.read\_only\_allow\_delete" : false } }'  
responese:{"acknowledged":false}  
i reinstall elasticsearch and kibana, don't work.  
i have iptables deny any 9200 9300 port incoming connect. only 127.0.0.1.

---

<div class="post-metadata">

**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\
**Post date:** [January 25, 2019, 6:47pm UTC](https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index/165708/2 "2019-01-25T18:47:56Z")

</div>

> [@walkexk](#):
>
> Another Kibana instance appears to be migrating the index.

Thanks for the report. This issue is caused by stopping the process which is in charge of handling the migration. This "locking" is to handle having multiple Kibana instances. Probably same as the issue here: [[migration v6.5] Another Kibana instance appears to be migrating the index · Issue #25464 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/25464)

Rashmi

---

<div class="post-metadata">

**Author:** ![walkexk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/walkexk/32/35973_2.png) [@walkexk](https://discuss.elastic.co/u/walkexk)\
**Post date:** [January 28, 2019, 2:41am UTC](https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index/165708/3 "2019-01-28T02:41:20Z")

</div>

it just repeat the same error after i use curl -XDELETE [http://localhost:9200/.kibana\_1](http://localhost:9200/.kibana_1) to delete the index, and restart kibana.  
i user kibana 6.5.4, not kibana 6.5.0.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 25, 2019, 2:41am UTC](https://discuss.elastic.co/t/another-kibana-instance-appears-to-be-migrating-the-index/165708/4 "2019-02-25T02:41:24Z")

</div>

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