Custom Query (2297 matches)

nginx is incorrectly honoring user directive in the configuration file. When only user is given, nginx runs under nobody group. Documents state that, it should use the group, with the same name as the user. This issue may only be present for fastcgi & cgi.

Details: I'm running a Debian stable server with fcgiwrap & nginx. fcgiwrap is set to run under www-data:www-data and nginx set to www-data user via "user www-data;" directive. I've set up gitweb for repository displaying. To set up I added www-data to git group and set up gitweb. But gitweb got file access errors without any log entry or trace. After changing user directive to "user www-data www-data;" and restarting nginx, problem vanished. Documents[1] state that the second www-data shouldn't be necessary in normal cases. Maybe some parts of the code doesn't interpret the directive as they should.

[1]​http://wiki.nginx.org/CoreModule#user

Nginx / 1.4.1 set different limit_conn is not effective in multiple locations.

config file: limit_conn_zone $binary_remote_addr zone=test:10m; server {

location /a/{

limit_conn test 1;

}

}

My Case: a upstream named "readingjoy" is not defined in nginx.conf,and there is a defined server use upstream "readingjoy",this is a wrong config. but sometime.when I run nginx -t ,the result is the one of 1.long time process,return nginx: the configuration file /usr/local/nginx/conf/nginx.conf syntax is ok nginx: configuration file /usr/local/nginx/conf/nginx.conf test is successful 2.fast time process,return nginx: [emerg] host not found in upstream "readingjoy" in /usr/local/nginx/conf/nginx.conf:98 nginx: configuration file /usr/local/nginx/conf/nginx.conf test failed this is a bug,right?