Heartbeat keeps getting restarted

[hanjukim]

I am using docker image elastic/heartbeat:6.8.8, and container keeps getting restarted.
Full log
https://pastebin.com/raw/Aag5Q3eL

Configuration

############################# Heartbeat ######################################
heartbeat.config.monitors:
  # Directory + glob pattern to search for configuration files
  path: ${path.config}/monitors.d/*.yml
  reload.enabled: true

#============================== Output monitoring =====================================
output.elasticsearch:
  hosts: ["elasticsearch:9200"]
  index: "heartbeat-%{[beat.version]}-%{+yyyy}"
#============================== Kibana =====================================
setup:
  kibana.host: "kibana:5601"
  kibana.protocol: "http"

#==================== Elasticsearch template setting ==========================
setup.template.enabled: true
setup.template.name: "heartbeat"
setup.template.pattern: "heartbeat-*"
setup.template.overwrite: true

setup.template.settings:
  index:
    number_of_shards: 1
    number_of_replicas: 1
    codec: best_compression
    number_of_routing_shards: 30

#============================== X-Pack monitoring =====================================
xpack.monitoring.enabled: true
xpack.monitoring.elasticsearch.url: ["http://elasticsearch:9200"]

#================================ HTTP Endpoint ======================================
# Defines if the HTTP endpoint is enabled.
http.enabled: true

# The HTTP endpoint will bind to this hostname or IP address. It is recommended to use only localhost.
http.host: localhost

# Port on which the HTTP endpoint will bind. Default is 5066.
http.port: 5066

#================================ Logging =====================================
logging.level: warning

[Andrew_Cholakian1 (Andrew Cholakian)]

Apologies for the delay here.

There's a known bug with that version of heartbeat that was just patched (it's not present in 7.x versions) where multiple ports, when used with the tcp monitor type would cause a hard crash. I can't tell if that's happening here because your monitor config is not included.

If that's what the cause is, the work around is to have a separate config line per port (single value per monitor).