Drupal 10, the latest version of the open-source digital experience platform with even more features, is here.When upgrading from 3.4 to 3.5 (using the Ubuntu repository), We get this error in the log when trying to reload or restart nginx:
Reloading nginx configuration: nginx: [emerg] unknown "status" variable
Status is used in two places in /var/aegir/config/includes/nginx_vhost_common.conf
add_header X-Response-Status "$status";
and
fastcgi_cache_key "$is_bot$device$host$request_method$key_uri$cache_uid$http_x_forwarded_proto$sent_http_x_local_proto$cookie_respimg$status";
Commenting out the add_header line and removing $status from the 2nd line allows nginx to start.
Using nginx version 1.2.1
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | 0001-Issue-2738983-Nginx-unknown-status-variable.patch | 3.58 KB | memtkmcc |
Comments
Comment #2
millenniumtreeHad this in the wrong project
Comment #3
memtkmcc CreditAttribution: memtkmcc commentedRight, it looks like we don't check Nginx version / compatibility properly here. Besides, this addition proved useless, because it never gets added to the cache key.
Comment #4
memtkmcc CreditAttribution: memtkmcc at Omega8.cc commentedAttached patch should fix the problem.
Comment #5
millenniumtreeNICE - thanks for that!
How do I force a template rebuild after patching?
Comment #6
memtkmcc CreditAttribution: memtkmcc at Omega8.cc commentedIt should be enough to re-verify the web server (node) to force it to use patched templates. Or just:
su -s /bin/bash aegir -c "drush @hm hosting-task @server_master verify --force"Comment #7
memtkmcc CreditAttribution: memtkmcc at Omega8.cc commentedThis can be marked as RTBC.
Comment #9
helmo CreditAttribution: helmo at Initfour websolutions for Aegir Cooperative commentedCommitted, thanks.