# Kibana Logs are not getting created/captured

**URL:** <https://discuss.elastic.co/t/kibana-logs-are-not-getting-created-captured/175531>\
**Category:** Kibana\
**Created:** [April 5, 2019, 7:24am UTC](https://discuss.elastic.co/t/kibana-logs-are-not-getting-created-captured/175531 "2019-04-05T07:24:45Z")\
**Posts on this page:** 6\
**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, 7:24am UTC](https://discuss.elastic.co/t/kibana-logs-are-not-getting-created-captured/175531/1 "2019-04-05T07:24:45Z")

</div>

Kibana Service Logs are not getting created/captured for both kibana.stderr and kibana.stdout

```
[abc@abc log]$ ll | grep kibana
drwxrwxrwx 2 kibana kibana 48 Jan 30 13:09 kibana
[abc@abc log]$ cd kibana/
[abc@abc kibana]$ ll
total 0
-rwxrwxrwx 1 kibana kibana 0 Jan 14 09:48 kibana.stderr
-rwxrwxrwx 1 kibana kibana 0 Jan 14 09:48 kibana.stdout

```

Systemctl is as followed:

```
systemctl cat kibana.service
# /etc/systemd/system/kibana.service
[Unit]
Description=Kibana
StartLimitIntervalSec=30
StartLimitBurst=3

[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=always
WorkingDirectory=/

[Install]
WantedBy=multi-user.target

```

Please help me with the resolution for capturing kibana.service logs.

---

<div class="post-metadata">

**Author:** ![joelgriffith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joelgriffith/32/53738_2.png) [@joelgriffith](https://discuss.elastic.co/u/joelgriffith)\
**Post date:** [April 8, 2019, 6:52pm UTC](https://discuss.elastic.co/t/kibana-logs-are-not-getting-created-captured/175531/2 "2019-04-08T18:52:07Z")

</div>

Hey @Hazoopr. Just want to verify a few things that are easy to rule out before going further -- what's your setting (either in env vars or in kibana.yaml) for `logging.dest`? Also want to verify no other settings are there to squelch logging (like `logging.quiet`).

Thanks!

---

<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 9, 2019, 6:37am UTC](https://discuss.elastic.co/t/kibana-logs-are-not-getting-created-captured/175531/3 "2019-04-09T06:37:30Z")

</div>

> [@joelgriffith](#):
>
> logging.dest

Hi @joelgriffith,

1. Kibana configs are from kibana.yml sharing you the kibana.yaml file.

2. I am running kibana.service via systemctl command, I know journalctl command is giving some logs but still my requirement is to capture logs in /var/log/kibana/............

---

<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 11, 2019, 11:17am UTC](https://discuss.elastic.co/t/kibana-logs-are-not-getting-created-captured/175531/4 "2019-04-11T11:17:25Z")

</div>

> [@Hazoopr](#):
>
> Kibana Service Logs are not getting created/captured for both kibana.stderr and kibana.stdout
> 
> ```auto
> [abc@abc log]$ ll | grep kibana
> drwxrwxrwx 2 kibana kibana 48 Jan 30 13:09 kibana
> [abc@abc log]$ cd kibana/
> [abc@abc kibana]$ ll
> total 0
> -rwxrwxrwx 1 kibana kibana 0 Jan 14 09:48 kibana.stderr
> -rwxrwxrwx 1 kibana kibana 0 Jan 14 09:48 kibana.stdout
> 
> ```
> 
> Systemctl is as followed:
> 
> ```auto
> systemctl cat kibana.service
> # /etc/systemd/system/kibana.service
> [Unit]
> Description=Kibana
> StartLimitIntervalSec=30
> StartLimitBurst=3
> 
> [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=always
> WorkingDirectory=/
> 
> [Install]
> WantedBy=multi-user.target
> 
> ```

Issue are solved, configuring the absolute path in the logging.dest=/var/log/kibana/kibana.stdout and it was successfully capturing the logs.

marking this as close.

---

<div class="post-metadata">

**Author:** ![joelgriffith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joelgriffith/32/53738_2.png) [@joelgriffith](https://discuss.elastic.co/u/joelgriffith)\
**Post date:** [April 11, 2019, 5:41pm UTC](https://discuss.elastic.co/t/kibana-logs-are-not-getting-created-captured/175531/5 "2019-04-11T17:41:38Z")

</div>

Thanks for posting your solution! You beat me to it, apologies I wasn't able to get you there. Glad you've got it solved though!

---

<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 9, 2019, 5:41pm UTC](https://discuss.elastic.co/t/kibana-logs-are-not-getting-created-captured/175531/6 "2019-05-09T17:41:39Z")

</div>

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