Kibana 7.9.1: Startup Issue

Elastic Stack Kibana
1

Hi,
We're setting up a new 7.9.1 elasticsearch/kibana combo. where kibana is running in kubernetes. This is a normal topology for us.

However, I'm seeing errors that don't make sense in the kibana log:

{"type":"log","@timestamp":"2020-09-14T07:52:18Z","tags":["info","savedobjects-service"],"pid":1,"message":"Waiting until all Elasticsearch nodes are compatible with Kibana before starting saved objects migrations..."}
{"type":"log","@timestamp":"2020-09-14T07:52:18Z","tags":["debug","plugins","reporting","config"],"pid":1,"message":"Running on OS: 'Linux Centos 7.8.2003'"}
{"type":"log","@timestamp":"2020-09-14T07:52:18Z","tags":["warning","plugins","reporting","config"],"pid":1,"message":"Chromium sandbox provides an additional layer of protection, but is not supported for Linux Centos 7.8.2003 OS. Automatically setting 'xpack.reporting.capture.browser.chromium.disableSandbox: true'."}
{"type":"log","@timestamp":"2020-09-14T07:52:18Z","tags":["debug","plugins","reporting"],"pid":1,"message":"Setup complete"}
{"type":"log","@timestamp":"2020-09-14T07:53:27Z","tags":["debug","http"],"pid":1,"message":"Kibana server is not ready yet get:/."}
{"type":"log","@timestamp":"2020-09-14T07:54:18Z","tags":["error","savedobjects-service"],"pid":1,"message":"Unable to retrieve version information from Elasticsearch nodes."}
{"type":"log","@timestamp":"2020-09-14T07:55:51Z","tags":["debug","http"],"pid":1,"message":"Kibana server is not ready yet get:/."}
{"type":"log","@timestamp":"2020-09-14T07:55:51Z","tags":["debug","http"],"pid":1,"message":"Kibana server is not ready yet get:/favicon.ico."}
{"type":"log","@timestamp":"2020-09-14T07:55:53Z","tags":["debug","http"],"pid":1,"message":"Kibana server is not ready yet get:/."}
{"type":"log","@timestamp":"2020-09-14T07:55:53Z","tags":["debug","http"],"pid":1,"message":"Kibana server is not ready yet get:/favicon.ico."}

Seeing as the remote cluster is running at the same version, is running, and has an elected master I'm rather confused. I can also curl the remote cluster from the kibana container.

Kibana pod startup parameters look like this:

        command:
        - /usr/share/kibana/bin/kibana
        - --cpu.cgroup.path.override=/
        - --cpuacct.cgroup.path.override=/
        - --elasticsearch.hosts=http://elasticsearch-service
        - --elasticsearch.requestTimeout=120000
        - --elasticsearch.startupTimeout=120000
        - --kibana.defaultAppId=discover
        - --kibana.index=.kibana
        - --logging.dest=stdout
        - --logging.quiet=false
        - --logging.verbose=true
        - --server.host=0.0.0.0
        - --server.name=kibana-7
        - --server.port=5601
        - --status.allowAnonymous=true
        - --xpack.infra.sources.default.logAlias=*logs-*
        - --monitoring.enabled=false
        - --xpack.security.enabled=false
        - --xpack.ml.enabled=false

Thx D

2

Looks like there was a network change which blocked off port level access.

1 Like
3

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