kibana启动报server is not ready yet

网上说的报这个错误可能有以下几种原因

• es和kibana版本不一致
• kibana.yml文件连接es的host配置错误

我可以排除上面说的俩个错误，查看kibana日志如下

kibana7   | {"type":"log","@timestamp":"2020-09-16T03:18:30Z","tags":["warning","savedobjects-service"],"pid":6,"message":"Unable to connect to Elasticsearch. Error: [resource_already_exists_exception] index [.kibana_1/ekKwihCdRmS9YAm-_IjKfQ] already exists, with { index_uuid=\"ekKwihCdRmS9YAm-_IjKfQ\" & index=\".kibana_1\" }"}
kibana7   | {"type":"log","@timestamp":"2020-09-16T03:18:30Z","tags":["warning","savedobjects-service"],"pid":6,"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_1 and restarting Kibana."}

这已经很明了了，index [.kibana_1/ekKwihCdRmS9YAm-_IjKfQ] already exist，you can get past this message by deleting index .kibana_1 and restarting Kibana。

查看es的索引，果然发现有.kibana_1这个索引，那么我们就删除该索引，重启kibana，发现ok了。

为什么新搭建es会有.kibana_1索引呢？

  elasticsearch:
    container_name: elasticsearch7
    build:
      context: .
      dockerfile: docker/elasticsearch/Dockerfile
    environment:
      - discovery.type=single-node
    ports:
      - 9201:9200
    volumes:
      - esdata:/usr/share/elasticsearch/data
    networks:
      - cluster

发现代码中有volume esdata,该volume是之前的一个es下面挂载的，导致数据混乱了。。。。。