Posted by emjayess on November 29, 2012 at 8:58pm
Hi. I just bumped into this hurdle... a glaring oversight in my planning effort. We need to temporarily run a v6 site and a v7 site on the same web server, if possible. Currently, the machine is serving up a d6 (pressflow) site and we're using @perusio's drupal-with-nginx project.
The nginx.conf file contains version-specific include directives, and so wondering if it's workable to move these to the relevant vhost for the 6 and 7 sites, respectively?
Comments
spoke to soon?
so the error I'm introducing by enabling a d7 vhost and doing a syntax check is actually:
[emerg] 23020#0: "fastcgi_cache" zone "microcache" is unknown in /etc/nginx/nginx.conf:185tho I'm not including
fastcgi_microcache_zone.conffrom the main nginx.conf, it's disabled/commented out.--
matt j. sorenson, g.d.o., d.o.
The problem is the solution
Ugh, sorry for the noise - the problem was having fastcgi_microcache_zone.conf not included; As a drupal 7 vhost will include drupal.conf which will include microcache_fcgi.conf which will puke if fastcgi_microcache_zone.conf isn't present.
In case it happens to be useful to anyone besides me :P
cheers
--
matt j. sorenson, g.d.o., d.o.
Thanks,
I'm probably going to bump into exactly the same issue in the next couple of months, so thanks..
John
few more tidbits
I haven't gone back to check, but I suspect the default include chain out of the box for drupal 6 would also have included microcache_fcgi.conf, and out of the box would have had alerted of a similar problem.
As best I can recall, we simply disabled all the microcaching setup for pressflow originally due to a md5 collisions issue we couldn't get to the bottom of, a bug that has been fixed in subsequent versions of nginx.
In summary, if you never disable all or part of the microcaching setup in the first place, you probably won't bump into this.
--
matt j. sorenson, g.d.o., d.o.