Kibana server is not ready yet - kibana 7.5

Elastic Stack Kibana
1

Hi,

I upgrade elasticsearch and kibana from 7.1 to 7.5 version, keeping the previous settings.

After restart the services both are running.
Whem I call kibana on browser gives the message:
"Kibana server is not ready yet"

Can you help me?

2

It sounds like there was an issue while upgrading. What steps did you take to upgrade? What do your Kibana logs show? https://www.elastic.co/guide/en/elastic-stack/current/upgrading-elastic-stack.html

3

Also, take a look at the saved object migration troubleshooting guide: https://www.elastic.co/guide/en/kibana/current/upgrade-migrations.html

4

This were the steps:
sudo /bin/systemctl stop elasticsearch.service
sudo /bin/systemctl stop kibana.service
Sudo apt-get upgrade elasticsearch
Sudo apt-get upgrade kibana
sudo /bin/systemctl start elasticsearch.service
sudo /bin/systemctl start kibana.service

5 
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins-service"],"pid":3512,"message":"Plugin \"security\" is disabled."}
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins-system"],"pid":3512,"message":"Setting up [14] plugins: [licensing,code,timelion,features,spaces,translations,uiActions,newsfeed,inspector,embeddable,advancedUiActions,expressions,eui_utils,data]"}
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins","licensing"],"pid":3512,"message":"Setting up plugin"}
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins","code"],"pid":3512,"message":"Setting up plugin"}
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins","timelion"],"pid":3512,"message":"Setting up plugin"}
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins","features"],"pid":3512,"message":"Setting up plugin"}
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins","spaces"],"pid":3512,"message":"Setting up plugin"}
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins","translations"],"pid":3512,"message":"Setting up plugin"}
Jan  6 17:56:28 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:28Z","tags":["info","plugins","data"],"pid":3512,"message":"Setting up plugin"}
Jan  6 17:56:32 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:32Z","tags":["info","plugins","licensing"],"pid":3512,"message":"Imported changed license information from Elasticsearch for the [data] cluster: type: basic | status: active"}
Jan  6 17:56:33 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:33Z","tags":["warning","legacy-plugins"],"pid":3512,"path":"/usr/share/kibana/src/legacy/core_plugins/visualizations","message":"Skipping non-plugin directory at /usr/share/kibana/src/legacy/core_plugins/visualizations"}
Jan  6 17:56:34 srvbigdata2 kibana[3512]: {"type":"log","@timestamp":"2020-01-06T17:56:34Z","tags":["info","plugins-system"],"pid":3512,"message":"Starting [7] plugins: [licensing,code,timelion,features,spaces,translations,data]"}
    indent preformatted text by 4 spaces
6

That log message looks incomplete- is that everything? It seems like it's failing to start.

7

That's all I have in the logs.

8

Okay, at this point I would recommend trying the troubleshooting steps for saved object migration as linked earlier in the thread. If that is unsuccessful, you may need to engage with Elastic support who are able to walk you through upgrading issues.

9

I am using ELKF on RHELv6. I had upgraded from 5.x to 7.x. Filebeat and Logstash run fine, but while starting Kibana I get the message, "Kibana server is not ready yet".
I am new to Elastic stack and any help is appreciated.

10

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