Opened 8 years ago
Closed 8 years ago
#1086 closed defect (invalid)
Connection failure on upstream health check repeatedly reports at error log level, other unhealthy peers report at info log level
| Reported by: | Owned by: | ||
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | other | Version: | 1.9.x |
| Keywords: | logging | Cc: | mpawelsk@… |
| uname -a: | Linux lx02096.starbucks.net 2.6.32-573.18.1.el6.x86_64 #1 SMP Wed Jan 6 11:20:49 EST 2016 x86_64 x86_64 x86_64 GNU/Linux | ||
| nginx -V: |
nginx version: nginx/1.11.3 (nginx-plus-r10)
built by gcc 4.4.7 20120313 (Red Hat 4.4.7-17) (GCC) built with OpenSSL 1.0.1e-fips 11 Feb 2013 TLS SNI support enabled configure arguments: --build=nginx-plus-r10 --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx --modules-path=/usr/lib64/nginx/modules --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock --http-client-body-temp-path=/var/cache/nginx/client_temp --http-proxy-temp-path=/var/cache/nginx/proxy_temp --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp --http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx --group=nginx --with-http_ssl_module --with-http_v2_module --with-http_realip_module --with-http_addition_module --with-http_sub_module --with-http_dav_module --with-http_flv_module --with-http_mp4_module --with-http_gzip_static_module --with-http_gunzip_module --with-http_random_index_module --with-http_secure_link_module --with-http_stub_status_module --with-http_auth_jwt_module --with-http_auth_request_module --with-http_slice_module --with-mail --with-mail_ssl_module --with-threads --with-file-aio --with-ipv6 --with-stream --with-stream_ssl_module --with-stream_geoip_module=dynamic --with-http_f4f_module --with-http_session_log_module --with-http_hls_module --with-http_xslt_module=dynamic --with-http_geoip_module=dynamic --with-http_image_filter_module=dynamic --with-http_perl_module=dynamic --add-dynamic-module=ngx_devel_kit-0.3.0 --add-dynamic-module=set-misc-nginx-module-0.31 --add-dynamic-module=lua-nginx-module-0.10.6 --add-dynamic-module=headers-more-nginx-module-0.31 --add-dynamic-module=nginx-rtmp-module-1.1.9 --add-dynamic-module=njs-0.1.1/nginx --add-dynamic-module=passenger-5.0.30/src/nginx_module --add-dynamic-module=wallarm/module --with-cc-opt='-O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic' |
||
Description
If a server is hard down (no connectivity/connection refused) then Nginx logging reports this at error level and repeats at every health check interval. All other unhealthy servers (inappropriate HTTP code response, no match to dynamic health check) is reported at Info log level once, upon health state change. Seems like connection refused should be Info level, else a failing host pollutes the logs every time the health check fire due to higher priority on Error log level.
2016/09/28 10:21:39 [notice] 17182#17182: OS: Linux 2.6.32-573.18.1.el6.x86_64
2016/09/28 10:21:39 [notice] 17182#17182: getrlimit(RLIMIT_NOFILE): 1024:4096
2016/09/28 10:21:39 [notice] 17183#17183: start worker processes
2016/09/28 10:21:39 [notice] 17183#17183: start worker process 17184
2016/09/28 10:21:39 [notice] 17183#17183: start worker process 17185
2016/09/28 10:21:39 [notice] 17183#17183: start worker process 17186
2016/09/28 10:21:39 [notice] 17183#17183: start worker process 17187
2016/09/28 10:21:39 [error] 17184#17184: connect() failed (111: Connection refused) while connecting to upstream, health check of peer 10.12.6.249:80 in upstream "someupstream"
2016/09/28 10:21:39 [info] 17184#17184: peer is unhealthy while connecting to upstream, health check of peer 10.12.6.249:80 in upstream "someupstream"
2016/09/28 10:21:49 [error] 17184#17184: connect() failed (111: Connection refused) while connecting to upstream, health check of peer 10.12.6.249:80 in upstream "someupstream"
This is a bug tracker for opensource nginx, so I'm closing this ticket.
Please consider using nginx-plus support channels for further questions about nginx-plus.
I'll ask sales engineers to contact you directly.