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.

Sign up for GitHub

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

Jump to bottom

Route /backend_checker does not response as expected #102

Open

sontags opened this issue Nov 13, 2019 · 0 comments

sontags commented Nov 13, 2019 •

edited

/backend_checker (see https://github.com/geoadmin/service-print/blob/master/print3/main.py#L77) seems to abort() on every request. I tried to reproduce manually but was not successful: calling the handler via nginx returns the error:

# curl [ip]:8009/backend_checker
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>503 Service Unavailable</title>
<h1>Service Unavailable</h1>
<p>Incomprehensible answer. tomcat is probably not ready yet.</p>

Calling the Tomcat check directly returns the required ok:

# curl [ip]:8011/service-print-main/checker 
OK

This causes all our Load Balancer to consider all targets "unhealthy" (which luckily forces the LB to server all backends).

The text was updated successfully, but these errors were encountered:

sontags changed the title ~~Route ''``~~ Route /backend_checker does not response as expected

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment