2010/4/13 MMRUser <[email protected]>: > ldd mod_wsgi.so out puts : > > libpython2.4.so.1.0 => /usr/lib64/libpython2.4.so.1.0 > (0x00002b6f95177000) > libpthread.so.0 => /lib64/libpthread.so.0 (0x00002b6f954a9000) > libdl.so.2 => /lib64/libdl.so.2 (0x00002b6f956c4000) > libutil.so.1 => /lib64/libutil.so.1 (0x00002b6f958c9000) > libm.so.6 => /lib64/libm.so.6 (0x00002b6f95acc000) > libc.so.6 => /lib64/libc.so.6 (0x00002b6f95d4f000) > /lib64/ld-linux-x86-64.so.2 (0x0000003aaec00000) > > seems like it's the older version how to correct this one, I used the > rpm "mod_wsgi-3.2-1.el5.x86_64.rpm" to install mos_wsgi is that the > wrong rpm ?..
If you got it from http://codepoint.net/attachments/mod_wsgi then it is built against the default Python install: 2.4 BTW what is so special about Python 2.5/2.6 that some people must prove to the world that their servers run it? The Django site says it works with Python 2.4. Redhat 5 as it is can run for years without a single glitch and I think that is the main goal for a production server, stability. Why would someone want to screw that and ask for a life of trouble? If their applications where that demanding they would not be running Django or any other morbidly obese framework. Why not just shift the server maintenance effort to application development? The application users will never know what Python version they are running or any other technical details. I don't know where people is getting the advice to upgrade Python. I think it is plain wrong, especially for not experienced server admins. Regards, Clodoaldo > > System: > Redhat Enterprise Linux 5.4 (64bit) > > On Apr 13, 6:49 pm, Graham Dumpleton <[email protected]> > wrote: >> On 13 April 2010 22:17, MMRUser <[email protected]> wrote: >> >> > I'm getting this error on my server log.... I have two versions of >> > Python 2.4 and 2.5 Django is installed in to 2.6 and it's the default >> > python on my system, also it can be imported through command line.. >> >> > I tried then it raised no module name os >> > WSGIPythonHome /usr/local >> >> > [Tue Apr 13 12:04:44 2010] [error] Exception exceptions.ImportError: >> > 'No module named ate$ >> > 'import site' failed; use -v for traceback >> >> There is no Python installation under /usr/local of the version that >> mod_wsgi has been compiled against. >> >> Run: >> >> ldd mod_wsgi.so >> >> on the .so file that was generated by built process to work out which >> Python it was compiled against. It possibly isn't the version you want >> to use. >> >> > Fatal Python error: unexpected exception during garbage collection >> > [Tue Apr 13 12:04:44 2010] [notice] caught SIGTERM, shutting down >> > [Tue Apr 13 12:04:44 2010] [notice] suEXEC mechanism enabled >> > (wrapper: /usr/sbin/suexec) >> > [Tue Apr 13 12:04:44 2010] [warn] module wsgi_module is already >> > loaded, skipping >> >> You have duplicate LoadModule lines for mod_wsgi. Either you have >> listed it twice by accident, or your snippet configuration file is >> being included more than once for some reason. >> >> Graham >> >> > [Tue Apr 13 12:04:44 2010] [notice] Digest: generating secret for >> > digest authentication .$ >> > [Tue Apr 13 12:04:44 2010] [notice] Digest: done >> > [Tue Apr 13 12:04:44 2010] [notice] Apache/2.2.3 (Red Hat) configured >> > -- resuming normal $ >> > [Tue Apr 13 12:09:03 2010] [error] [client 127.0.0.1] Directory index >> > forbidden by Option$ >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] mod_wsgi >> > (pid=24108): Target WSGI s$ >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] mod_wsgi >> > (pid=24108): Exception occ$ >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] Traceback (most >> > recent call last): >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] File "/var/www/ >> > html/testproject/a$ >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] import >> > django.core.handlers.wsgi >> > [Tue Apr 13 12:09:14 2010] [error] [client 127.0.0.1] ImportError: No >> > module named django$ >> >> > -- >> > 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 >> > athttp://groups.google.com/group/modwsgi?hl=en. > > -- > 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. > > -- 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.
