# Heartbeat log file is not created

**URL:** <https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [July 31, 2020, 6:33am UTC](https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310 "2020-07-31T06:33:28Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![AClerk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aclerk/32/55297_2.png) [@AClerk](https://discuss.elastic.co/u/AClerk)\
**Post date:** [July 31, 2020, 6:33am UTC](https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310/1 "2020-07-31T06:33:28Z")

</div>

Very basic, but...  
The log file is not created.  
Any ideas?

```auto
logging.level: debug
logging.to_files: true
logging.files:
  path: /var/log/heartbeat
  name: heartbeat.log
  keepfiles: 3
  permissions: 0644

```

Copied from - [https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-logging.html](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-logging.html)

Thanks!

---

<div class="post-metadata">

**Author:** ![d.silwon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/d.silwon/32/65853_2.png) [@d.silwon](https://discuss.elastic.co/u/d.silwon)\
**Post date:** [July 31, 2020, 10:23am UTC](https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310/2 "2020-07-31T10:23:43Z")

</div>

Hi,

What show: systemctl status hearbeat or journalctl -u heartbeat.service ?

Dan

---

<div class="post-metadata">

**Author:** ![AClerk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aclerk/32/55297_2.png) [@AClerk](https://discuss.elastic.co/u/AClerk)\
**Post date:** [August 2, 2020, 11:53pm UTC](https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310/3 "2020-08-02T23:53:26Z")

</div>

Command

```auto
sudo service heartbeat-elastic status

```

Result

```auto
[root@VM00V02 ~]# sudo service heartbeat-elastic status
● heartbeat-elastic.service - Ping remote services for availability and log results to Elasticsearch or send to Logstash.
   Loaded: loaded (/usr/lib/systemd/system/heartbeat-elastic.service; disabled; vendor preset: disabled)
   Active: active (running) since Fri 2020-07-31 16:21:17 AEST; 2 days ago
     Docs: https://www.elastic.co/products/beats/heartbeat
 Main PID: 39477 (heartbeat)
   CGroup: /system.slice/heartbeat-elastic.service
           └─39477 /usr/share/heartbeat/bin/heartbeat -e -c /etc/heartbeat/heartbeat.yml -path.home /usr/share/heartbeat -path.config /etc/heartbeat -path.data /var/lib/heartbeat -path.logs /var/log/heartbeat

Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.841+1000 DEBUG [publisher] memqueue/eventloop.go:535 broker ACK events: count=1, start-seq=7859, end-seq=7859
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/eventloop.go:535 broker ACK events: count=1, start-seq=7859, end-seq=7859
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/eventloop.go:535 broker ACK events: count=1, start-seq=7859, end-seq=7859
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/eventloop.go:535 broker ACK events: count=1, start-seq=7859, end-seq=7859
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/eventloop.go:535 broker ACK events: count=1, start-seq=7859, end-seq=7859
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/eventloop.go:535 broker ACK events: count=1, start-seq=7859, end-seq=7859
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/eventloop.go:535 broker ACK events: count=1, start-seq=7859, end-seq=7859
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/eventloop.go:535 broker ACK events: count=1, start-seq=7859, end-seq=7859
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/ackloop.go:128 ackloop: return ack to broker loop:20
Aug 03 09:50:48 VM00V02 heartbeat[39477]: 2020-08-03T09:50:48.842+1000 DEBUG [publisher] memqueue/ackloop.go:131 ackloop: done send ack

```

---

<div class="post-metadata">

**Author:** ![AClerk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aclerk/32/55297_2.png) [@AClerk](https://discuss.elastic.co/u/AClerk)\
**Post date:** [August 2, 2020, 11:55pm UTC](https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310/4 "2020-08-02T23:55:15Z")

</div>

> [@d.silwon](#):
>
> journalctl -u heartbeat.service

The commands you gave me do not show anything

---

<div class="post-metadata">

**Author:** ![d.silwon](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/d.silwon/32/65853_2.png) [@d.silwon](https://discuss.elastic.co/u/d.silwon)\
**Post date:** [August 3, 2020, 9:45am UTC](https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310/5 "2020-08-03T09:45:21Z")

</div>

> [@AClerk](#):
>
> `/var/log/heartbeat`

Strange, because you should have logs in this directory: /var/log/heartbeat/

---

<div class="post-metadata">

**Author:** ![AClerk](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/aclerk/32/55297_2.png) [@AClerk](https://discuss.elastic.co/u/AClerk)\
**Post date:** [August 4, 2020, 12:04am UTC](https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310/6 "2020-08-04T00:04:41Z")

</div>

I agree it is strange.  
I have other beat services running with no issues, on many servers.  
First time I encounter such an issue.

---

<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:** [September 1, 2020, 2:04am UTC](https://discuss.elastic.co/t/heartbeat-log-file-is-not-created/243310/7 "2020-09-01T02:04:42Z")

</div>

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