Kibana 6.3 not getting started

Elastic Stack Kibana
1

I have started elasticsearch 6.3 and then kibana 6.3 with changes in kibana.yml---> elasticsearchurl field. My console shows no error but kibana doesnt start. I get "Kibana did not load properly. Check the server output for more information." wen i hit localhost:5601.
Following is the log i get which keeps on iterating constantly:

log [11:33:52.858] [debug][kibana-monitoring][monitoring-ui] Uploading bulk Kibana monitoring payload
log [11:33:54.979] [debug][plugin] Checking Elasticsearch version
ops [11:33:57.375] memory: 106.0MB uptime: 0:11:34 load: [0.00 0.00 0.00] delay: 2.407
log [11:33:57.382] [debug][kibana-monitoring][monitoring-ui] Received Kibana Ops event data
log [11:33:57.496] [debug][plugin] Checking Elasticsearch version
log [11:34:00.013] [debug][plugin] Checking Elasticsearch version
ops [11:34:02.375] memory: 106.7MB uptime: 0:11:39 load: [0.00 0.00 0.00] delay: 2.395
log [11:34:02.382] [debug][kibana-monitoring][monitoring-ui] Received Kibana Ops event data
log [11:34:02.534] [debug][plugin] Checking Elasticsearch version
log [11:34:02.851] [debug][kibana-monitoring][monitoring-ui] Fetching data from kibana collector
log [11:34:02.854] [debug][kibana-monitoring][monitoring-ui] Fetching data from kibana_stats collector
log [11:34:02.858] [debug][kibana-monitoring][monitoring-ui] Fetching data from kibana_settings collector
log [11:34:02.860] [debug][kibana-monitoring][monitoring-ui] Fetching data from reporting_stats collector
log [11:34:02.866] [debug][kibana-monitoring][monitoring-ui] not sending [kibana_settings] monitoring document because [undefined] is null or invalid.

2

By default, everything works without any modification of the conf files.

Can I have your changes?

3

I just changed these:

The URL of the Elasticsearch instance to use for all your queries.

elasticsearch.url: "http://localhost:9200"

Set the value of this setting to true to log all events, including system usage information

and all requests.

logging.verbose: true

4

I was getting the same. Deleting the monitoring indices and letting ES re-create them fixed it for me.

5

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