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 29, 2009 9:40:50 am
List:ru.sysoev.nginx

On Sun, Aug 30, 2009 at 01:45:30AM +1000, Jeff Waugh wrote:

<quote who="Igor Sysoev">

2009/08/29 23:15:52 [alert] 8716#0: open socket #152 left in connection 105

This is probably after reconfiguraiton.

Sorry, yes, I should've checked the time -> that was from when I reverted to 0.8.10... there no alerts prior to that.

There are signinficant changes in 0.8.11, but you case is strange: I'am testing 0.8.11 on a host with 400r/s with a lot of proxied SSIed subrequests and static files, and there is no connection leak.

Have you built any third party modules ?

None.

btw, the majority of my non-static traffic is fastcgi over unix socket. I'm going to do the upgrade again and watch the activity.

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 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

do not forget to set NN from log message.

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