Opened 7 years ago

Closed 7 years ago

#1495 closed defect (worksforme)

cutom "log_format" can't be used in server block that is included from another file

Reported by: Renkas@… Owned by:
Priority: major Milestone:
Component: nginx-core Version: 1.13.x
Keywords: log_format Cc:
uname -a: Linux 2c6f6973cfbc 4.9.60-linuxkit-aufs #1 SMP Mon Nov 6 16:00:12 UTC 2017 x86_64 GNU/Linux
nginx -V: ginx version: nginx/1.13.9
built by gcc 6.3.0 20170516 (Debian 6.3.0-18)
built with OpenSSL 1.1.0f 25 May 2017
TLS SNI support enabled
configure arguments: --prefix=/etc/nginx --sbin-path=/usr/sbin/nginx --modules-path=/usr/lib/nginx/modules --conf-path=/etc/nginx/nginx.conf --error-log-path=/var/log/nginx/error.log --http-log-path=/var/log/nginx/access.log --pid-path=/var/run/nginx.pid --lock-path=/var/run/nginx.lock --http-client-body-temp-path=/var/cache/nginx/client_temp --http-proxy-temp-path=/var/cache/nginx/proxy_temp --http-fastcgi-temp-path=/var/cache/nginx/fastcgi_temp --http-uwsgi-temp-path=/var/cache/nginx/uwsgi_temp --http-scgi-temp-path=/var/cache/nginx/scgi_temp --user=nginx --group=nginx --with-compat --with-file-aio --with-threads --with-http_addition_module --with-http_auth_request_module --with-http_dav_module --with-http_flv_module --with-http_gunzip_module --with-http_gzip_static_module --with-http_mp4_module --with-http_random_index_module --with-http_realip_module --with-http_secure_link_module --with-http_slice_module --with-http_ssl_module --with-http_stub_status_module --with-http_sub_module --with-http_v2_module --with-mail --with-mail_ssl_module --with-stream --with-stream_realip_module --with-stream_ssl_module --with-stream_ssl_preread_module --with-cc-opt='-g -O2 -fdebug-prefix-map=/data/builder/debuild/nginx-1.13.9/debian/debuild-base/nginx-1.13.9=. -specs=/usr/share/dpkg/no-pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fPIC' --with-ld-opt='-specs=/usr/share/dpkg/no-pie-link.specs -Wl,-z,relro -Wl,-z,now -Wl,--as-needed -pie'

Description

I'm trying to use custom log format that is required in Amplify to get extended info: ​https://github.com/nginxinc/nginx-amplify-doc/blob/master/amplify-guide.md#additional-nginx-metrics

The error I'm getting:

[emerg] unknown log format "main_ext" in /etc/nginx/conf.d/00-main.conf:35

Simplified config:

# /etc/nginx/nginx.conf
http {
    log_format main_ext '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for" '
                      '"$host" sn="$server_name" '
                      'rt=$request_time '
                      'ua="$upstream_addr" us="$upstream_status" '
                      'ut="$upstream_response_time" ul="$upstream_response_length" '
                      'cs=$upstream_cache_status';

    include /etc/nginx/conf.d/*.conf;
}

# /etc/nginx/conf.d/00-main.conf
server {
    access_log            /var/log/nginx/access.log main_ext;
    error_log             /var/log/nginx/error.log warn;
}

I also tried this on 1.12 branch and the result is the same

Change History (1)

comment:1 by Maxim Dounin, 7 years ago

Resolution: → worksforme
Status: new → closed

There is something wrong with your configuration. The one identical to your simplified configuration, cut-n-pasted with minimal path changes and the events{} section added, works fine here:

$ nginx -T -c /tmp/nginx/nginx.conf
nginx: the configuration file /tmp/nginx/nginx.conf syntax is ok
nginx: configuration file /tmp/nginx/nginx.conf test is successful
# configuration file /tmp/nginx/nginx.conf:
events {}

http {
    log_format main_ext '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" "$http_x_forwarded_for" '
                      '"$host" sn="$server_name" '
                      'rt=$request_time '
                      'ua="$upstream_addr" us="$upstream_status" '
                      'ut="$upstream_response_time" ul="$upstream_response_length" '
                      'cs=$upstream_cache_status';

    include /tmp/nginx/conf.d/*.conf;
}

# configuration file /tmp/nginx/conf.d/00-main.conf:
server {
    access_log            /tmp/nginx/access.log main_ext;
    error_log             /tmp/nginx/error.log warn;
}

In particular, I would recommend checking the configuration for missing ; before the log_format. In some cases missing semicolon still results in a syntactically valid configuration, yet a different one.

Note: See TracTickets for help on using tickets.