stub_status always give me 0 Reading when upgraded to 1.4.1
    Maxim Dounin 
    mdounin at mdounin.ru
       
    Wed Jul 17 10:29:52 UTC 2013
    
    
  
Hello!
On Wed, Jul 17, 2013 at 10:34:48AM +0800, Tsz Ming WONG wrote:
> Hi,
> 
> We have upgraded one of our nginx from 0.7.65 to 1.4.1 (keeping existing
> configuration) and the stub_status module now always give me "0 Reading"
> 
> 0.7.65
> Active connections: 4798
> server accepts handled requests
>  1690444496 1690415734 1814927218
> Reading: 573 Writing: 184 Waiting: 4041
> 
> 1.4.1
> Active connections: 4858
> server accepts handled requests
>  33056255 33056255 37277559
> Reading: 0 Writing: 196 Waiting: 4386
This is an effect from the following change in 1.3.15:
    *) Change: opening and closing a connection without sending any data in
       it is no longer logged to access_log with error code 400.
Connections in question no longer have an associated request 
created, and as a result are counted in "waiting" instead of 
"reading".
-- 
Maxim Dounin
http://nginx.org/en/donation.html
    
    
More information about the nginx
mailing list