Graham,
No I am not using any PythonImport directive neither on the prod server,
nor on the test server. On the test server, the only mod_python related
directive is :
LoadModule python_module modules/mod_python.so
I'll try you suggestion about adding some logging messages in mod_python.c.
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 wha
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 star
for myself, I have not had problems on ubuntu 5.10 amd64.
Nick
Jim Gallacher wrote:
Michel Jouvin wrote:
Jim,
I am not totally surprised... I am afraid this is a platform specific
issue as we are running mod_python on Tru64. Something like a 64 bits
issue. Does it sound a reasonnable possi
Michel Jouvin wrote:
Jim,
I am not totally surprised... I am afraid this is a platform specific
issue as we are running mod_python on Tru64. Something like a 64 bits
issue. Does it sound a reasonnable possibility ?
I have no idea what may be going on, but that seems as likely as
anything el
Jim,
I am not totally surprised... I am afraid this is a platform specific issue
as we are running mod_python on Tru64. Something like a 64 bits issue. Does
it sound a reasonnable possibility ? How to progress in troubleshooting ?
Michel
--On jeudi 24 novembre 2005 17:41 -0500 Jim Gallacher
Michel,
I can't reproduce the problem on debian i386. I put together a script
that continually greps a apache child pid and kills it. After killing
200 processes there is no change in the total number of apache
processes, and nothing in the apache log other an entry for each process
killed:
I don't know If really need to write a script, this is so simple.
asa/root % ps -e -opid,ppid,cmd | grep http
15601381048577 /www/Web/servers/apache/2.0.54/bin/httpd -k start
15601631560138 /www/Web/servers/apache/2.0.54/bin/httpd -k start
10863961086105 grep http
From thi
Michel Jouvin wrote:
Graham,
I played a little bit with worker MPM parameters. In particular I tested
your suggestion to increase to 2 StartServers. This has no effect on the
problem. I also tried to raise MaxSpareThread to MaxClient and
suppressed child recycling (MaxRequestPerChild=0) to su
Graham,
I played a little bit with worker MPM parameters. In particular I tested
your suggestion to increase to 2 StartServers. This has no effect on the
problem. I also tried to raise MaxSpareThread to MaxClient and suppressed
child recycling (MaxRequestPerChild=0) to suppress restart of chil
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 ch
11 matches
Mail list logo
