Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

Route /backend_checker does not response as expected #102

Open
sontags opened this issue Nov 13, 2019 · 0 comments
Open

Route /backend_checker does not response as expected #102

sontags opened this issue Nov 13, 2019 · 0 comments

Comments

@sontags
Copy link

sontags commented Nov 13, 2019

/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).

@sontags sontags changed the title Route ''`` Route /backend_checker does not response as expected Nov 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant