Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Monit fails to detect when ingestor_syslog process stops listening on port 443 #196

Open
mrdavidlaing opened this issue Dec 15, 2015 · 5 comments

Comments

@mrdavidlaing
Copy link
Member

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.

@dpb587
Copy link
Contributor

dpb587 commented Dec 16, 2015

Interesting; haven't experienced this yet. Maybe https://mmonit.com/monit/documentation/monit.html#CONNECTION-TESTING will be useful as a workaround?

@mrdavidlaing
Copy link
Member Author

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

@t2sa
Copy link
Contributor

t2sa commented Nov 16, 2016

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

@cromega
Copy link
Contributor

cromega commented Nov 17, 2016

We had all sorts of issues with this. 468015a

@t2sa
Copy link
Contributor

t2sa commented Jan 19, 2017

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants