Heartbeat startup error

Elastic Stack Beats
1

Hi all,
I'm trying to configure heartbeat-elastic without success. When I try to start the service I get this error:
● heartbeat-elastic.service - Ping remote services for availability and log results to Elasticsearch or send to Logstash.
Loaded: loaded (/lib/systemd/system/heartbeat-elastic.service; enabled; vendor preset: enabled)
Active: failed (Result: start-limit-hit) since Mon 2019-06-10 10:22:37 UTC; 27min ago
Docs: https://www.elastic.co/products/beats/heartbeat
Process: 12111 ExecStart=/usr/share/heartbeat/bin/heartbeat -c /etc/heartbeat/heartbeat.yml -path.home /usr/share/heartbeat -path.config /etc/heartbeat -path.data /va
Main PID: 12111 (code=exited, status=1/FAILURE)

Jun 10 10:22:37 host systemd[1]: heartbeat-elastic.service: Unit entered failed state.
Jun 10 10:22:37 host systemd[1]: heartbeat-elastic.service: Failed with result 'exit-code'.
Jun 10 10:22:37 host systemd[1]: heartbeat-elastic.service: Service hold-off time over, scheduling restart.
Jun 10 10:22:37 host systemd[1]: Stopped Ping remote services for availability and log results to Elasticsearch or send to Logstash..
Jun 10 10:22:37host systemd[1]: heartbeat-elastic.service: Start request repeated too quickly.
Jun 10 10:22:37 host systemd[1]: Failed to start Ping remote services for availability and log results to Elasticsearch or send to Logstash..
Jun 10 10:22:37 host systemd[1]: heartbeat-elastic.service: Unit entered failed state.
Jun 10 10:22:37 host systemd[1]: heartbeat-elastic.service: Failed with result 'start-limit-hit'.

I guess that it has some problem of configuration but checking the heartbeat.yml file all seems correct:
heartbeat.monitors:

  • type: tcp
    hosts: ${EXAMPLE}
    schedule: '@every 10s'
    processors:
  • add_cloud_metadata: ~
  • add_host_metadata:
    netinfo.enabled: true
  • add_locale: ~
    fields:
    name: "{EXAMPLE}" owneremail: "{EXAMPLE}"
    projectid: "{EXAMPLE}" orgscope: "{EXAMPLE}"
    functionalscope: "{EXAMPLE}" environment: "{EXAMPLE}"
    tier: "{EXAMPLE}" applicationid: "{EXAMPLE}"
    appversion: "{EXAMPLE}" stage: "{EXAMPLE}"
    network: "{EXAMPLE}" setup.template.settings: index.number_of_shards: 1 index.codec: best_compression output.elasticsearch: hosts: {EXAMPLE}
    protocol: "https"
    username: {EXAMPLE} password: {EXAMPLE}
    ssl.verification_mode: none
    ssl.supported_protocols: [TLSv1.2]
    xpack.monitoring.enabled: true

All variables are correctly sets and works with other beats..any clue? thank you

2

Can you share your heartbeat log output? The output from systemd doesn't contain enough info.

4

andre_b -- Any update on whether you were able to work past this error?

I'm seeing this as well and would appreciate an update if you have one.

5

hi Andrew,

the only way to let it work is writing all value, don't now why but defining these value by environment variables it doesn't work. I'm running the 6.7.1 maybe has been fixed with latest updates.
It's quite strange because other beats are working correctly with that settings

6

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