www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christoph Dietz ...@amiga-news.de>
Subject os-linux/7132: Childs keep in KeepAlive state after KeepAlive timeout
Date Thu, 25 Jan 2001 20:21:40 GMT

>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
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Thu Jan 25 12:30:04 PST 2001
>Originator:     cd@amiga-news.de
>Release:        1.3.14
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)
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 www.amiga-news.de GET /pics/flag_jp.gif
2-1 4820 1/7/7 K  0.27 5412 1 5.7 0.01 0.01 www.amiga-news.de GET /pics/kinne300x65.jpg

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.
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.
Only a quick and dirty solution: We restart the server every 24 hours.
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> 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!     ]

View raw message