2010/1/22 janedenone <[email protected]>: > On Jan 22, 12:00 pm, Graham Dumpleton <[email protected]> > wrote: >> BTW, are you by chance also loading mod_python into the same Apache. >> If you are then disable it and do a full stop and start of Apache. The >> mod_python module can cause various conflicts, including causing >> daemon mode to not work in some rare cases. > > That's exactly what happened (I found a relevant thread *after* > posting, sorry - http://groups.google.com/group/modwsgi/msg/9d29b81bc7297e72). > > I do load mod_python next to mod_wsgi, but I also did that on my local > machine OS X/FreeBSD, and no problem occurred. That's why I did not > think about disabling mod_python first. On OS X, I can access > different app1 (using mod_python) and app2 (using mod_wsgi) in > parallel. > > Anyway: I know what causes the error now, and will disable mod_python > for all apps running on my server.
Alternatively you ensure that mod_python is built/linked against same Python version and that in linking Python it is using a shared library. See: http://code.google.com/p/modwsgi/wiki/InstallationIssues Graham -- 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.
