nginx segfault around ~600 requests per second (reverse proxy)

[Marcus Clyne]

Hi,

yomuppet wrote:
> Hello,
>
> I have noticed that we seem to consistently get an nginx segault when reaching around 600 requests per second (reverse proxy).
>
> Here is the nginx build information:
> $ nginx -V
> nginx version: nginx/0.8.29
> built by gcc 4.1.2 20080704 (Red Hat 4.1.2-44)
> TLS SNI support disabled
> configure arguments: --add-module=../agentzh-chunkin-nginx-module-cb610a5 --with-http_ssl_module --with-http_realip_module --with-http_addition_module --with-http_sub_module --with-http_dav_module --with-http_flv_module --with-http_gzip_static_module --with-http_stub_status_module --with-http_perl_module
>
>   
Have you tried compiling without the chunkin module?  AFAIK it's still 
experimental.
> Here is the segfault information: 
> Jan 17 12:51:31 util1 kernel: nginx[27888]: segfault at 0000000000000008 rip 0000000000429061 rsp 00007fffcc260500 error 6
> Jan 24 16:21:33 util1 kernel: nginx[3835]: segfault at 0000000000000008 rip 0000000000429061 rsp 00007fffcc260550 error 6
> Jan 24 16:22:24 util1 kernel: nginx[8956]: segfault at 0000000000000008 rip 0000000000429061 rsp 00007fffcc260550 error 6
> Jan 24 16:22:26 util1 kernel: nginx[8982]: segfault at 0000000000000008 rip 0000000000429061 rsp 00007fffcc260550 error 6
> Jan 24 16:22:27 util1 kernel: nginx[9026]: segfault at 0000000000000008 rip 0000000000429061 rsp 00007fffcc260550 error 6
>
> Does anyone know why this might be occurring, or any helpful information we can provide to better track it down?
>   
If compiling without the chunkin module doesn't isolate the problem, 
perform a backtrace.

Marcus.