#551 closed defect (invalid)
Start Failure; Invalid Option with Map Expression in nginx.conf
| Reported by: | sah62.pip.verisignlabs.com | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | nginx-core | Version: | 1.4.x |
| Keywords: | Cc: | ||
| uname -a: | Linux impala 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | ||
| nginx -V: |
nginx version: nginx/1.4.6 (Ubuntu)
built by gcc 4.8.2 (Ubuntu 4.8.2-16ubuntu6) TLS SNI support enabled configure arguments: --with-cc-opt='-g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -D_FORTIFY_SOURCE=2' --with-ld-opt='-Wl,-Bsymbolic-functions -Wl,-z,relro' --prefix=/usr/share/nginx --conf-path=/etc/nginx/nginx.conf --http-log-path=/var/log/nginx/access.log --error-log-path=/var/log/nginx/error.log --lock-path=/var/lock/nginx.lock --pid-path=/run/nginx.pid --http-client-body-temp-path=/var/lib/nginx/body --http-fastcgi-temp-path=/var/lib/nginx/fastcgi --http-proxy-temp-path=/var/lib/nginx/proxy --http-scgi-temp-path=/var/lib/nginx/scgi --http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit --with-ipv6 --with-http_ssl_module --with-http_stub_status_module --with-http_realip_module --with-http_addition_module --with-http_dav_module --with-http_geoip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_spdy_module --with-http_sub_module --with-http_xslt_module --with-mail --with-mail_ssl_module --add-module=/build/buildd/nginx-1.4.6/debian/modules/nginx-auth-pam --add-module=/build/buildd/nginx-1.4.6/debian/modules/nginx-dav-ext-module --add-module=/build/buildd/nginx-1.4.6/debian/modules/nginx-echo --add-module=/build/buildd/nginx-1.4.6/debian/modules/nginx-upstream-fair --add-module=/build/buildd/nginx-1.4.6/debian/modules/ngx_http_substitutions_filter_module |
||
Description
I recently upgraded a server from Ubuntu 12.04 LTS to 14.04 LTS and noticed that nginx was not starting automatically. Attempts to start it manually produce the following:
$ sudo service nginx start $ sudo service nginx restart * Restarting nginx nginx [fail] $
I can start the server successfully from the command line with "sudo nginx". Testing the configuration produces no error:
$ sudo nginx -t nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful $
I modified /etc/init.d/nginx to produce more information and found the following:
nginx: invalid option: "~*(crawl|Google|Slurp|bingbot|tracker|click|parser|spider|msnbot|Gigabot)"
This is the offending directive in my nginx.conf file:
map $http_user_agent $is_bot {
default 0;
~*(crawl|Google|Slurp|bingbot|tracker|click|parser|spider|msnbot|Gigabot) 1;
}
It turns out that the string "pid" in "spider" is causing the start failure. If I change the regex to "s.ider" or "s\160ider" I can start the server successfully.
Change History (2)
comment:1 by , 11 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 11 years ago
Thanks! Yup, the 14.04 version of /etc/init.d/nginx does this:
PID=$(awk -F'[ \t;]+' '/[^#]pid/ {print $2}' /etc/nginx/nginx.conf)
Note:
See TracTickets
for help on using tickets.
This doesn't looks like a problem in nginx. Rather, it's an incorrect assumption in init.d script you use - looks like it tries to grep nginx.conf for the "pid" directive, and fails to do it properly. Ask your package maintainer for a refund.