# Kibana Upgrade to 7.8 : FATAL CLI ERROR Error: ENOENT: no such file or directory

**URL:** <https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885>\
**Category:** Kibana\
**Created:** [July 4, 2020, 11:18am UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885 "2020-07-04T11:18:37Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![hilo21](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hilo21/32/66272_2.png) [@hilo21](https://discuss.elastic.co/u/hilo21)\
**Post date:** [July 4, 2020, 11:18am UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885/1 "2020-07-04T11:18:37Z")

</div>

Upgraded from 7.7 to 7.8 elasticsearch works fine but kibana shows me this error :

FATAL CLI ERROR Error: ENOENT: no such file or directory, open '/usr/share/kibana/config/kibana.yml'  
at Object.openSync (fs.js:443:3)  
at readFileSync (fs.js:343:35)  
at readYaml (/usr/share/kibana/src/core/server/config/read\_config.js:34:69)  
at getConfigFromFiles (/usr/share/kibana/src/core/server/config/read\_config.js:66:18)  
at RawConfigService.loadConfig (/usr/share/kibana/src/core/server/config/raw\_config\_service.js:51:70)  
at bootstrap (/usr/share/kibana/src/core/server/bootstrap.js:61:20)  
at Command. (/usr/share/kibana/src/cli/serve/serve.js:195:33)  
at Command. (/usr/share/kibana/src/cli/command.js:111:20)  
at Command.listener (/usr/share/kibana/node\_modules/commander/index.js:291:8)  
at Command.emit (events.js:198:13)  
at Command.parseArgs (/usr/share/kibana/node\_modules/commander/index.js:672:12)  
at Command.parse (/usr/share/kibana/node\_modules/commander/index.js:459:21)  
at Object. (/usr/share/kibana/src/cli/cli.js:60:9)  
at Module.\_compile (internal/modules/cjs/loader.js:778:30)  
at Module.\_compile (/usr/share/kibana/node\_modules/pirates/lib/index.js:99:24)  
at Module.\_extensions..js (internal/modules/cjs/loader.js:789:10)

My config file is in /etc/kibana/ and it worked fine before. what can I do to bypass this error ?

Here is my service config for kibana :

```auto
[Unit]
Description=Kibana

[Service]
Type=simple
User=kibana
Group=kibana
# Load env vars from /etc/default/ and /etc/sysconfig/ if they exist.
# Prefixing the path with '-' makes it try to load, but if the file doesn't
# exist, it continues onward.
EnvironmentFile=-/etc/default/kibana
EnvironmentFile=-/etc/sysconfig/kibana
ExecStart=/usr/share/kibana/bin/kibana
Restart=on-failure
RestartSec=3
StartLimitBurst=3
StartLimitInterval=60
WorkingDirectory=/

[Install]
WantedBy=multi-user.target

```

---

<div class="post-metadata">

**Author:** ![madkoala](https://avatars.discourse-cdn.com/v4/letter/m/977dab/32.png) [@madkoala](https://discuss.elastic.co/u/madkoala)\
**Post date:** [July 8, 2020, 2:22am UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885/2 "2020-07-08T02:22:27Z")

</div>

Same with me, but fixed.

You should add "-c /etc/kibana/kibana.yml" at the end of ExecStart config.  
Here is my service config (/etc/systemd/system/kibana.service):

```
[Service]
Type=simple
User=kibana
Group=kibana
# Load env vars from /etc/default/ and /etc/sysconfig/ if they exist.
# Prefixing the path with '-' makes it try to load, but if the file doesn't
# exist, it continues onward.
EnvironmentFile=-/etc/default/kibana
EnvironmentFile=-/etc/sysconfig/kibana
ExecStart=/usr/share/kibana/bin/kibana "-c /etc/kibana/kibana.yml"
Restart=on-failure
RestartSec=3
StartLimitBurst=3
StartLimitInterval=60
WorkingDirectory=/
```

---

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [July 8, 2020, 4:15pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885/3 "2020-07-08T16:15:52Z")

</div>

I opened [https://github.com/elastic/kibana/issues/71120](https://github.com/elastic/kibana/issues/71120). Confirming ^ as the recommended fix.

---

<div class="post-metadata">

**Author:** ![Kunal12899](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kunal12899/32/71910_2.png) [@Kunal12899](https://discuss.elastic.co/u/Kunal12899)\
**Post date:** [July 9, 2020, 10:54pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885/4 "2020-07-09T22:54:23Z")

</div>

I am setting up a new cluster and got this error, so basically have not gone through the upgrade path and got the exact same error. Did not get success after the above step to make changes in /etc/systemd/system/kibana.service, what I see is there is no config folder available  
I am using es 7.8.0 version

```auto
/usr/share/kibana$ ls
bin built_assets LICENSE.txt node node_modules NOTICE.txt optimize package.json plugins README.txt src webpackShims x-pack

```

---

<div class="post-metadata">

**Author:** ![BannTeagann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bannteagann/32/46786_2.png) [@BannTeagann](https://discuss.elastic.co/u/BannTeagann)\
**Post date:** [July 20, 2020, 1:03pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885/5 "2020-07-20T13:03:55Z")

</div>

I have the same issue. A new install of v7.8 on Debian 10. madkoala's fix is not sufficient.

/usr/share/kibana/config does not exist.

The only changes to /etc/kibana/kibana.yaml are  
server.port  
server.host  
elasticsearch.hosts

---

<div class="post-metadata">

**Author:** ![BannTeagann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/bannteagann/32/46786_2.png) [@BannTeagann](https://discuss.elastic.co/u/BannTeagann)\
**Post date:** [July 21, 2020, 12:49am UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885/6 "2020-07-21T00:49:06Z")

</div>

Found a resolution. The following IP occurrences all must match.

/etc/kibana/kibana.yml  
`elasticsearch.url: "http://ip:9200"`

/etc/elasticsearch/elasticsearch.yml  
`network.host: "ip"`  
`cluster.initial_master_nodes: ["ip"]`

I also uncommented the following line in kibana.yml  
`#server.name: "your-hostname"`

---

<div class="post-metadata">

**Author:** ![elasticforme](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@elasticforme](https://discuss.elastic.co/u/elasticforme)\
**Post date:** [July 21, 2020, 7:52pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885/7 "2020-07-21T19:52:41Z")

</div>

> [@madkoala](#):
>
> `"-c /etc/kibana/kibana.yml"`

just confirming that I had a same problem and this fixed the problem.

---

<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:** [August 18, 2020, 7:52pm UTC](https://discuss.elastic.co/t/kibana-upgrade-to-7-8-fatal-cli-error-error-enoent-no-such-file-or-directory/239885/8 "2020-08-18T19:52:43Z")

</div>

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