Forum: NGINX Status code 000 in the logs

2974d09ac2541e892966b762aad84943?d=identicon&s=25 monkeybrain (Guest)
on 2013-09-16 18:22
(Received via mailing list)
What does status code 000 mean in the Nginx logs? I have the following
in
the config:

        location  =  /get-img.pl
        {
            limit_req  zone=slow  burst=10;
            proxy_pass  http://service_perl;
        }

get-img.pl generates an image, writes it to disk and then returns
"X-Accel-Redirect" to the image. Everything seems to be working just
fine, I
see delayed responses because of limit_req in the logs (with code 200).
Sometimes there are responses with code 503 for "greedy" clients that
exceed
the burst=10 parameter. All as expected.

However, occasionally I see a bunch of requests (around 5 to 20 within a
few
seconds of each other) with status code 000 and 0 for the body size in
the
logs. They are always from the same IP address for the entire bunch, so
I'm
guessing it's requests that already went through internal
"X-Accel-Redirect"
redirect and then something happened. Connection aborted? Something
else?
Why not status code 503? That's where you come in with a helpful
explanation. :)

In case it is relevant:
nginx version: nginx/1.4.2
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-54)
TLS SNI support disabled
configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx
--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_realip_module
--with-http_addition_module
--with-http_sub_module --with-http_dav_module --with-http_flv_module
--with-http_mp4_module --with-http_gunzip_module
--with-http_gzip_static_module --with-http_random_index_module
--with-http_secure_link_module --with-http_stub_status_module
--with-mail
--with-mail_ssl_module --with-file-aio --with-ipv6 --with-cc-opt='-O2 -g
-pipe -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector
--param=ssp-buffer-size=4 -m64 -mtune=generic'

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,242893,242893#msg-242893
A8108a0961c6087c43cda32c8616dcba?d=identicon&s=25 Maxim Dounin (Guest)
on 2013-09-16 18:47
(Received via mailing list)
Hello!

On Mon, Sep 16, 2013 at 12:22:17PM -0400, monkeybrain wrote:

> "X-Accel-Redirect" to the image. Everything seems to be working just fine, I
> explanation. :)
It happens if client closes connection whily waiting for limit_req
delay, and correct code to log is 499 (client closed request).
This is already fixed in 1.5.3 with the following commit:

http://hg.nginx.org/nginx/rev/aadfadd5af2b

--
Maxim Dounin
http://nginx.org/en/donation.html
Please log in before posting. Registration is free and takes only a minute.
Existing account

NEW: Do you have a Google/GoogleMail, Yahoo or Facebook account? No registration required!
Log in with Google account | Log in with Yahoo account | Log in with Facebook account
No account? Register here.