Weird Memleak problem

Paul paul at gtcomm.net
Wed Sep 2 03:48:28 MSD 2009


I know this.. but there isn't any slow requests going on :/ Or shouldn't 
be anyway.  Just odd it never used to
take more than a few mins, must have been a new site we added or 
something that is keeping the connections open long.


Maxim Dounin wrote:
> Hello!
>
> On Mon, Aug 31, 2009 at 06:10:16PM -0400, Paul wrote:
>
>   
>> Oh I also notice another issue, when ram usage is high like this, when i  
>> reload nginx it does this:
>> root      5776  0.0  0.1  19528  4876 ?        Ss   Aug30   0:00 nginx:  
>> master process /usr/local/nginx/sbin/nginx -c conf/ng1.conf
>> www       5777  2.3  2.3 184060 94364 ?        S    Aug30  28:53 nginx:  
>> worker process is shutting down
>> www       5778  2.3  2.3 315500 95496 ?        S    Aug30  29:23 nginx:  
>>     
>
> [...]
>
>   
>> and the processes stay in 'process is shutting down' for a LONG time..  
>> I've waited quite a while before
>> doing a restart instead of reload to clear them out.   Not sure what  
>> would cause this?
>> Most of my connection timeouts are set between 60-120seconds. Except SSL  
>> session one is 10m, but i've waited
>> hours for the old processes to shut down.
>>     
>
> nginx worker processes wait for all currently processed requests 
> to finish before exiting.  It can take hours if there are active 
> but slow requests or requests with big responses.
>
> You may use normal network diagnostic tools (netstat, tcpdump, 
> ...) to see what actually happens on the wire.
>
> Maxim Dounin
>
>
>   

-- 
GloboTech Communications
Phone: 1-514-907-0050 x 215
Toll Free: 1-(888)-GTCOMM1
Fax: 1-(514)-907-0750
paul at gtcomm.net
http://www.gtcomm.net 






More information about the nginx mailing list