As a request comes in, it is denoted in the scoreboard. The scoreboard itself is basically a way to keep track of each incoming, waiting, and completing connections. These connections are broken down into the following types:
- “_” Waiting for Connection
- “S” Starting up
- “R” Reading Request
- “W” Sending Reply
- “K” Keepalive (read)
- “D” DNS Lookup
- “C” Closing connection
- “L” Logging
- “G” Gracefully finishing
- “I” Idle cleanup of worker
- “.” Open slot with no current process
Here is an example of the apache scoreboard in WHM:
(22:06 root@host) > service httpd status
Apache Server Status for localhost
Server Version: Apache/2.2.26 (Unix) mod_ssl/2.2.26
OpenSSL/0.9.8e-fips-rhel5 mod_bwlimited/1.4
Server Built: Mar 7 2014 08:09:21
_________________________________________________________________
Current Time: Tuesday, 15-Jul-2014 22:08:36 MST
Restart Time: Tuesday, 15-Jul-2014 13:44:12 MST
Parent Server Generation: 4
Server uptime: 8 hours 24 minutes 24 seconds
Total accesses: 58665 - Total Traffic: 173.3 MB
CPU Usage: u9.9 s5.84 cu114.75 cs0 - .431% CPU load
1.94 requests/sec - 5.9 kB/second - 3098 B/request
104 requests currently being processed, 9 idle workers
GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG
GGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGGG_GGG_GG_____W...__............
................................................................
................................................................
Scoreboard Key:
"_" Waiting for Connection, "S" Starting up, "R" Reading Request,
"W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup,
"C" Closing connection, "L" Logging, "G" Gracefully finishing,
"I" Idle cleanup of worker, "." Open slot with no current process
Was this post helpful?
Let us know if you liked the post. That’s the only way we can improve.