2010/1/12 sborf <[email protected]>:
> Thanks for your prompt reply,
>
> On Jan 11, 10:24 pm, Graham Dumpleton <[email protected]>
> wrote:
>> To comment further I really need to see the exact messages from the
>> Apache error log.
>
> The following is an extract from errors.log (apachectl start and stop
> logs):
>
> [Thu Jan 01 22:42:18 1970] [debug] mod_wsgi.c(11253): mod_wsgi
> (pid=2006): Reset default group for daemon process group 'etproWS' to
> gid=-1.
> [Thu Jan 01 22:42:18 1970] [debug] mod_wsgi.c(9921): mod_wsgi
> (pid=2006): Socket for 'etproWS' is '/usr/logs/wsgi.2006.0.1.sock'.
> [Thu Jan 01 22:42:19 1970] [info] mod_wsgi (pid=2007): Starting
> process 'etproWS' with uid=99, gid=4294967295 and threads=1.
> [Thu Jan 01 22:42:19 1970] [info] mod_wsgi (pid=2007): Initializing
> Python.
> [Thu Jan 01 22:42:19 1970] [notice] Apache/2.0.54 (Unix) mod_wsgi/3.1
> Python/2.6.2 configured -- resuming normal operations
> [Thu Jan 01 22:42:19 1970] [info] Server built: Jan 11 2010 11:30:45
> [Thu Jan 01 22:42:19 1970] [debug] prefork.c(956): AcceptMutex:
> sysvsem (default: sysvsem)
> [Thu Jan 01 22:42:19 1970] [info] mod_wsgi (pid=2008): Initializing
> Python.
> [Thu Jan 01 22:42:19 1970] [info] mod_wsgi (pid=2007): Attach
> interpreter ''.
> [Thu Jan 01 22:42:19 1970] [info] mod_wsgi (pid=2008): Attach
> interpreter ''.
> [Thu Jan 01 22:42:19 1970] [error] mod_wsgi (pid=2008): Unable to
> import 'site' module.
> [Thu Jan 01 22:42:30 1970] [info] mod_wsgi (pid=2008): Create
> interpreter '127.0.0.1:8000|'.
> [Thu Jan 01 22:42:30 1970] [error] mod_wsgi (pid=2008): Unable to
> import 'site' module.
> [Thu Jan 01 22:42:30 1970] [info] [client 192.168.10.80] mod_wsgi
> (pid=2008, process='', application='127.0.0.1:8000|'): Loading WSGI
> script '/usr/local/lib/python2.6/site-packages/
> ApplicationLibraries-0.0.0-py2.6.egg/homepf/apache/django.wsgi'.
> [Thu Jan 01 22:42:30 1970] [error] [client 192.168.10.80] mod_wsgi
> (pid=2008): Target WSGI script '/usr/local/lib/python2.6/site-packages/
> ApplicationLibraries-0.0.0-py2.6.egg/homepf/apache/django.wsgi' cannot
> be loaded as Python module.
> [Thu Jan 01 22:42:30 1970] [error] [client 192.168.10.80] mod_wsgi
> (pid=2008): Exception occurred processing WSGI script '/usr/local/lib/
> python2.6/site-packages/ApplicationLibraries-0.0.0-py2.6.egg/homepf/
> apache/django.wsgi'.
> [Thu Jan 01 22:42:30 1970] [error] Traceback (most recent call last):
> [Thu Jan 01 22:42:30 1970] [error] File "/usr/local/lib/python2.6/
> site-packages/ApplicationLibraries-0.0.0-py2.6.egg/homepf/apache/
> django.wsgi", line 1, in <module>
> [Thu Jan 01 22:42:30 1970] [error] import os, sys
> [Thu Jan 01 22:42:30 1970] [error] ImportError: No module named os
> [Thu Jan 01 23:04:14 1970] [info] mod_wsgi (pid=2008): Destroying
> interpreters.
> [Thu Jan 01 23:04:14 1970] [info] mod_wsgi (pid=2008): Destroy
> interpreter '127.0.0.1:8000|'.
> [Thu Jan 01 23:04:14 1970] [info] mod_wsgi (pid=2008): Cleanup
> interpreter ''.
> [Thu Jan 01 23:04:14 1970] [info] mod_wsgi (pid=2008): Terminating
> Python.
> [Thu Jan 01 23:04:14 1970] [error] Exception ImportError: 'No module
> named atexit' in 'garbage collection' ignored
> Could not find platform independent libraries <prefix>
> Could not find platform dependent libraries <exec_prefix>
> Consider setting $PYTHONHOME to <prefix>[:<exec_prefix>]
> 'import site' failed; use -v for traceback
> 'import site' failed; use -v for traceback
> Fatal Python error: unexpected exception during garbage collection
> [Thu Jan 01 23:04:14 1970] [notice] SIGHUP received. Attempting to
> restart
>
>> One thing though to perhaps try, is to use the WSGIPythonHome
>> directive to specify the home directory for the Python installation in
>> case it isn't being derived correctly.
>
> I tried it but without success; I put this directive just after the
> WSGIDaemonProcess one.
>
>
> However I worked around the problem: instead of running "apachectl
> start" which spoons another shell without environment, I executed ./
> httpd and before it I set into the environment PATH variable the path
> to the python executable, so doing all works fine!
For when you set WSGIPythonHome, can you look through log files for
line generated by:
ap_log_error(APLOG_MARK, WSGI_LOG_INFO(0), wsgi_server,
"mod_wsgi (pid=%d): Python home %s.", getpid(),
wsgi_server_config->python_home);
I want to confirm that WSGIPythonHome was actually applied and what
you set it to. It should work just as if PATH was set.
Also post what you get for value of 'sys.prefix' when printed out from
command line Python and also what you get for 'which python'.
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.
