On Tue, Jan 5, 2010 at 11:39 AM, dcorbe <dco...@gmail.com> wrote: > Hi, > > I've tried the (relatively straight-forward-looking) steps to get > django and mod_wsgi working together with little success thus far. > I'm trying to run a simple django application from my Apache web > server. The documentation doesn't make it clear whether user= and > group= needs to be set to the webserver's uid/gid (which it currently > is) or whether it needs to be set to the uid/gid that own the > application (which I tried with no success). Beyond that I'm not sure > how to proceed. > > When I attempt to hit the site (http://blog.corbe.net) it simply times > out. > > I get an Internal Server Error page if I let the browser sit long enough trying to retrieve the page. I believe the default deadlock timeout for mod_wsgi is 5 minutes and that may be about how long it took so you may find some error messages logged about that, if it was deadlock detection that kicked in and eventually triggered the error. You might try setting LogLevel to debug to see if that offers any more clues about what is going on.
More info that might be a clue: if I telnet to blog.corbe.net 80 and type in GET /, I get a page in response. But that isn't exactly what the browser is sending, it sends (probably) GET / HTTP/1.1. Adding the HTTP spec after the GET / seems to be what is causing the trouble. Seems like a clue but I have no idea what it means. 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-us...@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.
