Package: nginx-extras Version: 1.4.4-1 Severity: minor There is a bug in the nginx-extras package triggered by the push module, in which case it creates error output into the error.log file, whenever fastcgi_cache or proxy_cache is used. It does not, however, prevent the caching from working (hence the "minor" severity). This has been seen going all the way back to 1.1.19 on Ubuntu, however this was replicated in the nginx-extras packages in unstable, which is why I marked it found in 1.4.4-1. It is safe to assume this affects testing and stable-backports.
The Ubuntu bug on this is https://bugs.launchpad.net/nginx/+bug/1216817 The configuration I used to replicate is in a Debian pastebin at http://paste.debian.net/71051. The error output for the push module in this cases is located at http://paste.debian.net/71053 and from what testing I have done I have been able to narrow this down to a startup bug, however I have not in-depth tested this issue. You can replicate this issue by setting up caching, and just restarting the nginx service. I tested this with setting up php5-fpm and did fastcgi_cache for php documents, and put a few test PHP documents into the cache. Whether files exist or not seems to be irrelevant, as this happens on startup regardless if the cache exists or not, based on my testing. --- Michael Lustfield was also able to reproduce this error after I provided some steps to reproduce this bug after discussion on IRC. It may be that this is an issue in the push module that is included in the extras package. ------ Thomas -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
