Return-Path: Delivered-To: apmail-httpd-users-archive@www.apache.org Received: (qmail 2143 invoked from network); 13 Apr 2005 19:52:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Apr 2005 19:52:04 -0000 Received: (qmail 31786 invoked by uid 500); 13 Apr 2005 19:51:44 -0000 Delivered-To: apmail-httpd-users-archive@httpd.apache.org Received: (qmail 31774 invoked by uid 500); 13 Apr 2005 19:51:43 -0000 Mailing-List: contact users-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: users@httpd.apache.org list-help: list-unsubscribe: List-Post: Delivered-To: mailing list users@httpd.apache.org Received: (qmail 31760 invoked by uid 99); 13 Apr 2005 19:51:43 -0000 X-ASF-Spam-Status: No, hits=0.4 required=10.0 tests=DNS_FROM_RFC_ABUSE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of skylos@gmail.com designates 64.233.170.206 as permitted sender) Received: from rproxy.gmail.com (HELO rproxy.gmail.com) (64.233.170.206) by apache.org (qpsmtpd/0.28) with ESMTP; Wed, 13 Apr 2005 12:51:42 -0700 Received: by rproxy.gmail.com with SMTP id y7so267652rne for ; Wed, 13 Apr 2005 12:51:40 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=PNAku0pF9P4t3ERxqzoTaOqZp22w3FYFs8MXH2noYRpN+/yD9JkIKAswav1gaJF9j3bqGd5fGwg3qSepQNpQNJuwfCgtIUJmsFAF4EU4BSZ5J29KuC4u6Vb5TdfQKnz2jcQZFKNg3b/sON4skn97j3OQS2bMw45xXmmAUy79yuY= Received: by 10.38.150.20 with SMTP id x20mr964174rnd; Wed, 13 Apr 2005 12:51:37 -0700 (PDT) Received: by 10.38.65.23 with HTTP; Wed, 13 Apr 2005 12:51:36 -0700 (PDT) Message-ID: <3650cdc005041312513b848e25@mail.gmail.com> Date: Wed, 13 Apr 2005 12:51:36 -0700 From: Skylos Reply-To: Skylos To: users@httpd.apache.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Virus-Checked: Checked Subject: [users@httpd] Runaway thread, troubleshooting tools needed X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Greetings, I'm pretty new to the concept of threads and debugging them - I currently am running... Server version: Apache/2.0.53 Server built: Mar 6 2005 21:52:49 I am utilizing the worker mpm to serve a moderate volume website with two servers. I extensively use mod_perl, but I realize this is not a mod_perl list. I purely wish to learn ways of finding out what stage/process is going on when this thread/process locks up. This should be general to apache, right? My symptoms are that a server will start utilizing 100% of one of the 4 cpus. (this happens on both) This usually happens within 18 hours of a server startup, but seems entirel.y random. If I do an 'apachectl restart', the problem will almost always go away. However, even on shutdown, there will be a several httpd processes left that will not die without a kill -9 to them specifically. When I display top, it shows the cpu usage, but it doesn't show which process is using it - sorting by cpu usage shows no process using more than about 0.3% of the cpu. I need help. Can you suggest commands that would allow me to track the threads, see what might be happening in the request stream when this occurs? Hopefully, Skylos --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See for more info. To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org " from the digest: users-digest-unsubscribe@httpd.apache.org For additional commands, e-mail: users-help@httpd.apache.org