# Upgraded to 7.2 "Kibana server is not ready yet" **URL:** \ **Category:** Kibana\ **Created:** [June 28, 2019, 3:05pm UTC](https://discuss.elastic.co/t/upgraded-to-7-2-kibana-server-is-not-ready-yet/188072 "2019-06-28T15:05:53Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\ **Post date:** [June 28, 2019, 3:05pm UTC](https://discuss.elastic.co/t/upgraded-to-7-2-kibana-server-is-not-ready-yet/188072/1 "2019-06-28T15:05:53Z")
I'm working in Ubuntu 18.04 and upgraded ELK stack to 7.2. All services are running (Elasticsearch, Logstash , Kibana and Filebeat), but Kibana displays "Kibana server is not ready yet" and the kibana status shows: Jun 28 15:54:39 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:54:39Z","tags":["error","task\_manager"],"pid":1099,"message":"Failed to poll for work: [search\_phase\_execution\_exception] all shards failed :: {"path":"/.kibana\_task\_manager/\_search","query":{"ignore\_unavailable":true},"body":"{\"query\":{\"bool\":{\"must\":[{\"term\":{\"type\":\"task\"}},{\"b Jun 28 15:54:42 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:54:42Z","tags":["error","task\_manager"],"pid":1099,"message":"Failed to poll for work: [search\_phase\_execution\_exception] all shards failed :: {"path":"/.kibana\_task\_manager/\_search","query":{"ignore\_unavailable":true},"body":"{\"query\":{\"bool\":{\"must\":[{\"term\":{\"type\":\"task\"}},{\"b Jun 28 15:54:44 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:54:44Z","tags":["info","migrations"],"pid":1099,"message":"Creating index .kibana\_2."} Jun 28 15:54:44 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:54:44Z","tags":["warning","migrations"],"pid":1099,"message":"Another Kibana instance appears to be migrating the index. Waiting for that migration to complete. If no other Kibana instance is attempting migrations, you can get past this message by deleting index .kibana\_2 and restarting Kibana."} Jun 28 15:55:45 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:55:45Z","tags":["warning","task\_manager"],"pid":1099,"message":"The task maps\_telemetry "Maps-maps\_telemetry" is not cancellable."} Jun 28 15:56:49 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:56:49Z","tags":["warning","task\_manager"],"pid":1099,"message":"The task maps\_telemetry "Maps-maps\_telemetry" is not cancellable."} Jun 28 15:57:49 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:57:49Z","tags":["warning","task\_manager"],"pid":1099,"message":"The task maps\_telemetry "Maps-maps\_telemetry" is not cancellable."} Jun 28 15:58:49 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:58:49Z","tags":["warning","task\_manager"],"pid":1099,"message":"The task maps\_telemetry "Maps-maps\_telemetry" is not cancellable."} Jun 28 15:59:49 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T14:59:49Z","tags":["warning","task\_manager"],"pid":1099,"message":"The task maps\_telemetry "Maps-maps\_telemetry" is not cancellable."} Jun 28 16:00:50 SCL-SIEM-01 kibana[1099]: {"type":"log","@timestamp":"2019-06-28T15:00:50Z","tags":["warning","task\_manager"],"pid":1099,"message":"The task maps\_telemetry "Maps-maps\_telemetry" is not cancellable."} Any Thoughts? ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [June 28, 2019, 4:54pm UTC](https://discuss.elastic.co/t/upgraded-to-7-2-kibana-server-is-not-ready-yet/188072/2 "2019-06-28T16:54:24Z")
From which version did you upgrade from ? ---
**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\ **Post date:** [July 1, 2019, 12:46pm UTC](https://discuss.elastic.co/t/upgraded-to-7-2-kibana-server-is-not-ready-yet/188072/3 "2019-07-01T12:46:56Z")
sorry for the late reply we upgraded from Kibana 6.8 I believe and elasticsearch was 7 ---
**Author:** ![SCL\_ADMIN](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/scl_admin/32/49037_2.png) [@SCL\_ADMIN](https://discuss.elastic.co/u/SCL_ADMIN)\ **Post date:** [July 2, 2019, 4:25pm UTC](https://discuss.elastic.co/t/upgraded-to-7-2-kibana-server-is-not-ready-yet/188072/4 "2019-07-02T16:25:09Z")
Look like i've fix the problem I deleted one of the kibana index using curl -XDELETE '[http://localhost:9200/.kibana\_1](http://localhost:9200/.kibana_1)' --header "content-type: application/JSON" -u elastic -p based off this: > ---
**Author:** ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)\ **Post date:** [July 16, 2019, 1:29pm UTC](https://discuss.elastic.co/t/upgraded-to-7-2-kibana-server-is-not-ready-yet/188072/5 "2019-07-16T13:29:53Z")
Glad it worked..thanks for posting your solution. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [August 13, 2019, 1:29pm UTC](https://discuss.elastic.co/t/upgraded-to-7-2-kibana-server-is-not-ready-yet/188072/6 "2019-08-13T13:29:58Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.