Piotr Sikora Wrote: ------------------------------------------------------- > Hey, > assuming this is your whole config, could you either uncomment the > access_log directive or add "access_log off"? I'm pretty sure you're > hitting the bug introduced in 1.7.0: > http://mailman.nginx.org/pipermail/nginx-devel/2014-June/005430.html Yes. It started since 1.7.0 - allby Spacedust - Nginx Mailing List - English
Also dmesg is full of this: nginx[9184]: segfault at 27 ip 0000000000447606 sp 00007fff9972a8b0 error 4 in nginx[400000+b6000] nginx[9599]: segfault at 19 ip 0000000000447606 sp 00007fff9972b7f0 error 4 in nginx[400000+b6000] nginx[9579]: segfault at 117 ip 0000000000447606 sp 00007fff9972b7f0 error 4 in nginx[400000+b6000] nginx[9600]: segfault at 19 ip 0000000000447606 sp 00007fff9972b7f0by Spacedust - Nginx Mailing List - English
I use nginx 1.7.1 as frontend proxy to Apache 2.2.27 + php-fpm 5.5.13. When I add new domain, then just reload nginx it throwing errors like "connection reset" etc. Error log is full of something like this: tail -f /var/log/nginx/error.log 2014/06/04 11:36:23 12928#0: worker process 3958 exited on signal 11 2014/06/04 11:36:23 12928#0: worker process 3959 exited on signal 11by Spacedust - Nginx Mailing List - English