atom feed27 messages in ru.sysoev.nginxRe: Weird 0.8.11.1 connections spike
FromSent OnAttachments
Jeff WaughAug 29, 2009 5:50 am 
Igor SysoevAug 29, 2009 6:48 am 
Jeff WaughAug 29, 2009 7:32 am 
Igor SysoevAug 29, 2009 8:08 am 
Jeff WaughAug 29, 2009 8:45 am 
Igor SysoevAug 29, 2009 9:40 am 
Jim OhlsteinAug 30, 2009 7:59 am 
Igor SysoevAug 30, 2009 8:31 am 
Jim OhlsteinAug 30, 2009 8:52 am 
Igor SysoevAug 30, 2009 9:29 am 
Jim OhlsteinAug 30, 2009 7:55 pm 
Jeff WaughAug 30, 2009 8:03 pm 
Igor SysoevAug 30, 2009 10:23 pm 
Igor SysoevAug 30, 2009 10:46 pm 
Jeff WaughAug 30, 2009 11:36 pm 
Jeff WaughAug 31, 2009 12:14 am 
Igor SysoevAug 31, 2009 12:24 am 
Jeff WaughAug 31, 2009 12:55 am 
Igor SysoevAug 31, 2009 1:34 am 
Jeff WaughAug 31, 2009 1:36 am 
Jeff WaughAug 31, 2009 2:03 am 
Igor SysoevAug 31, 2009 3:37 am 
Igor SysoevAug 31, 2009 4:27 am.Other
Jim OhlsteinAug 31, 2009 5:13 am 
Igor SysoevAug 31, 2009 5:27 am 
Jeff WaughAug 31, 2009 6:53 am 
Igor SysoevAug 31, 2009 7:07 am 
Subject:Re: Weird 0.8.11.1 connections spike
From:Igor Sysoev (is@rambler-co.ru)
Date:Aug 30, 2009 9:29:58 am
List:ru.sysoev.nginx

On Sun, Aug 30, 2009 at 11:52:51AM -0400, Jim Ohlstein wrote:

2009/08/30 10:29:00 [alert] 2042#0: open socket #1023 left in connection 1015 2009/08/30 10:29:00 [alert] 2042#0: aborting

Other servers seem to be running fine including ones with busy sites. For the moment I have reverted that VPS to 0.8.10.

Could you do the following:

1) enable coredumps 2) set in nginx.conf: debug_points abort; 3) reconfigure nginx, if there are open connections, then nginx creates coredump on exit

Do you want nginx reconfigured "--with-debug" or is there another option you need?

No. The coredump is enough, it's just should have debug info (gcc -g option).

4) look in log for alerts: open socket #... left in connection NN 5) run "gdb /path/to/nginx /path/to/core", then

p ((ngx_connection_t *) ngx_cycle->connections[NN]->data)->uri p ((ngx_connection_t *) ngx_cycle->connections[NN]->data)->main->count

where NN is NN from log message.

-- Igor Sysoev http://sysoev.ru/en/