>Number:         4397
>Category:       mod_status
>Synopsis:       server-status displays huge number for "Req"
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Wed May 12 09:30:02 PDT 1999
>Last-Modified:
>Originator:     [EMAIL PROTECTED]
>Organization:
apache
>Release:        1.3.6
>Environment:
Linux 2.0.33
>Description:
If you do a server-status immediately after restarting the server, a huge 
number is displayed for the milliseconds required to process most recent 
request.

Below is a snippet from an actual server-status page:

Server uptime: 3 seconds
Total accesses: 0 - Total Traffic: 0 kB
CPU Usage: u0 s0 cu0 cs0
0 requests/sec - 0 B/second - 
1 requests currently being processed, 2 idle servers 

W__.............................................................
................................................................
................................................................
................................................................


Srv PID   Acc   M CPU  SS Req        Conn Child  Slot  Client        VHost      
      Request
0-9 25382 0/0/0 W 0.00 3  1193254549 0.0  0.00   0.00  134.169.10.45 
www.euroavia.org GET /server-status HTTP/1.0

When I reload the page the "Req" number is back down to something reasonable.
>How-To-Repeat:
Restart your server, then immediately request a server-status page.
>Fix:
I'd guess that some variable is not initialized properly (???).
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, ]
[you need to include <[EMAIL PROTECTED]> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]



Reply via email to