# No runtime directory making kibana failed to start

**URL:** <https://discuss.elastic.co/t/no-runtime-directory-making-kibana-failed-to-start/318199>\
**Category:** Kibana\
**Created:** [November 4, 2022, 2:29pm UTC](https://discuss.elastic.co/t/no-runtime-directory-making-kibana-failed-to-start/318199 "2022-11-04T14:29:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JimJ](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@JimJ](https://discuss.elastic.co/u/JimJ)\
**Post date:** [November 4, 2022, 2:29pm UTC](https://discuss.elastic.co/t/no-runtime-directory-making-kibana-failed-to-start/318199/1 "2022-11-04T14:29:40Z")

</div>

Hi,

I installed kibana 8.4.1-1 on a RHEL server using Elastic RPM's.

After the first reboot, kibana failed to start because of missing `/run/kibana` directory:  
`FATAL Error: ENOENT: no such file or directory, open '/run/kibana/kibana.pid'`

Problem on our servers, the `/run` FS is a `tmpfs`.

It means the initial `/run/kibana/` directory created during the package installation diseappeared after the first reboot.

I solved it using the recommended systemd way of working adding `RuntimeDirectory` in chapter `[Service]` of the kibana.service definition via a Drop-In.

Same as in the elasticsearch.service.

Just a question: why the default kibana.service from package does not contain this option ?

Regards,

JM

---

<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:** [December 2, 2022, 2:30pm UTC](https://discuss.elastic.co/t/no-runtime-directory-making-kibana-failed-to-start/318199/2 "2022-12-02T14:30:33Z")

</div>

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