nginx core dump explodes

Maxim Dounin mdounin at
Mon Jun 20 18:18:38 UTC 2016


On Fri, Jun 17, 2016 at 07:30:26AM -0400, martinproinity wrote:

> nginx version: nginx/1.11.1
> built with OpenSSL 1.0.2h  3 May 2016
> I try to debug those alerts currently, which only appear after a reload:
> 2016/06/17 13:10:49 [alert] 14624#0: *15709 open socket #626 left in
> connection 628
> I compiled nginx with --with-debug and set the flags CFLAGS="-g -O0"
> ./configure...
> The following core dump settings are defined:
> debug_points abort;
> working_directory /var/tmp/cores/;
> worker_rlimit_core 512M;
> error_log /var/log/nginx/error.log debug;
> I can see that it starts to generate the core file but it becomes very large
> (>500GB) and removes it at the end.
> Any idea what I'm doing wrong here?

The "worker_rlimit_core 512M" line in your configuration suggests 
that the kernel should not generate core files bigger than 512M.  
If a worker process core takes more than that, the behaviour you 
describe looks more or less normal.

Maxim Dounin

More information about the nginx mailing list