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

Add baggageclaim monit restart when healthcheck fails #5

Open
kcmannem opened this issue Oct 17, 2018 · 0 comments
Open

Add baggageclaim monit restart when healthcheck fails #5

kcmannem opened this issue Oct 17, 2018 · 0 comments

Comments

@kcmannem
Copy link
Member

The monit config for the baggageclaim job relies on a pid file to ensure the job is alive. This can lead to false positives in determining a healthy system (ran into a scenario where baggageclaim's stderr logs 2018/10/11 20:32:16 http: Accept error: accept tcp 0.0.0.0:7788: accept4: too many open files; retrying in 5ms and closes its socket but monit lists the process as running).

We might want to consider giving monit a health endpoint so it can successfully handle the lifecycle. Here is an example from the UAA-Release.

      if failed port <%= active_uaa_port %> protocol http
        request "/healthz"
        with timeout 60 seconds for 64 cycles
      then restart
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

1 participant