You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
The text was updated successfully, but these errors were encountered: