Received: (qmail 2293 invoked by uid 501); 25 Jan 2001 20:21:40 -0000 Message-Id: <20010125202140.2292.qmail@apache.org> Date: 25 Jan 2001 20:21:40 -0000 From: Christoph Dietz Reply-To: cd@amiga-news.de To: submit@bugz.apache.org Subject: Childs keep in KeepAlive state after KeepAlive timeout X-Send-Pr-Version: 3.110 >Number: 7132 >Category: os-linux >Synopsis: Childs keep in KeepAlive state after KeepAlive timeout >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Thu Jan 25 12:30:04 PST 2001 >Closed-Date: >Last-Modified: Fri Jan 26 11:20:03 PST 2001 >Originator: cd@amiga-news.de >Release: 1.3.14 >Organization: apache >Environment: Linux uus 2.2.7 #2 Sat Nov 18 17:09:02 MET 2000 i686 unknown Compiler unknown (We're not the hostmaster of the server) >Description: We are using 1.3.14 with php 4.0.1pl1 and mysql db usage on a SuSE 7.0 based linux system. KeepAlive is set to (now) 10 secondes (before 15) MaxRequests per Child is (now) set to 0 (before 20) MaxChilds is set to 256 MinSparServers 5 MaxSparServers 10 InitialServers 5 After running the server a few hours more and more childs keep in the "K" state. Also childs which handle new customers don't leave the K state after the set time (I tested it with getting the /server-status and checked if the K for my IP address was removed after one minute. Result: I got the same child and it told me that it waited so long (filed SS). After waiting two minutes, I got another child and the original one handled a request. But there are childs waiting in K state much longer: 0-1 4818 11/78/78 K 0.92 4867 1 5.0 0.14 0.14 62.226.18.62 www.amiga-news.de GET /pics/flag_jp.gif HTTP/1.1 2-1 4820 1/7/7 K 0.27 5412 1 5.7 0.01 0.01 213.21.3.76 www.amiga-news.de GET /pics/kinne300x65.jpg HTTP/1.1 I tried several settings (as shown above). It didn't help. Also we removed mod_SSL (as shown as the trouble maker in another Bug-Report for the same problem). No changes. >How-To-Repeat: If needed I can give access to /server-status on www.amiga-news.de. But I need the IP address of the tester for security reasons. >Fix: Only a quick and dirty solution: We restart the server every 24 hours. >Release-Note: >Audit-Trail: From: cd@amiga-news.de To: submit@bugz.apache.org, apache-bugdb@apache.org Cc: Subject: Re: os-linux/7132: Childs keep in KeepAlive state after KeepAlive timeout Date: Fri, 26 Jan 2001 11:15:32 -0800 Hello! > Thank you very much for your problem report. > It has the internal identification `os-linux/7132'. > The individual assigned to look at your > report is: apache. > > >Category: os-linux > >Responsible: apache > >Synopsis: Childs keep in KeepAlive state after KeepAlive timeout > >Arrival-Date: Thu Jan 25 12:30:04 PST 2001 We solved the problem with applying the patch which is discribed at the end of the bug report: ttp://bugs.apache.org/index.cgi/full/3906 Our server now closes the connections after the given time. Regards, ChrisDi >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! ]