Nginx error log log_format variables

nginx

I want to specify log format for nginx error logs, but I could not find any variable for errors.
I found required variables for access logs like below:

log_format test'$remote_addr - $remote_user [$time_local] '
                       '"$request" $status $bytes_sent '
                       '"$http_referer" "$http_user_agent" "$gzip_ratio"';

Is there any $error, $error_body or something like this that could be matched for errors?

Best Answer

No, $status is the one you want. It contains both erroneous and successful statuses. You should grep the access_log for statuses indicating the errors and the error_log for their causes. I guess you're misunderstanding the concept of access and error log separation.

Related Solutions

Nginx – Trouble with nginx and serving from multiple directories under the same domain

The root directive is the problem here. Quote from the doc:

note: Keep in mind that the root will still append the directory to the request so that a request for "/i/top.gif" will not look in "/spool/w3/top.gif" like might happen in an Apache-like alias configuration where the location match itself is dropped. Use the alias directive to achieve the Apache-like functionality.

Basically, only use root for real roots: if the content is to be at / use root. If it's going to end on a subfolder, use alias:

location  /map/ {
  alias  /home/user/public_html/map/;
}

Also check what user nginx is running as and make sure that this user can access /home/user/public_html/map

Nginx – Change Nginx document root from /usr/share/nginx to /etc/nginx

nginx docs state the following about the --prefix configure command:

--prefix=path — defines a directory that will keep server files. This same directory will also be used for all relative paths set by configure (except for paths to libraries sources) and in the nginx.conf configuration file. It is set to the /usr/local/nginx directory by default.

Thus, all relative paths are computed against this one.

To check the prefix value for the binary you use, check nginx -V.

In your case, I see several options, from best to worst:

Use absolute paths (either directly or prefixing existing paths with a variable). A simple script would make it easy to transform the original paths into propers ones, even launched as a 'post-hook' on file drop by the fellas
Create symbolic links in the computed locations referring to the expected one
Build nginx binaries manually, configuring that command as you see fit

Best Answer

Related Solutions

Nginx – Trouble with nginx and serving from multiple directories under the same domain

Nginx – Change Nginx document root from /usr/share/nginx to /etc/nginx

Related Topic