Hello,
As agentzh mentioned eval was causing the problem. I replaced eval with lua
and after changing the configuration accordingly I haven't seen any
segfaults again.
Thanks everybody for the help
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,247886,248324#msg-248324
__
Hello,
I suppose you are correct. I have tried to recreate the problem without the
two modules and I haven't succeeded yet. Anyway I need the modules so I can
live with some segmentation faults. From the part of debug log below I think
that the worker (5201) before dying closes properly the connec
Hello
Below is the backtrace. I have seen the behaviour without eval and Postgres
and I will try to take a trace tomorrow. In the debug log actually there is
no error. Since I have only one worker the PID just changes to the new
worker without any info. Since I am using nginx as proxy only I am
su
Hello
Finally I managed to get a core dump and below is the output:
[root@ape-01 nginx]# gdb /usr/local/nginx/sbin/nginx
/var/log/nginx/core.31000
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
Hello,
The debug log is huge. Any ideas where to uploaded?
BR/Kostas
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,247886,247891#msg-247891
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
Hello,
I have an issue with segfaults especially when I send lot's of traffic to
the server. The hardware is an HP proliant G8 with 24 cores but I am using
only one worker because the problem becames worse with more than one. I have
also modified the ulimit for the nginx user up to 65535 b
