# Heartbeat 7 seems to stop running
**URL:** https://discuss.elastic.co/t/heartbeat-7-seems-to-stop-running/170261
**Category:** Beats
**Tags:** heartbeat
**Created:** [February 27, 2019, 11:34pm UTC](https://discuss.elastic.co/t/heartbeat-7-seems-to-stop-running/170261 "2019-02-27T23:34:57Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@RayS](https://discuss.elastic.co/u/RayS)
#### Post date: [February 27, 2019, 11:34pm UTC](https://discuss.elastic.co/t/heartbeat-7-seems-to-stop-running/170261/1 "2019-02-27T23:34:57Z")
I'm trying to nail down what is happening with it. I start heartbeat using a simple "./hearbeat &" and it seems to run fine for a couple of hours and then the process dies.
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [February 28, 2019, 2:05pm UTC](https://discuss.elastic.co/t/heartbeat-7-seems-to-stop-running/170261/2 "2019-02-28T14:05:33Z")
That's not good. Is there anything at all in the logs?
---
### Author:  [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)
#### Post date: [February 28, 2019, 2:05pm UTC](https://discuss.elastic.co/t/heartbeat-7-seems-to-stop-running/170261/3 "2019-02-28T14:05:49Z")
Also, can you share your config?
---
### Author:  [@RayS](https://discuss.elastic.co/u/RayS)
#### Post date: [February 28, 2019, 2:57pm UTC](https://discuss.elastic.co/t/heartbeat-7-seems-to-stop-running/170261/4 "2019-02-28T14:57:09Z")
So don't get to concerned yet. I started the heartbeat service last night doing a full path command like this:
```
/home/rseals/heartbeat-7.0.0-beta1-linux-x86_64/heartbeat &
```
And it's been running since Feb 27, 2019 @ 20:09:47.468. So that has been better than before. Before I was just starting it as ./heartbeat & from the directory.
My config is super super simple:
```
> # Configure monitors inline
> heartbeat.monitors:
> - type: http
>
> # List or urls to query
> urls: ["http://10.200.100.101:9200","http://10.200.100.100"]
>
> # Configure task schedule
> schedule: '@every 10s'
>
> # Total test connection and data exchange timeout
> timeout: 16s
>
> #==================== Elasticsearch template setting ==========================
>
> setup.template.settings:
> index.number_of_shards: 1
> index.codec: best_compression
> #_source.enabled: false
>
> #================================ General =====================================
>
> # The name of the shipper that publishes the network data. It can be used to group
> # all the transactions sent by a single shipper in the web interface.
> #name:
>
> # The tags of the shipper are included in their own field with each
> # transaction published.
> #tags: ["service-X", "web-tier"]
>
> # Optional fields that you can specify to add additional information to the
> # output.
> #fields:
> # env: staging
>
>
> #============================== Dashboards =====================================
> # These settings control loading the sample dashboards to the Kibana index. Loading
> # the dashboards is disabled by default and can be enabled either by setting the
> # options here or by using the `setup` command.
> setup.dashboards.enabled: false
>
> # The URL from where to download the dashboards archive. By default this URL
> # has a value which is computed based on the Beat name and version. For released
> # versions, this URL points to the dashboard archive on the artifacts.elastic.co
> # website.
> #setup.dashboards.url:
>
> #============================== Kibana =====================================
>
> # Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
> # This requires a Kibana endpoint configuration.
> setup.kibana:
>
> # Kibana Host
> # Scheme and port can be left out and will be set to the default (http and 5601)
> # In case you specify and additional path, the scheme is required: http://localhost:5601/path
> # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
> #host: "localhost:5601"
> host: "10.200.100.101:5601"
>
> # Kibana Space ID
> # ID of the Kibana Space into which the dashboards should be loaded. By default,
> # the Default Space will be used.
> #============================= Elastic Cloud ==================================
>
> # These settings simplify using heartbeat with the Elastic Cloud (https://cloud.elastic.co/).
>
> # The cloud.id setting overwrites the `output.elasticsearch.hosts` and
> # `setup.kibana.host` options.
> # You can find the `cloud.id` in the Elastic Cloud web UI.
> #cloud.id:
>
> # The cloud.auth setting overwrites the `output.elasticsearch.username` and
> # `output.elasticsearch.password` settings. The format is `:`.
> #cloud.auth:
>
> #================================ Outputs =====================================
>
> # Configure what output to use when sending the data collected by the beat.
>
> #-------------------------- Elasticsearch output ------------------------------
> output.elasticsearch:
> # Array of hosts to connect to.
> hosts: ["10.200.100.101:9200"]
>
> # Optional protocol and basic auth credentials.
> #protocol: "https"
> #username: "elastic"
> #password: "changeme"
>
> #----------------------------- Logstash output --------------------------------
> #output.logstash:
> # The Logstash hosts
> #hosts: ["localhost:5044"]
>
> # Optional SSL. By default is off.
> # List of root certificates for HTTPS server verifications
> #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]
>
> # Certificate for SSL client authentication
> #ssl.certificate: "/etc/pki/client/cert.pem"
>
> # Client Certificate Key
> #ssl.key: "/etc/pki/client/cert.key"
>
>
> #================================ Processors =====================================
>
> # Configure processors to enhance or manipulate events generated by the beat.
>
> processors:
> - add_host_metadata: ~
> - add_cloud_metadata: ~
>
> #================================ Logging =====================================
>
> # Sets log level. The default log level is info.
> # Available log levels are: error, warning, info, debug
> #logging.level: debug
>
> # At debug level, you can selectively enable logging only for some components.
> # To enable all selectors use ["*"]. Examples of other selectors are "beat",
> # "publish", "service".
> #logging.selectors: ["*"]
>
> #============================== Xpack Monitoring ===============================
> # heartbeat can export internal metrics to a central Elasticsearch monitoring
> # cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
> # reporting is disabled by default.
>
> # Set to true to enable the monitoring reporter.
> #xpack.monitoring.enabled: false
>
> # Uncomment to send the metrics to Elasticsearch. Most settings from the
> # Elasticsearch output are accepted here as well. Any setting that is not set is
> # automatically inherited from the Elasticsearch output configuration, so if you
> # have the Elasticsearch output configured, you can simply uncomment the
> # following line.
> #xpack.monitoring.elasticsearch:
>
> #================================= Migration ==================================
>
> # This allows to enable migration aliases
> #migration.enabled: false
```
Everything runs on the same box. Elastic Search, Kibana and Heartbeat. Its configured with an IP instead of Local host so I could get to it remotely via web browser.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 28, 2019, 2:57pm UTC](https://discuss.elastic.co/t/heartbeat-7-seems-to-stop-running/170261/5 "2019-03-28T14:57:15Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.