Re: 3.2b5 : mod_python doesn't handle properly signals likeKILL,SEGV...
Web Server forum
Back To The Forum Home!Search!Private Messaging System

Web Server Talk Web Server Talk > Web Servers reviews > Apache Server configuration support > Apache Mod-Python > Re: 3.2b5 : mod_python doesn't handle properly signals likeKILL,SEGV...




  Last Thread   Next Thread Next
  Show Printable Version Email this Page Subscribe to this Thread      Post New Thread    Post A Reply      

    Re: 3.2b5 : mod_python doesn't handle properly signals likeKILL,SEGV...  
Graham Dumpleton


View Ip Address Report This Message To A Moderator Edit/Delete Message


 
11-22-05 07:46 AM

Sorry, a couple more questions.

When you kill the child process, is Apache under load, ie., receiving
lots of requests or in an idle state with no requests being received?
Also, do you get the same results if you set "StartServers" to 2 and
kill off only one child process?

If you only have one child process and kill it, and lots of requests are
coming in, am wandering if Apache gets confused, thinking that the newly
spawned child process isn't ready and thus it decides to start a new
one. If this were happening but you have "StartServers" at 2 to begin
with such that you always have at least 1 child process even when you
kill off one of the originals, all those requests coming in would get
bumped off to the remaining child process and Apache may decide
not to create additional child processes.

Hope you can see what I am thinking.

Graham


Michel Jouvin wrote ..
> Graham,
>
> Sorry for the ambiguity. With worker MPM, the max number of process is
> the
> max number of threads divided by the number of thread per process. My
> config is :
>
> # worker MPM
> # StartServers: initial number of server processes to start
> # MaxClients: maximum number of simultaneous client connections
> # MinSpareThreads: minimum number of worker threads which are kept spare
> # MaxSpareThreads: maximum number of worker threads which are kept spare
> # ThreadsPerChild: constant number of worker threads in each server proces
s
>
> <IfModule worker.c>
> MaxClients       245
> StartServers     1
> MinSpareThreads  5
> MaxSpareThreads 10
> ThreadsPerChild 35
> </IfModule>
>
> In our case that means that one process can handle 35 requessts and
> normally we have only one httpd slave running.
>
> After mod_python receives a signal like KILL or SEGV (in fact anything
> except TERM or HUP if  I am right, you can test with kill command), I have
> 8 httpd slave processes and the following message in main Apache error
> log
> file :
>
> [error] server reached MaxClients setting, consider raising the MaxCli
ents
> setting
>
> The only solution is to stop and start (not graceful restart) Apache.
>
> Cheers,
>
> Michel
>
> --On lundi 21 novembre 2005 19:28 -0500 Graham Dumpleton
> <grahamd@dscpl.com.au> wrote:
> 
> with 
> you 
>
>
>
>       ****************************************
*********************
>      * Michel Jouvin                 Email : jouvin@lal.in2p3.fr *
>      * LAL / CNRS                    Tel : +33 1 64468932        *
>      * B.P. 34                       Fax : +33 1 69079404        *
>      * 91898 Orsay Cedex                                         *
>      * France                                                    *
>       ****************************************
*********************






[ Post a follow-up to this message ]



    Sponsored Links  




 





   All times are GMT. The time now is 02:37 PM.      Post New Thread    Post A Reply      
  Last Thread   Next Thread Next


Most Popular forums 

Forum Jump:
Rate This Thread:

Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is OFF
vB code is ON
Smilies are ON
[IMG] code is OFF
 
Medical and Health forum | Computer Games Reviews | Graphics design forum

Back To The Top
Home | Usercp | Faq | Register