On Sat, 28 Jul 2001, Greg Ames wrote:
> When I set MaxClients to 1 and ThreadsPerChild to 2, I cannot make it
> hang. When I lower ThreadsPerChild to 1, ab hangs if
> server-status?refresh=2 is running, because mod_status is grabbing the
> only worker thread on my server and never giving it up, no doubt due to
> keepalives. With refresh=5, ab can run concurrently. It is dog slow
> with c=200 though, reasonable with c=50, dunno why, maybe a O(n**2)
> problem somewhere - my hunch would be ab or the kernel. apachectl
> graceful seems to work fine no matter what I do.
>
> OK, now I have Cliff's config parms for threaded (they look like the
> defaults),
They're almost the defaults, but not quite. I bumped up one or two of the
numbers (ThreadsPerChild and MaxSpareThreads, I think):
StartServers 3
MaxClients 8
MinSpareThreads 5
MaxSpareThreads 30
ThreadsPerChild 50
MaxRequestsPerChild 0
> still don't see the same problem, still nothing funky ever
> with graceful. Cliff, two more questions: what do you have for
> HARD_SERVER_LIMIT and HARD_THREAD_LIMIT? defaults?
I haven't changed them, so I guess they're the defaults.
> and did you make
> clean && make ? (I'm wondering about mpm_common in particular)
Yep. I think I even did a make extraclean, but I'm not positive. I've
gone through this process so many times in the past three days it's
impossible to remember. I always do a make fooclean, where foo is usually
either extra or dist at least.
> But I did get a hang after getting 16 seg faults (which could be in
> mod_status - still no dumps) because all my worker processes are gone.
> They shouldn't be - new ones should crank up after seg faults. gdb
> shows the process_scores are clean, so that's not it. I'll keep
> plugging until my better half gets home.
[Shrug] I'll try it again in a little while on my Linux box. Maybe my
Solaris machine was just misbehaving.
--Cliff
--------------------------------------------------------------
Cliff Woolley
[EMAIL PROTECTED]
Charlottesville, VA
