http://code.google.com/p/modwsgi/wiki/ConfigurationIssues#Location_Of_UNIX_Sockets
If however you have other sites working on same Apache which also use
daemon process groups then is odd.
Does this happen on all requests, or only requests which come around
the time of doing an Apache graceful restart? See:
http://groups.google.com/group/modwsgi/browse_frm/thread/8d72119604fe53b6
I have a feeling it may be because of the graceful restart.
Do a full stop and start of Apache and see if it then works.
Graham
> --
> You received this message because you are subscribed to the Google Groups "modwsgi" group.
> To post to this group, send email to mod...@googlegroups.com.
> To unsubscribe from this group, send email to modwsgi+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
>
>
A 500 error is usually a different issue as that daemon socket error
gives a different error number.
What are the errors for the 500 error?
Pinax is not always straightforward to setup from what I have seen.
> then refreshed and now it's just stuck in the loading loop and will
> most likely end up giving me the same error message as above. It times
> out after about 5 - 7 minutes.
That would suggest a thread deadlock in daemon process.
Use:
WSGIApplicationGroup %{GLOBAL}
for the Pinax application.
Graham
8.[Sun Nov 07 16:11:27 2010] [error] [client 24.37.183.231] Premature
end of script headers: django.wsgi
is in a virtual host error log, what messages are in the main Apache
error log at the same time?
That message may be because of crash caused by a request, but may also
be because of a long running request being interrupted when process
restarted. The messages in main Apache error log will give a better
indication of why.
Also, what are the error log messages for the new 500 error?
Graham
[Tue Oct 26 15:53:46 2010] [info] [client 127.0.0.1] mod_wsgi
(pid=3372, process='tests', application=''): Loading WSGI script
'/Users/grahamd/Testing/tests/echo.wsgi'.
which corresponds to when the first request arrives which triggers the
loading of Pinax WSGI script.
Can you find that and post messages from around that point in time?
Graham
Graham
Is Pinax defined in a SSL (port 443) virtual host as well as non SSL
(port 80) virtual host?
Graham
Graham
Sorry, need the actual patch revision.
$ /usr/sbin/httpd -V | grep version
Server version: Apache/2.2.14 (Unix)
The mod_ssl may have no bearing on things, but it has caused some
weird issues with daemon mode in the past.
Graham
http://code.google.com/p/modwsgi/wiki/DebuggingTechniques#Tracking_Request_and_Response
to track in Apache error logs when the WSGI application entry point is
actually being called. This will confirm it is even getting to that
point or whether import of WSGI script itself is failing.
You can also put debug statements to log message at the start and end
of WSGI script file itself. This will track progress of import of WSGI
script.
It doesn't make sense that you aren't see the loading script message.
With LogLevel set to debug as you have, you should see it.
Do you perhaps have SELinux enabled on the box?
Graham