# Status 0 on proxy MISS

**URL:** <https://www.ruby-forum.com/t/status-0-on-proxy-miss/216317>\
**Category:** NGINX\
**Created:** [February 1, 2012, 11:21am UTC](https://www.ruby-forum.com/t/status-0-on-proxy-miss/216317 "2012-02-01T11:21:54Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![luislavena](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/l/0ea827/32.png) [@luislavena](https://www.ruby-forum.com/u/luislavena)\
**Post date:** [February 1, 2012, 11:21am UTC](https://www.ruby-forum.com/t/status-0-on-proxy-miss/216317/1 "2012-02-01T11:21:54Z")

</div>

Hello.

I’m using nginx as proxy for an apache.  
Somtimes, on a MISS, the logged status is 0, instead of 200 (or anything  
else). The log format is configured like this:

log\_format cache '[$time\_local] $remote\_addr - $request\_time - ’  
'$upstream\_cache\_status ’  
'Cache-Control: $upstream\_http\_cache\_control ’  
'Expires: $upstream\_http\_expires ’  
'"$request" ($status) ’  
'"$http\_user\_agent" ';

The value 0 occurs for the variable $status

Has anyone any idea, what the status 0 means or why it occurs?

Kind regards

Andreas

---

<div class="post-metadata">

**Author:** ![Andreas\_Martin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/dec6dc/32.png) [@Andreas\_Martin](https://www.ruby-forum.com/u/Andreas_Martin)\
**Post date:** [February 2, 2012, 9:21am UTC](https://www.ruby-forum.com/t/status-0-on-proxy-miss/216317/2 "2012-02-02T09:21:27Z")

</div>

Hello.

I think I found the cause of this error.  
In the error log, there are corresponding entries with “Too many open  
files”. I’ll increase this limit and check if the status 0 occurs again  
or (hopefully) not.

Andreas

Am 01.02.2012 09:39, schrieb Andreas Martin:

---

<div class="post-metadata">

**Author:** ![Andreas\_Martin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/a/dec6dc/32.png) [@Andreas\_Martin](https://www.ruby-forum.com/u/Andreas_Martin)\
**Post date:** [February 7, 2012, 3:35pm UTC](https://www.ruby-forum.com/t/status-0-on-proxy-miss/216317/3 "2012-02-07T15:35:03Z")

</div>

Hi.

After increasing the open files limits on OS level and increasing the  
values for worker\_rlimit\_nofile and worker\_connections in nginx.conf  
according to our needs, the error does not longer occur.

Regards

Andreas

Am 02.02.2012 09:20, schrieb Andreas Martin: