mod_wsgi (pid=11920): Target WSGI script '/home/dingo/fossacademy/lernanta/wsgi/batucada.wsgi' cannot be loaded as Python module.[Sun Jan 06 09:53:34 2013] [error] [client 119.82.82.76] mod_wsgi (pid=11920): Exception occurred processing WSGI script '/home/dingo/fossacademy/lernanta/wsgi/batucada.wsgi'.[Sun Jan 06 09:53:34 2013] [error] [client 119.82.82.76] Traceback (most recent call last):[Sun Jan 06 09:53:34 2013] [error] [client 119.82.82.76] File "/home/dingo/fossacademy/lernanta/wsgi/batucada.wsgi", line 20, in <module>[Sun Jan 06 09:53:34 2013] [error] [client 119.82.82.76] import manage[Sun Jan 06 09:53:34 2013] [error] [client 119.82.82.76] ImportError: No module named manage
import sys
sys.path.append('enter_path_of_directory')
Hi,
Try WSGI attached with this mail.
now i am getting this error also i fixed group to www-data for wsgi file[Sun Jan 06 13:24:15 2013] [error] [client 119.82.82.76] Premature end of script headers: batucada.wsgi/home/dingo/.virtualenvs/fossacademy/bin/python: can't open file 'mod_wsgi': [Errno 2] No such file or directory[Sun Jan 06 13:24:21 2013] [error] [client 119.82.82.76] Premature end of script headers: batucada.wsgi
A: If using daemon mode, this is a symptom of the mod_wsgi daemon process crashing when handling a request. You would probably also see the message 'segmentation fault'. See answer for question about 'segmentation fault' above.
This error message can also occur where you haven't configured Apache correctly and your WSGI script file is being executed as a CGI script instead.
-Satya
instead.hmm just ran a test check fossacademy.org , we need to just fix the env variable errors , things on the apache side are just fine