Open mrdavidlaing opened 8 years ago
Interesting; haven't experienced this yet. Maybe https://mmonit.com/monit/documentation/monit.html#CONNECTION-TESTING will be useful as a workaround?
Yep - that is the plan.
Although worth mentioning that BOSH uses monit 5.2 and those docs are for monit 5.15. So we'll need to double check the syntax against man monit
Tested something like this in monit and it worked fine. Hope this could be included in the next release. if failed port 443 then restart
We had all sorts of issues with this. https://github.com/logsearch/logsearch-boshrelease/commit/468015a71e3b93605bc03a8c752b02de9f685730
Seems to work great for our case. Hope this option could be provided as a configurable value for people that would like to keep it.
If logstash detects a crash in the TCP input and shuts it down; logstash continues to run (an monit thinks everything is ok) even though logstash is no longer accepting traffic.
This should be detected as a failure condition by monit and logstash should be restarted.