We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Nginx log (possibly trouble with overlay network)
2020/03/15 20:26:10 [error] 6#6: *4885 connect() failed (113: No route to host) while connecting to upstream, client: 10.0.0.2, server: , request: "GET /vchains/2000/metrics HTTP/1.1", upstream: "http://10.0.2.33:8080/metrics", host: "52.60.147.59" 10.0.0.2 - - [15/Mar/2020:20:26:10 +0000] "GET /vchains/2000/metrics HTTP/1.1" 502 173 "-" "-" "-" 2020/03/15 20:26:10 [error] 6#6: *4893 connect() failed (113: No route to host) while connecting to upstream, client: 10.0.0.2, server: , request: "GET /vchains/2000/metrics HTTP/1.1", upstream: "http://10.0.2.33:8080/metrics", host: "52.60.147.59"
Recovers by itself, but still raises concerns. Maybe giving a shorter timeout to the resolver in the nginx config should make the problem go away.
The text was updated successfully, but these errors were encountered:
Maybe it's actually connectivity problem between the Docker swarm nodes, needs more tests:
https://stackoverflow.com/questions/58632940/docker-swarm-overlay-connect-no-route-to-host
Sorry, something went wrong.
No branches or pull requests
Nginx log (possibly trouble with overlay network)
Recovers by itself, but still raises concerns. Maybe giving a shorter timeout to the resolver in the nginx config should make the problem go away.
The text was updated successfully, but these errors were encountered: