server-status traffic bug

[xmb <xm...@digital-bless.com>]

Morning, i just saw something weird while the server had heavy load for a day

   Server uptime: 28 days 3 hours 33 minutes 54 seconds
   Total accesses: 5327861 - Total Traffic: 102.0 GB

   Server uptime: 28 days 3 hours 45 minutes 44 seconds
   Total accesses: 5331468 - Total Traffic: 99.0 GB

and after 9 hours:

   Server uptime: 28 days 12 hours 33 minutes 4 seconds
   Total accesses: 5449896 - Total Traffic: 86.6 GB

(and oh well, a few mins later)

   Server uptime: 28 days 12 hours 48 minutes 47 seconds
   Total accesses: 5453416 - Total Traffic: 87.1 GB


the actual traffic usage up to the second paste here was around 48GB gotten from the apache logs with mod_logio (and iptables logging)

the whole thing on a debian sid box, release apache 2.0.48, compiled with gcc ~3.3.2 around two months ago, only addition was -march=i686

Re: server-status traffic bug

[Jeff Trawick <tr...@attglobal.net>]

On Dec 28, 2003, at 6:55 PM, xmb wrote:

> Morning, i just saw something weird while the server had heavy load 
> for a day
>
>    Server uptime: 28 days 3 hours 33 minutes 54 seconds
>    Total accesses: 5327861 - Total Traffic: 102.0 GB
>
>    Server uptime: 28 days 3 hours 45 minutes 44 seconds
>    Total accesses: 5331468 - Total Traffic: 99.0 GB

the accumulated totals only include processes currently owning a 
scoreboard slot; the totals won't be accurate unless you disable 
exiting of child processes

so in that 12 minute period, at least one child process exited 
(presumably due to MaxRequestsPerChild or 
MaxSpareThreads/MaxSpareServers), and its counts were lost