On 10 February 2011 18:27, commonzenpython <[email protected]> wrote: > thanks for the reply, > no mod_python is not being loaded, also i ran ldd mod_wsgi.so on the > shell and it gave me: > ldd: ./mod_wsgi.so: No such file or directory
It was assumed you would know to replace mod_wsgi.so with the full path to where the mod_wsgi.so is installed that Apache is using, or change your working directory to be the same directory as the mod_wsgi.so file resided. If you haven't cleaned your source directory, you could also do: ldd .libs/mod_wsgi.so as the compiled mod_wsgi.so file will be in the .libs subdirectory. Check both. That which is installed into Apache and that which is still in the .libs subdirectory of the source directory. > checking the error logs i found something interesting, it says : > Apache/2.0.63 (Unix) mod_ssl/2.0.63 OpenSSL/0.9.7a > mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 > mod_wsgi/3.2 Python/2.4.3 configured > > the wsgi i compiled using 2.7 was version 3.3 not 3.2 Then possibly the new compiled mod_wsgi.so has not been installed into Apache modules directory, was installed into different location to where Apache is loading it (an old version) from, or mod_wsgi when being compiled found and different Apache installation and installed it there instead. For the latter, try using the --with-apxs option as documented in build instructions for mod_wsgi to explicitly indicate which Apache installation you want to use. 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.
