[mod_python] Problems with mod_python on MacOS

Paul Sholtz paul at doublegemini.com
Mon Jun 27 09:26:29 EDT 2005


Thanks for all the help.

I got it to work, and ...... I'm not 100% sure what I did to make it  
work. Just kinda seemed to "magically" start working on it own....

I did notice this, though... (and I'm not sure this is what caused it  
to start working, but... it is something that I did *differently*)..  
Before, whenever I was making changes to httpd.conf or the mptest.py  
file, etc, I would just type "apachectl restart" on the command line  
and figure that the changes would be applied. Since I saw the message  
"mod_python/3.1.4 Python/2.3.5 configured -- resuming normal  
operations" come through in error_log, I figured that the changes  
were being applied, etc

What I did this time, was do a "hard reboot" on Apache, by first  
stopping it ("apachectl stop") and then starting it back up  
("apachectl start").

For whatever reason, that seems to have made it work....

On Jun 26, 2005, at 7:59 PM, Graham Dumpleton wrote:

> Scott Sanders wrote ..
>> I was receiving this on OS X because mod_python was loading, but it
>> was using the wrong copy of python, so the import _apache failed and
>> caused the server error, though NOTHING came out in the logs.
> The lack of logging in that situation is the sort of thing that the  
> bug
> report I referred to was about. Thus, known issue which masks the
> true nature of a couple of problems. Already addressed for next  
> version.
> Graham
> _______________________________________________
> Mod_python mailing list
> Mod_python at modpython.org
> http://mailman.modpython.org/mailman/listinfo/mod_python

More information about the Mod_python mailing list