>Hi, >You should compile upstream hash module which cep12 patched, See: >https://github.com/cep21/nginx_upstream_hash/tree/support_http_healthchecks nginx-1.0.5 was compiled with both patches: root@true:/tmp/nginx-1.0.5# patch -p0 < ../nginx_upstream_hash-0.3.1/nginx.patch patching file src/http/ngx_http_upstream.h Hunk #1 succeeded at 106 (offset 1 line). root@true:/tmp/by gidrobaton - Nginx Mailing List - English
>But in my case all inversely - :81 and :82 are good - they answer "HTTP/1.1 200 OK\r\n" >and 22 is bad - he close connection without answer Sorry, in states all right - this paragraph used mistakenly But nginx NOT mark 172.16.0.130:22 as wrong server and unsuccessfully trying to redirect browser request to 22 tcp-portby gidrobaton - Nginx Mailing List - English
Good day! I have same problem with nginx-1.0.5 (and nginx-1.0.0) root@true:/tmp/nginx-1.0.5# ./configure --add-module=/tmp/nginx_upstream_hash-0.3.1/ --add-module=/tmp/healthcheck_nginx_upstreams/ --with-debug error_log logs/error_log debug_http; upstream backend { ip_hash; server 172.16.0.130:81; server 172.16.0.130:82; server 172.16.0.130:22; #by gidrobaton - Nginx Mailing List - English