# Kibana service goes down & result in systemctl daemon-reload (without any changes)

**URL:** <https://discuss.elastic.co/t/kibana-service-goes-down-result-in-systemctl-daemon-reload-without-any-changes/175557>\
**Category:** Kibana\
**Created:** [April 5, 2019, 9:38am UTC](https://discuss.elastic.co/t/kibana-service-goes-down-result-in-systemctl-daemon-reload-without-any-changes/175557 "2019-04-05T09:38:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Hazoopr](https://avatars.discourse-cdn.com/v4/letter/h/c6cbf5/32.png) [@Hazoopr](https://discuss.elastic.co/u/Hazoopr)\
**Post date:** [April 5, 2019, 9:38am UTC](https://discuss.elastic.co/t/kibana-service-goes-down-result-in-systemctl-daemon-reload-without-any-changes/175557/1 "2019-04-05T09:38:55Z")

</div>

[elasticsearch@gcp6207hdfqa02 ~]$ sudo systemctl status kibana.service -l  
● kibana.service - Kibana  
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)  
Active: inactive (dead) since Fri 2019-04-05 05:42:09 UTC; 28min ago  
Process: 3131 ExecStart=/usr/share/kibana/bin/kibana -c /etc/kibana/kibana.yml (code=exited, status=0/SUCCESS)  
Main PID: 3131 (code=exited, status=0/SUCCESS)

Apr 05 05:41:19 \<hostname -f\> kibana[3131]: {"type":"response","@timestamp":"2019-04-05T05:41:19Z","tags":,"pid":3131,"method":"get","statusCode":304,"req":{"url":"/ui/fonts/open\_sans/open\_sans\_v15\_latin\_600.woff2","method":"get","headers":{"host":"\<hostname -i\>:5601","connection":"keep-alive","origin":"http://\<hostname -i\>:5601","user-agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.86 Safari/537.36","accept":"_/_","referer":"http://\<hostname -i\>:5601/app/kibana","accept-encoding":"gzip, deflate","accept-language":"en-US,en;q=0.9","if-none-match":""24234c1c81b3948758c1a0be8e5a65386ca94c52"","if-modified-since":"Thu, 21 Mar 2019 16:01:09 GMT"},"remoteAddress":"\<ip\_addr\>","userAgent":"\<ip\_addr\>","referer":"http://\<hostname -i\>:5601/app/kibana"},"res":{"statusCode":304,"responseTime":4,"contentLength":9},"message":"GET /ui/fonts/open\_sans/open\_sans\_v15\_latin\_600.woff2 304 4ms - 9.0B"}  
Apr 05 05:42:09 \<hostname -f\> systemd[1]: Stopping Kibana...  
Apr 05 05:42:09 \<hostname -f\> systemd[1]: Stopped Kibana.  
**Warning: kibana.service changed on disk. Run 'systemctl daemon-reload' to reload units.**

---

<div class="post-metadata">

**Author:** ![Hazoopr](https://avatars.discourse-cdn.com/v4/letter/h/c6cbf5/32.png) [@Hazoopr](https://discuss.elastic.co/u/Hazoopr)\
**Post date:** [April 5, 2019, 9:39am UTC](https://discuss.elastic.co/t/kibana-service-goes-down-result-in-systemctl-daemon-reload-without-any-changes/175557/2 "2019-04-05T09:39:31Z")

</div>

Issue resolved as it was due to auto upgrade of kibana service via yum-cron which leads to system daemon-reload.  
for auto-upgrade issue refer to [ElasticSearch, Kibana & Logstash Auto-Upgrading](https://discuss.elastic.co/t/elasticsearch-kibana-logstash-auto-upgrading/175565/2)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 3, 2019, 9:39am UTC](https://discuss.elastic.co/t/kibana-service-goes-down-result-in-systemctl-daemon-reload-without-any-changes/175557/3 "2019-05-03T09:39:31Z")

</div>

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