access_log with variable is a features that I requested and was
waiting anxious, but I try here and the access logs simple stop
working.
This is what I did:
access_log /qi/nginx/logs/$host.log;
Any body succeed?
access_log with variable is a features that I requested and was
waiting anxious, but I try here and the access logs simple stop
working.
This is what I did:
access_log /qi/nginx/logs/$host.log;
Any body succeed?
On Mon, Jun 30, 2008 at 12:13:09PM -0300, Marcos N. wrote:
access_log with variable is a features that I requested and was
waiting anxious, but I try here and the access logs simple stop
working.
This is what I did:
access_log /qi/nginx/logs/$host.log;
Can nginx user write to /qi/nginx/logs/ ?
To make sure, I make it 777, but I don´t think that´s the problem,
cause the access logs are created as root user.
What could be?
On Mon, Jun 30, 2008 at 12:27:44PM -0300, Marcos N. wrote:
To make sure, I make it 777, but I don?t think that?s the problem,
cause the access logs are created as root user.
What could be?
I’ve just found that without open_log_file_cache directive worker exits
with signal. Try
open_log_file_cache max=1000;
I found that log files with variable, are created with nginx worker
user, in my case, nobody:nogroup
Now it´s working, without need to set open_log_file_cache max=1000;
On Mon, Jun 30, 2008 at 12:49:52PM -0300, Marcos N. wrote:
I found that log files with variable, are created with nginx worker
user, in my case, nobody:nogroup
Yes, they are created by worker processes only.
Now it?s working, without need to set open_log_file_cache max=1000;
The attached patch fixes signal 10.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.
Sponsor our Newsletter | Privacy Policy | Terms of Service | Remote Ruby Jobs