Hi all,
I usually start Heartbeat (and other beats) with the following command:
nohup ./beatname >/dev/null 2>&1 &
but heartbeat stops after a while (random period). I checked on debug logs and this is the message I found:
2019-09-26T13:00:36.933+0200 DEBUG [service] service/service.go:55 Received sighup, stopping
Of course, sighup is related to an iterrupt of the process related to the user disconnection from the terminal, but this is strange cause sometimes heartbeat runs for hour after user disconnection.
NB: Elasticsearch and Kibana are running in the same server and are started using the same command, but they are not stopped.
According to your experience what could be the cause of this issue?
Thanks
Well, I have performed a brief check on all main ELK components about their signal managements and I noticed that beats, apm and node (Kibana) handle sighup command by theirself, as can be seen looking at the last SigIn digit (it should be a number, instead of 0)
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.