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
When the health check script fails due to Nginx unavailability, it triggers a chain of events that causes Nginx to exit, resulting in a deadlock instead of retrying.
this triggers monit to restart cloud_controller_ng
that triggers nginx to exit due to no one is listening to the socket
Steps to Reproduce
Delay cloud_controller_ng start that it is not listening to the socket.
Expected result
Health-check script to retry when Nginx is not listening instead of exiting.
Current result
The current logic of the health check script triggers monit to restart the cloud_controller_ng web server, causing deadlock.
Possible Fix
Make the health check script stay in the retry loop when the curl exit code is 7 to tolerate nginx availability.
Ensure that the health check process starts only after both web server and Nginx are online and ready by investigating and correcting monit dependencies.
The content you are editing has changed. Please copy your edits and refresh the page.
The text was updated successfully, but these errors were encountered:
a-b
changed the title
Healthcheck script exits when nginx is not available resulting deadlock.
Healthcheck script exits when nginx is not available resulting deadlock
Dec 27, 2023
a-b
added a commit
to a-b/capi-release
that referenced
this issue
Dec 27, 2023
Addresses cloudfoundry#364
If Nginx restarts, the healthcheck curl exits with code 7, triggering
another Nginx restart. To avoid this, we need stay in the loop and retry
to allow Nginx to complete the restart.
Issue
When the health check script fails due to Nginx unavailability, it triggers a chain of events that causes Nginx to exit, resulting in a deadlock instead of retrying.
Context
cloud_controller_ng
nginx
to exit due to no one is listening to the socketSteps to Reproduce
Delay
cloud_controller_ng
start that it is not listening to the socket.Expected result
Health-check script to retry when Nginx is not listening instead of exiting.
Current result
The current logic of the health check script triggers monit to restart the
cloud_controller_ng
web server, causing deadlock.Possible Fix
Tasks
The text was updated successfully, but these errors were encountered: