Re: 404s logged in error.log?

Perfect, that clarified it, thank you. I will turn off log_not_found and stick to having 404s just in my access logs, to be on the safe side. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,239307,239312#msg-239312 ___ nginx mailing list nginx

Re: 404s logged in error.log?

- 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

Re: 404s logged in error.log?

I might have misread the two answers here, but I get the impression that they're saying the exact opposite of each other. Here's a sample (redacted) error message I'm seeing in error.log when doing a GET on a file that doesn't exist: 2013/05/18 02:21:27 [error] 11619#0: *417 open() "/var/www/mysit

Re: 404s logged in error.log?

Hey, > Is that normal, or is there some piece of configuration I am missing that > will stop them from being logged to error.log? I figured 404s would be an > un-exceptional event that doesn't require error logging, but perhaps I'm > simply not handling that situation correctly in my configuration

Re: 404s logged in error.log?

- 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

404s logged in error.log?

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 error.log? I figured 404s would be an un-excep

Re: Permissions check

> I just updated nginx and was warned about permissions. Are these appropriate: > > /var/log/nginx: > drwxr-x--- root root > > /var/lib/nginx/tmp and /var/lib/nginx/tmp/*: > drwx-- nginx nginx > > - Grant Whoops, please make that: /var/lib/nginx/tmp and /var/lib/nginx/tmp/*: drwx-- apach

Permissions check

I just updated nginx and was warned about permissions. Are these appropriate: /var/log/nginx: drwxr-x--- root root /var/lib/nginx/tmp and /var/lib/nginx/tmp/*: drwx-- nginx nginx - Grant ___ nginx mailing list nginx@nginx.org http://mailman.nginx

Re: Choosing source-address for upstream connections

On Fri, 17 May 2013 17:17:20 +0400 Ruslan Ermilov wrote: > On Fri, May 17, 2013 at 02:57:00PM +0200, Bruno Prémont wrote: > > Is there a way to tell nginx to use a specific address when talking to > > an upstream? > > > > I would like to do something like: > > > > upstream bla { > > server [

Re: Choosing source-address for upstream connections

On Fri, May 17, 2013 at 02:57:00PM +0200, Bruno Prémont wrote: > Is there a way to tell nginx to use a specific address when talking to > an upstream? > > I would like to do something like: > > upstream bla { > server [D0C::1234]:8080 src [D0C::beaf]; > server 1.2.3.4:8080 src 1.2.3.5

Re: Add [nginx] to subject lines on this mailing list?

Hello! On Thu, May 16, 2013 at 11:07:28AM -0400, Daniel Griscom wrote: > At 3:34 PM +0200 5/16/13, René Neumann wrote: > >Am 16.05.2013 15:18, schrieb Jim Ohlstein: > >> I think what Maxim was alluding to is that any decent email client will > >> sort messages for you based on headers if you set

Choosing source-address for upstream connections

Is there a way to tell nginx to use a specific address when talking to an upstream? I would like to do something like: upstream bla { server [D0C::1234]:8080 src [D0C::beaf]; server 1.2.3.4:8080 src 1.2.3.5; server upstream.example.tld src site.example.tld; } My system h

Re: Handling nginx's too many open files even I have the correct ulimit

Try setting worker_rlimit_nofile Jader H. 2013/5/15 0liver > I'm facing the same problem here, but I found much lower settings on our > machine (a VPS running Ubuntu 12.04): > > # the hard limit of open files > www-data@215247:~$ ulimi