Kibana Docker“这可能需要几分钟”但从未启动

时间:2018-04-27 11:08:05

标签: docker elasticsearch docker-compose kibana

我正在尝试使用Docker运行Elasticsearch和Kibana。我在一台虚拟机(Ubuntu Server)上安装了docker,我使用了这里提到的docker-compose.yml,elasticsearch.yml和kibana.yml:https://stackoverflow.com/a/44005640/1843511

现在它首先开始启动额外的插件(head_540),这个插件可以在http://ip_of_my_vm:9100上找到,但Elasticsearch不是,而且kibana也没有。当我试图达到http://ip_of_my_vm:5601时,Kibana给了我一个“太多重定向”的错误。我发现它试图将我重定向到登录页面,可能原因是X-Pack随图像一起发送并自动启用(但不是因为它看起来应该如此,因为我无法打开网址)。所以我尝试通过编辑elasticsearch.yml来禁用它:

cluster.name: "chimeo-docker-cluster"
node.name: "chimeo-docker-single-node"
network.host: 0.0.0.0
xpack.security.enabled: false

http.cors.enabled: true
http.cors.allow-origin: "*"
http.cors.allow-headers: "Authorization"

和kibana.yml:

server.name: kibana
server.host: "0"
xpack.security.enabled: false
xpack.reporting.enabled: false
xpack.monitoring.enabled: false

elasticsearch.url: http://elasticsearch:9200
# elasticsearch.username: "elastic"
# elasticsearch.password: "changeme"
xpack.monitoring.ui.container.elasticsearch.enabled: false

现在,我可以在docker-compose up启动作曲家时联系Elasticsearch,但kibana卡住了:

kibana_540       | {"type":"log","@timestamp":"2018-04-27T10:56:26Z","tags":["info","optimize"],"pid":1,"message":"Optimizing and caching bundles for graph, ml, kibana, timelion and status_page. This may take a few minutes"}

现在,除了所有这些错误,如

elasticsearch_540 | [2018-04-27T10:58:12,100][ERROR][o.e.x.m.e.l.LocalExporter] failed to get monitoring watch [h7x_x5GCTjqL2wadFDSM8w_logstash_version_mismatch]
elasticsearch_540 | java.lang.IllegalStateException: watch store not started

似乎Elasticsearch实际上正在工作,因为我可以到达http://ip_of_my_vm:9200的网址,但我的kibana不是,也不是额外的插件。

任何可以帮助我解决这个问题的人?

2 个答案:

答案 0 :(得分:0)

我是这个领域的新手,但我设法让它在不久前运行。 你想停靠ELK Stack吗? 因为您似乎不在这里谈论一个logstash服务,而您所遇到的错误是关于" logstash_version_mismatch"。

您能为我们提供您的docker-compose.yml以使其更清晰吗? :)

答案 1 :(得分:0)

所以看起来只需要很长时间来优化捆绑包,因为我今天早上检查了服务器,一切似乎都有效。我不得不重新启动docker,因为Kibana中存在内部服务器错误,但现在一切正常。这些是我的YAML文件。顺便说一句,我禁用了x-pack,因为我没有使用它,我从一开始就遇到了一些x-pack的问题:

搬运工-compose.yml

version: '2'
services:
  elasticsearch:
    image: docker.elastic.co/elasticsearch/elasticsearch:5.4.0
    container_name: elasticsearch_540
    environment:
      - http.host=0.0.0.0
      - transport.host=0.0.0.0
      - "ES_JAVA_OPTS=-Xms4g -Xmx4g"
    volumes:
      - esdata:/usr/share/elasticsearch/data
      - ./elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml
    ports:
      - 9200:9200
      - 9300:9300
    ulimits:
      memlock:
        soft: -1
        hard: -1
      nofile:
        soft: 65536
        hard: 65536
    mem_limit: 4g
    cap_add:
      - IPC_LOCK
  kibana:
    image: docker.elastic.co/kibana/kibana:5.4.0
    container_name: kibana_540
    environment:
      - SERVER_HOST=0.0.0.0
    volumes:
      - ./kibana.yml:/usr/share/kibana/config/kibana.yml
    ports:
      - 5601:5601
  headPlugin:
    image: mobz/elasticsearch-head:5
    container_name: head_540
    ports:
      - 9100:9100

volumes:
  esdata:
    driver: local

elasticsearch.yml

cluster.name: "chimeo-docker-cluster"
node.name: "chimeo-docker-single-node"
network.host: 0.0.0.0
xpack.security.enabled: false

xpack.graph.enabled: false
xpack.ml.enabled: false
xpack.monitoring.enabled: false
xpack.watcher.enabled: false

http.cors.enabled: true
http.cors.allow-origin: "*"
http.cors.allow-headers: "Authorization"

kibana.yml

cluster.name: "chimeo-docker-cluster"
node.name: "chimeo-docker-single-node"
network.host: 0.0.0.0
xpack.security.enabled: false

xpack.graph.enabled: false
xpack.ml.enabled: false
xpack.monitoring.enabled: false
xpack.reporting.enabled: false
xpack.watcher.enabled: false

http.cors.enabled: true
http.cors.allow-origin: "*"
http.cors.allow-headers: "Authorization"

就像我提到的那样,我从https://stackoverflow.com/a/44005640/1843511获取了文件,但是在elasticsearch.yml和kibana.yml中禁用了x-pack,我增加了堆大小,因为它的内存耗尽了几次。 / p>

修改

我在这里分享了我当前的群集配置:https://gist.github.com/ErikvdVen/8207e39b27472361378bd3909aa247ea