# Systemctl status kibana & systemctl status Elasticsearch is Running but kibana page is not loading **URL:** \ **Category:** Elasticsearch\ **Created:** [June 29, 2022, 12:49pm UTC](https://discuss.elastic.co/t/systemctl-status-kibana-systemctl-status-elasticsearch-is-running-but-kibana-page-is-not-loading/308467 "2022-06-29T12:49:41Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![bbkunbi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bbkunbi/32/107767_2.png) [@bbkunbi](https://discuss.elastic.co/u/bbkunbi)\ **Post date:** [June 29, 2022, 12:49pm UTC](https://discuss.elastic.co/t/systemctl-status-kibana-systemctl-status-elasticsearch-is-running-but-kibana-page-is-not-loading/308467/1 "2022-06-29T12:49:41Z")
command result :==\> journalctl -fu kibana.service Jun 29 18:18:13 linux kibana[54048]: FATAL Error: Unable to complete saved object migrations for the [.kibana] index. Please check the health of your Elasticsearch cluster and try again. Unexpected Elasticsearch ResponseError: statusCode: 429, method: PUT, url: /.kibana\_7.16.2\_001/\_mapping?timeout=60s error: [cluster\_block\_exception]: index [.kibana\_7.16.2\_001] blocked by: [TOO\_MANY\_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block];, Jun 29 18:18:13 linux systemd[1]: kibana.service: Main process exited, code=exited, status=1/FAILURE Jun 29 18:18:13 linux systemd[1]: kibana.service: Failed with result 'exit-code'. Jun 29 18:18:16 linux systemd[1]: kibana.service: Scheduled restart job, restart counter is at 53. Jun 29 18:18:16 linux systemd[1]: Stopped Kibana. Jun 29 18:18:16 linux systemd[1]: Started Kibana. ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [June 29, 2022, 1:08pm UTC](https://discuss.elastic.co/t/systemctl-status-kibana-systemctl-status-elasticsearch-is-running-but-kibana-page-is-not-loading/308467/2 "2022-06-29T13:08:13Z")
> [@bbkunbi](#): > > Jun 29 18:18:16 linux systemd[1]: kibana.service: Scheduled restart job, restart counter is at 53. > Jun 29 18:18:16 linux systemd[1]: Stopped Kibana. Your kibana is not running, the systemd service is constantly restarting it. This is the reson: > [@bbkunbi](#): > > Jun 29 18:18:13 linux kibana[54048]: FATAL Error: Unable to complete saved object migrations for the [.kibana] index. Please check the health of your Elasticsearch cluster and try again. Unexpected Elasticsearch ResponseError: statusCode: 429, method: PUT, url: /.kibana\_7.16.2\_001/\_mapping?timeout=60s error: [cluster\_block\_exception]: index [**.kibana\_7.16.2\_001**] blocked by: [**TOO\_MANY\_REQUESTS/12/disk usage exceeded flood-stage watermark, index has read-only-allow-delete block**] The indice that kibana needs to write is marked as read-only because your elasticsearch cluster data path reached the flood-stage disk watermark, which means that the disk is 95% or more full, you need to clean up some space in the disk. If there is anything else running in the same server check if you can remove anything, if it is only for Elasticsearch you will need to delete some indices. ---
**Author:** ![bbkunbi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bbkunbi/32/107767_2.png) [@bbkunbi](https://discuss.elastic.co/u/bbkunbi)\ **Post date:** [June 29, 2022, 1:15pm UTC](https://discuss.elastic.co/t/systemctl-status-kibana-systemctl-status-elasticsearch-is-running-but-kibana-page-is-not-loading/308467/3 "2022-06-29T13:15:14Z")
Thank you for the prompt reply! how to delete indices from Elasticsearch? ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 27, 2022, 1:15pm UTC](https://discuss.elastic.co/t/systemctl-status-kibana-systemctl-status-elasticsearch-is-running-but-kibana-page-is-not-loading/308467/4 "2022-07-27T13:15:39Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.