addis_a
December 16, 2014, 11:37am
1
Hello;
for many months I’ve been running the config shown here:
This morning, I apt-get upgraded and got nginx 1.7.8 and a load of dead
After a whole load of panicking and commenting one line out at a time, I
location ~ /purge(/.*) {
If I comment that out, I can start up wordpress and nginx -t doesn’t
I can’t see anything obvious in the release notes that would cause this,
Linux 3.16.0-28-generic #37-Ubuntu SMP Mon Dec 8 17:22:00 UTC 2014 i686
nginx version: nginx/1.7.8
Posted at Nginx Forum:
On Tuesday 16 December 2014 05:36:38 talkingnews wrote:
location ~ /purge(/.*) {
If I comment that out, I can start up wordpress and nginx -t doesn’t core
I can’t see anything obvious in the release notes that would cause this,
2014-12-23 VERSION 2.3
* Fix compatibility with nginx-1.7.9+.
2014-12-02 VERSION 2.2
* Fix compatibility with nginx-1.7.8+.
2014-05-19
* Fix build on Solaris with SunCC (Solaris Studio).
Reported by Jussi Sallinen.
2013-03-19 VERSION 2.1
* When enabled, cache purge will now catch all requests with
PURGE (or specified) method, even if cache isn't configured.
Previously, it would pass such requests to the upstream.
2012-12-07 VERSION 2.0
* Add alternative "same location" syntax.
From CloudFlare.
2012-07-02 VERSION 1.6
show original
Since you’re using a lot of 3rd-party modules it’s a good idea to
wbr, Valentin V. Bartenev
ngx_cache_purge/CHANGES at master · FRiCKLE/ngx_cache_purge · GitHub
Since you’re using a lot of 3rd-party modules it’s a good idea to
Not sure how I can do this when I’m usingIndex of /nginx/development/ubuntu utopic main
As far as I can see, the nginx-extras package was built 15 hours ago.
2014-12-02 VERSION 2.2
From nginx -V
So, it SHOULD be up to date. It sounds like I need to post a ticket on
opened 11:20AM - 16 Dec 14 UTC
closed 02:15PM - 16 Dec 14 UTC
for many months I've been running the config shown here: https://rtcamp.com/word… press-nginx/tutorials/single-site/fastcgi-cache-with-purging/
This morning, I apt-get upgraded and got nginx 1.7.8 and a load of dead sites. running nginx -t gave me a segmentation fault (core dumped) error.
After a whole load of panicking and commenting one line out at a time, I finally tracked it down to this section:
```
location ~ /purge(/.*) {
fastcgi_cache_purge WORDPRESS "$scheme$request_method$host$1";
}
```
If I comment that out, I can start up wordpress and nginx -t doesn't core dump.
I posted on the nginx forum at http://forum.nginx.org/read.php?2,255522, and they are suggesting it's definitely a third party module causing it, and linked here.
However, As far as I can see, the nginx-extras package was built 15 hours ago.
Also, from this repo:
```
2014-12-02 VERSION 2.2
* Fix compatibility with nginx-1.7.8+.
```
From nginx -V
```
--add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-cache-purge
```
I can't see anything obvious in the release notes that would cause this, server details are below:
```
Linux 3.16.0-28-generic #37-Ubuntu SMP Mon Dec 8 17:22:00 UTC 2014 i686 i686 i686 GNU/Linux
nginx version: nginx/1.7.8
TLS SNI support enabled
configure arguments: --with-cc-opt='-g -O2 -fstack-protector-strong -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_auth_request_module --with-http_addition_module --with-http_dav_module --with-http_flv_module --with-http_geoip_module --with-http_gzip_static_module --with-http_image_filter_module --with-http_mp4_module --with-http_perl_module --with-http_random_index_module --with-http_secure_link_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.7.8/debian/modules/headers-more-nginx-module --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-auth-pam --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-cache-purge --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-dav-ext-module --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-development-kit --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-echo --add-module=/build/buildd/nginx-1.7.8/debian/modules/ngx-fancyindex --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-http-push --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-lua --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-upload-progress --add-module=/build/buildd/nginx-1.7.8/debian/modules/nginx-upstream-fair --add-module=/build/buildd/nginx-1.7.8/debian/modules/ngx_http_substitutions_filter_module
```
Thanks
Posted at Nginx Forum:
For anyone following this, I had a reply on the repo bug ticket saying:
I just downloaded nginx_1.7.8-1+utopic1.debian.tar.gz sources from PPA and
So, I’ve just done that - I’ll let you know what the outcome is -
Posted at Nginx Forum:
Right, sorted! Bug #1403054 “[Mainline] 1.7.8 package not using compatible cach...” : Bugs : Nginx
New nginx-extras mainline is now available to fix the bug - my good deed
Posted at Nginx Forum:
