Karen hi,
Thanks for the reply. I think I narrowed it down to the way I
installed Python on this server. I can run django applications and
other python scripts just fine from the command line.
It turns out that a quick way to test my Python + Apache setup is
replace the .wsgi file with the following
import socket
def application(environ, start_response):
status = '200 OK'
output = 'Hello world!'
response_headers = [('Content-type', 'text/plain'),
('Content-Length', str(len(output)))]
start_response(status, response_headers)
return [output]
Notice how it bypasses django and tests to see if Python can actually
run in the apache context. If that doesn't work, then it surely means
Python has been installed incorrectly. I googled some more and found
out that Python needs to be installed 'for all users', instead of
'just for me' (there are some required registry settings the xampp
process won't be able to find unless Python has been set up as such).
I switched my .wsgi file back to what it was previously and now my
django app is running!
Thanks again.
On Jul 31, 3:23 pm, Karen Tracey <kmtra...@gmail.com> wrote:
> On Fri, Jul 31, 2009 at 8:53 AM, Michael Ralan <mr5...@gmail.com> wrote:
>
> > I get an (unhelpful) xampp error message that reads
>
> > Microsoft Visual C++ Runtime Library
> > ---------------------------
> > Runtime Error!
>
> > Program: C:\xampp\apache\bin\httpd.exe
>
> > R6034
>
> > An application has made an attempt to load the C runtime library
> > incorrectly.
> > Please contact the application's support team for more information.
>
> > Furthermore, the following is in my apache errors.log
>
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] mod_wsgi
> > (pid=2136): Target WSGI script 'C:/xampp/htdocs/testproject/apache/
> > django.wsgi' cannot be loaded as Python module.
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] mod_wsgi
> > (pid=2136): Exception occurred processing WSGI script 'C:/xampp/htdocs/
> > testproject/apache/django.wsgi'.
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] Traceback (most
> > recent call last):
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] File "C:/xampp/
> > htdocs/testproject/apache/django.wsgi", line 6, in <module>
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] import
> > django.core.handlers.wsgi
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] File "C:\
> > \Python26\\Lib\\site-packages\\django\\core\\handlers\\wsgi.py", line
> > 8, in <module>
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] from django
> > import http
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] File "C:\
> > \Python26\\Lib\\site-packages\\django\\http\\__init__.py", line 5, in
> > <module>
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] from urllib
> > import urlencode
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] File "C:\
> > \Python26\\lib\\urllib.py", line 26, in <module>
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] import
> > socket
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] File "C:\
> > \Python26\\lib\\socket.py", line 46, in <module>
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] import
> > _socket
> > [Fri Jul 31 12:04:18 2009] [error] [client 127.0.0.1] ImportError: DLL
> > load failed: A dynamic link library (DLL) initialization routine
> > failed.
>
> All of which implies to me there's nothing wrong with your definitions, but
> there is something fundamentally broken with the server setup. From the
> traceback you can see mod_wsgi itself is getting loaded fine, the django
> code is being found, etc. Where things go south is when Python tries to
> load a C extension ("import _socket"). If Python can't load C extensions
> there's not much Python code that is going to work on this server.
>
> You don't see an error when you remove your changes to http.conf because
> then you're probably not trying to use Python code at all from this server.
> That doesn't mean there's anything wrong with the changes you made, it just
> means they are exposing an underlying problem you had not run across before
> because it is in code you were not attempting to use.
>
> For some reason Python on this server cannot load C extensions, that's the
> problem you need to fix. I'd Google around for Python, xampp, C extensions,
> that unhelpful error message, etc. and see if there is some trick to getting
> Python to work correctly in this environment. Until you've got a server
> that can actually run Python properly you've no chance of getting Django to
> work on top of it.
>
> Karen
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
