From: Rich Bowen Date: Tue, 29 Mar 2011 14:47:50 +0000 (+0000) Subject: Rebuild, and fix XML error. Troubleshooting using server-status X-Git-Tag: 2.3.12~141 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=1eae2441aca42ab9628fb9f04cfc4e539fb9f676;p=thirdparty%2Fapache%2Fhttpd.git Rebuild, and fix XML error. Troubleshooting using server-status git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1086608 13f79535-47bb-0310-9956-ffa450edef68 --- diff --git a/docs/manual/mod/mod_status.html.en b/docs/manual/mod/mod_status.html.en index 65d4e5a403c..030da90d564 100644 --- a/docs/manual/mod/mod_status.html.en +++ b/docs/manual/mod/mod_status.html.en @@ -81,6 +81,7 @@ performance
  • Enabling Status Support
  • Automatic Updates
  • Machine Readable Status File
    • +
  • Using server-status to troubleshoot
    • top
    @@ -134,6 +135,37 @@ performance ramifications for your site.
    +
    top
    +
    +

    Using server-status to troubleshoot

    + + +

    The server-status page may be used as a starting + place for troubleshooting a situation where your server is consuming + all available resources (CPU or memory), and you wish to identify + which requests or clients are causing the problem.

    + +

    First, ensure that you have ExtendedStatus set on, so that you can see + the full request and client information for each child or + thread.

    + +

    Now look in your process list (using top, or similar + process viewing utility) to identify the specific processes that are + the main culprits. Order the output of top by CPU + usage, or memory usage, depending on what problem you're trying to + address.

    + +

    Reload the server-status poage, and look for those process + ids, and you'll be able to see what request is being served by that + process, for what client. Requests are transient, so you may need to + try several times before you catch it in the act, so to speak.

    + +

    This process should give you some idea what client, or + what type of requests, are primarily responsible for your load + problems. Often you will identify a particular web application that + is misbehaving, or a particular client that is attacking your + site.

    +
    diff --git a/docs/manual/mod/mod_status.xml b/docs/manual/mod/mod_status.xml index da201f68f6f..ac6536a0fc4 100644 --- a/docs/manual/mod/mod_status.xml +++ b/docs/manual/mod/mod_status.xml @@ -142,7 +142,7 @@ performance usage, or memory usage, depending on what problem you're trying to address.

    -

    Reload the server-status<.code> poage, and look for those process +

    Reload the server-status poage, and look for those process ids, and you'll be able to see what request is being served by that process, for what client. Requests are transient, so you may need to try several times before you catch it in the act, so to speak.

    diff --git a/docs/manual/mod/mod_status.xml.ja b/docs/manual/mod/mod_status.xml.ja index a8c474fee6e..a9c449378bf 100644 --- a/docs/manual/mod/mod_status.xml.ja +++ b/docs/manual/mod/mod_status.xml.ja @@ -2,7 +2,7 @@ - + + +