On 12/01/2010 23:21, Graham Dumpleton wrote:
Just the LoadModule line for mod_python is enough to cause the
problem. This is because it is still loaded even if not used.
Also make sure you did a complete 'stop' of Apache and not just a
Linux init reload, as sometimes mod_python doesn't unload properly the
Python library.
If still a problem, you perhaps have SELinux extensions enabled and it
should be disabled or properly configured.
Graham
It's a bit strange. Last night I made a point of removing the port, the
LoadModule line from httpd.conf and everything connected with
mod_python. Apache has been fully stopped and started again a number of
times. I also use FreeBSD and don't have any Linux compatibility or
ports stuff installed, so that shouldn't be an issue.
I will check things out again to see if I can find out what the problem
is. *fingers crossed* it goes away.
I was hoping to avoid it, but if there's nothing else that might be
causing it, I'll install Apache and mod_wsgi on a fresh box that has
never had any web stuff on it before, and see if that makes a difference.
Thanks again,
mog
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
