Having this issue on production. We have installed filebeat using tar file. After starting, in few hours it's stopping without any error. On our other lower environment we have installed using rpm and never seen this issue. Kindly let me know, what can be the problem?
Hm.. it's really weird. You can try to enable debug logging on one of your production instances. Which version of filebeat did you install?
version 7.5
As we are running using nohup, i didn't see any error in nohup.out, when filebeat stops. Normally when we kill the filebeat process, the same logs generated in nohup. There is no change i see there. Will check after enabling debug log once.
Is there any chance that you can try with the latest version? 7.5 is getting old.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.