Issue when starting Kibana container

[bnouyou]

Hello,

I wanted to start kibana container and do the command: docker-compose up -d kibana.
Kibana container remains unhealthy and this is what I have in logs:

kibana_1           | {"type":"log","@timestamp":"2021-08-09T09:03:24Z","tags":["warning","elasticsearch","data"],"pid":8,"message":"Unable to revive connection: /"}
kibana_1           | {"type":"log","@timestamp":"2021-08-09T09:03:24Z","tags":["warning","elasticsearch","data"],"pid":8,"message":"No living connections"}
kibana_1           | {"type":"log","@timestamp":"2021-08-09T09:03:24Z","tags":["license","warning","xpack"],"pid":8,"message":"License information from the X-Pack plugin could not be obtained from Elasticsearch for the [data] cluster. Error: No Living connections"}
kibana_1           | {"type":"log","@timestamp":"2021-08-09T09:03:25Z","tags":["warning","elasticsearch","admin"],"pid":8,"message":"Unable to revive connection: /"}
kibana_1           | {"type":"log","@timestamp":"2021-08-09T09:03:25Z","tags":["warning","elasticsearch","admin"],"pid":8,"message":"No living connections"}
kibana_1           | {"type":"log","@timestamp":"2021-08-09T09:03:27Z","tags":["warning","elasticsearch","admin"],"pid":8,"message":"Unable to revive connection: /"}
kibana_1           | {"type":"log","@timestamp":"2021-08-09T09:03:27Z","tags":["warning","elasticsearch","admin"],"pid":8,"message":"No living connections"}
kibana_1           | {"type":"response","@timestamp":"2021-08-09T09:03:27Z","tags":[],"pid":8,"method":"get","statusCode":302,"req":{"url":"/","method":"get","headers":{"host":"kibana:5601","user-agent":"curl/7.64.0","accept":"*/*"},"remoteAddress":"172.17.0.7","userAgent":"172.17.0.7"},"res":{"statusCode":302,"responseTime":2,"contentLength":9},"message":"GET / 302 2ms - 9.0B"}

My ES is working.
I know that Kibana is not necessarily needed but I find it useful.

Thank you for you help.

[hanars]

Can you duble check that the ELASTICSEARCH_HOSTS variable in your kibana image corresponds to a valid elasticsearch host URL?

[bnouyou]

My ELASTICSEARCH_HOSTS variable is set like that in the docker-compose.yml file:

kibana:
    image: gcr.io/seqr-project/kibana:gcloud-prod
    environment:
      - ELASTICSEARCH_HOSTS=http://elasticsearch:9200

This is what I have in logs when I start kibana:

Attaching to seqr_kibana_1
kibana_1           | + env
kibana_1           | HOSTNAME=cc6ba8f49ba3
kibana_1           | KIBANA_VERSION=6.3.2
kibana_1           | JAVA_HOME=/usr/local/openjdk-8
kibana_1           | JAVA_BASE_URL=https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u242-b08/OpenJDK8U-jdk_
kibana_1           | PWD=/
kibana_1           | KIBANA_SERVICE_PORT=5601
kibana_1           | JAVA_URL_VERSION=8u242b08
kibana_1           | HOME=/root
kibana_1           | LANG=C.UTF-8
kibana_1           | SHLVL=1
kibana_1           | ELASTICSEARCH_HOSTS=http://elasticsearch:9200
kibana_1           | PATH=/usr/local/openjdk-8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
kibana_1           | JAVA_VERSION=8u242
kibana_1           | _=/usr/bin/env
kibana_1           | + su kibana -c '/usr/local/kibana-6.3.2-linux-x86_64/bin/kibana     --host=0.0.0.0     --port=5601     --elasticsearch.url=http://:'

See the last row, it seems that elasticsearch.urldoesn't take the variable.

[hanars]

So you appear to be using really old images as that is running kibana-6.3.2 and we are on 7.8.1. If you are intentionally maintaining elasticsearch and kibana on version 6 instead of 7, you can add ELASTICSEARCH_URL to the kibana environment with the same value currently in ELASTICSEARCH_HOSTSand it should work. If you are using elasticsearch version 7, the I would make sure to update your kibana docker image - try running docker-compose pull kibana

[bnouyou]

Thank you ! I pulled the latest image of kibana and now it's working.

[hanars]

So you appear to be using really old images as that is running `kibana-6.3.2` and we are on `7.8.1`. If you are intentionally maintaining elasticsearch and kibana on version 6 instead of 7, you can add `ELASTICSEARCH_URL` to the kibana environment with the same value currently in `ELASTICSEARCH_HOSTS`and it should work. If you are using elasticsearch version 7, the I would make sure to update your kibana docker image - try running `docker-compose pull kibana`

…

On Tue, Aug 10, 2021 at 5:52 AM Bénédicte ***@***.***> wrote: My ELASTICSEARCH_HOSTS variable is set like that in the docker-compose.yml file: kibana: image: gcr.io/seqr-project/kibana:gcloud-prod environment: - ELASTICSEARCH_HOSTS=http://elasticsearch:9200 This is what I have in logs when I start kibana: Attaching to seqr_kibana_1 kibana_1 | + env kibana_1 | HOSTNAME=cc6ba8f49ba3 kibana_1 | KIBANA_VERSION=6.3.2 kibana_1 | JAVA_HOME=/usr/local/openjdk-8 kibana_1 | JAVA_BASE_URL=https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u242-b08/OpenJDK8U-jdk_ kibana_1 <https://github.com/AdoptOpenJDK/openjdk8-upstream-binaries/releases/download/jdk8u242-b08/OpenJDK8U-jdk_kibana_1> | PWD=/ kibana_1 | KIBANA_SERVICE_PORT=5601 kibana_1 | JAVA_URL_VERSION=8u242b08 kibana_1 | HOME=/root kibana_1 | LANG=C.UTF-8 kibana_1 | SHLVL=1 kibana_1 | ELASTICSEARCH_HOSTS=http://elasticsearch:9200 kibana_1 | PATH=/usr/local/openjdk-8/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin kibana_1 | JAVA_VERSION=8u242 kibana_1 | _=/usr/bin/env kibana_1 | + su kibana -c '/usr/local/kibana-6.3.2-linux-x86_64/bin/kibana --host=0.0.0.0 --port=5601 --elasticsearch.url=http://:' See the last row, it seems that elasticsearch.urldoesn't take the variable. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2038 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AF3VREHLL5QBLOJ6NDP4BVDT4DZGBANCNFSM5BZTG6LA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email> .