not getting the status information.
Try stracing the munin-run, network capature or turning on the access logs on
/nginx_status just to be sure.
--
Daniel Black, Engineer @ Open Query (http://openquery.com)
Remote expertise & maintenance for MySQL/MariaDB server environments.
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
- Original Message -
> I might have misread the two answers here, but I get the impression
> that
> they're saying the exact opposite of each other.
If you analysed the responses and what you have I suspect you would of realised
that I was in error and the information you have and the d
- Original Message -
> I was wondering if someone could confirm that requests resulting in a
> 404
> response are by default logged to error.log at error level "error".
>
> Is that normal, or is there some piece of configuration I am missing
> that
> will stop them from being logged to er
de nginx 0.7.67-3+squeeze3 1.4.1-1~squeeze
I definitely restarted the nginx-1.4.1 with no remnants of 0.7.67 around and
haven't had the troubles when I re-tested.
Thanks for the fix Maxim and digging up this changelog entry.
Looking forward to putting it into product
meout 15;
> proxy_connect_timeout 3;
> proxy_next_upstream error timeout invalid_header http_500 http_502
> http_503 http_504 http_404;
>
> location ~ ^/img/(.*)
> {
> expires 2592000;
> add_header Cache-Control public;
> alias /var/www/live_site_resources/$1;
> error_page 40
A request for /img/file_doesnt_exist.jpg results in the backend server
(192.168.129.90) getting continuous requests for the same file (which doesn't
exist there either so 404 each time), while the original requester waits and
nginx keeps asking the backend the same.
I'm using the nginx-1.4.1 f
