Return-Path: Delivered-To: apmail-apache-bugdb-archive@apache.org Received: (qmail 83202 invoked by uid 500); 2 Jun 2001 19:30:02 -0000 Mailing-List: contact apache-bugdb-help@apache.org; run by ezmlm Precedence: bulk Reply-To: apache-bugdb@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list apache-bugdb@apache.org Received: (qmail 83182 invoked by uid 501); 2 Jun 2001 19:30:01 -0000 Resent-Date: 2 Jun 2001 19:30:01 -0000 Resent-Message-ID: <20010602193001.83180.qmail@apache.org> Resent-From: submit@bugz.apache.org (GNATS Filer) Resent-To: apache-bugdb@apache.org Resent-Cc: apache-bugdb@apache.org Resent-Reply-To: submit@bugz.apache.org, jag@nucleus.com Received: (qmail 81223 invoked by uid 501); 2 Jun 2001 19:24:29 -0000 Message-Id: <20010602192429.81222.qmail@apache.org> Date: 2 Jun 2001 19:24:29 -0000 From: Zak Greant Reply-To: jag@nucleus.com To: submit@bugz.apache.org X-Send-Pr-Version: 3.110 Subject: general/7808: apachectl stop does not halt the server >Number: 7808 >Category: general >Synopsis: apachectl stop does not halt the server >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sat Jun 02 12:30:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: jag@nucleus.com >Release: 2.0.16 >Organization: apache >Environment: SuSE 7.1 / Linux www 2.4.0-4GB #1 Wed Jan 24 15:55:09 GMT 2001 i686 unknown Apache was built with: % ./configure --enable-so \ --prefix=/home/httpd/apache2 \ --with-mpm=perchild >Description: apachectl stop does not halt the server Here is the scenario: The value stored in log/http.pid is 16686 Before running apachectl stop, ps -ax | grep "bin/httpd$" displays 44 processes After running apachectl stop, the same command displays 33 processes I am using the default settings for perchild There is more info below. Defore: 16686 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16687 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16688 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16689 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16690 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16691 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16692 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16693 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16694 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16705 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16706 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16707 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16711 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16712 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16713 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16714 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16715 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16716 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16717 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16721 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16722 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16723 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16724 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16725 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16728 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16729 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16730 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16731 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16732 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16733 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16736 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16737 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16738 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16739 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16743 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16744 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16745 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16748 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16749 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16750 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16753 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16754 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16825 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16973 pts/0 S 0:00 /home/httpd/apache2/bin/httpd After: 16686 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16688 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16689 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16692 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16693 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16694 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16707 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16712 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16713 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16714 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16721 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16724 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16725 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16728 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16729 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16730 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16731 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16732 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16733 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16736 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16737 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16738 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16739 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16743 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16744 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16745 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16748 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16749 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16750 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16753 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16754 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16825 pts/0 S 0:00 /home/httpd/apache2/bin/httpd 16973 pts/0 S 0:00 /home/httpd/apache2/bin/httpd Only 16687, 16690, 16691, 16705, 16706, 16711, 16715, 16716, 16717, 16722 and 16723 are killed. >How-To-Repeat: >Fix: ..er.. I don't know if this is a good idea or not, but you could explictly kill every process that has a PGID that matches the value stored in logs/httpd.pid??? I have just been using ps -ax | awk '/\/bin\/httpd$ {system ("kill -9 " $1)}' >Release-Note: >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database 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! ]