| Graham Dumpleton 2005-12-10, 2:45 am |
| Just to make sure, are you using PythonImport directive at all? Want
to eliminate
this as these get run regardless of whether a request against a
mod_python
handler is received. If the code associated with PythonImport took
some time
to run, that might be a contributor.
Anyway, not sure what else to suggest. I would probably start adding
extra
logging calls in the mod_python.c file of mod_python so that one
could see when
the Apache child process init function for mod_python is entered and
exited for
each process ID. That way could see if that is returning quickly or
taking some
time.
Graham
On 10/12/2005, at 10:38 AM, Michel Jouvin wrote:
> I am still fighting with my mod_python problem on Tru64. I have
> been able to set up a test configuration with just standard Apache
> modules and mod_python loaded (no php, no dav, no subversion...)
> and without any url activating a mod_python handler.
>
> The problem remains the same. Just after starting Apache, with no
> request received by this server, I 'kill -KILL' httpd slave and
> this leads to the restart of other children that don't succeed to
> initialize properly. Apache restarts as many children as it can
> before giving up when it reaches MaxClients.
>
> Any idea on how to troubleshoot this and get any useful information
> to debug this problem ?
>
> Thanks in advance.
>
> Michel
>
> --On jeudi 24 novembre 2005 23:43 +0100 Michel Jouvin
> <jouvin@lal.in2p3.fr> wrote:
>
>
>
>
>
> ****************************************
*********************
> * Michel Jouvin Email : jouvin@lal.in2p3.fr *
> * LAL / CNRS Tel : +33 1 64468932 *
> * B.P. 34 Fax : +33 1 69079404 *
> * 91898 Orsay Cedex *
> * France *
> ****************************************
*********************
>
>
|