Heartbeat log file is not created

Elastic Stack Beats
1

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

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

Thanks!

2

Hi,

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

Dan

3

Command

sudo service heartbeat-elastic status

Result

[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
4

The commands you gave me do not show anything

5

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

6

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

7

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