One of the other things I am not seeing in your logs is the line like:
[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
On 8 November 2010 09:30, sh4d0w <ad...@servqc.net> wrote:
> After looking over my post i noticed the time stamps for the httpd log
> don't really match up with the ones on the vhost so i looked over the
> main log again and I don't see anything related to the error in the
> vhost log at all. As far as the 500 message goes it does not post
> anything to the vhost log nor the main log at all.
>
> On Nov 7, 5:00 pm, sh4d0w <ad...@servqc.net> wrote:
>> Thats the thing apache doesn't log anything in relation to this in the
>> main log.
>> Here is my apache log from the stop and start on.
>> [Sun Nov 07 16:33:16 2010] [debug] prefork.c(1013): AcceptMutex:
>> sysvsem (default: sysvsem)
>> [Sun Nov 07 16:33:16 2010] [info] mod_wsgi (pid=15590): Attach
>> interpreter ''.
>> [Sun Nov 07 16:33:16 2010] [info] mod_wsgi (pid=15590): Adding '/usr/
>> local/lib/python2.6' to path.
>> [Sun Nov 07 16:33:16 2010] [info] mod_wsgi (pid=15592): Python home /
>> usr/local.
>> [Sun Nov 07 16:33:16 2010] [info] mod_wsgi (pid=15592): Initializing
>> Python.
>> [Sun Nov 07 16:33:16 2010] [info] mod_wsgi (pid=15591): Attach
>> interpreter ''.
>> [Sun Nov 07 16:33:16 2010] [info] mod_wsgi (pid=15591): Adding '/usr/
>> local/lib/python2.6' to path.
>> [Sun Nov 07 16:33:16 2010] [info] mod_wsgi (pid=15592): Attach
>> interpreter ''.
>> [Sun Nov 07 16:33:16 2010] [info] mod_wsgi (pid=15592): Adding '/usr/
>> local/lib/python2.6' to path.
>> [Sun Nov 07 16:33:19 2010] [debug] proxy_util.c(1818): proxy: grabbed
>> scoreboard slot 0 in child 15595 for worker proxy:reverse
>> [Sun Nov 07 16:33:19 2010] [debug] proxy_util.c(1837): proxy: worker
>> proxy:reverse already initialized
>> [Sun Nov 07 16:33:19 2010] [debug] proxy_util.c(1934): proxy:
>> initialized single connection worker 0 in child 15595 for (*)
>> [Sun Nov 07 16:33:19 2010] [info] mod_wsgi (pid=15595): Python home /
>> usr/local.
>> [Sun Nov 07 16:33:19 2010] [info] mod_wsgi (pid=15595): Initializing
>> Python.
>> [Sun Nov 07 16:33:19 2010] [info] mod_wsgi (pid=15595): Attach
>> interpreter ''.
>> [Sun Nov 07 16:33:19 2010] [info] mod_wsgi (pid=15595): Adding '/usr/
>> local/lib/python2.6' to path.
>> [Sun Nov 07 16:33:24 2010] [debug] proxy_util.c(1818): proxy: grabbed
>> scoreboard slot 0 in child 15601 for worker proxy:reverse
>> [Sun Nov 07 16:33:24 2010] [debug] proxy_util.c(1837): proxy: worker
>> proxy:reverse already initialized
>> [Sun Nov 07 16:33:24 2010] [debug] proxy_util.c(1934): proxy:
>> initialized single connection worker 0 in child 15601 for (*)
>> [Sun Nov 07 16:33:24 2010] [info] mod_wsgi (pid=15601): Python home /
>> usr/local.
>> [Sun Nov 07 16:33:24 2010] [info] mod_wsgi (pid=15601): Initializing
>> Python.
>> [Sun Nov 07 16:33:24 2010] [info] mod_wsgi (pid=15601): Attach
>> interpreter ''.
>> [Sun Nov 07 16:33:24 2010] [info] mod_wsgi (pid=15601): Adding '/usr/
>> local/lib/python2.6' to path.
>> [[Sun Nov 07 16:39:18 2010] [debug] proxy_util.c(1837): proxy: worker
>> proxy:reverse already initialized
>> [Sun Nov 07 16:39:18 2010] [debug] proxy_util.c(1934): proxy:
>> initialized single connection worker 0 in child 15982 for (*)
>> [Sun Nov 07 16:39:18 2010] [info] mod_wsgi (pid=15982): Python home /
>> usr/local.
>> [Sun Nov 07 16:39:18 2010] [info] mod_wsgi (pid=15982): Initializing
>> Python.
>> [Sun Nov 07 16:39:18 2010] [info] mod_wsgi (pid=15982): Attach
>> interpreter ''.
>> [Sun Nov 07 16:39:18 2010] [info] mod_wsgi (pid=15982): Adding '/usr/
>> local/lib/python2.6' to path.
>> [Sun Nov 07 16:43:41 2010] [debug] proxy_util.c(1818): proxy: grabbed
>> scoreboard slot 0 in child 16290 for worker proxy:reverse
>> [Sun Nov 07 16:43:41 2010] [debug] proxy_util.c(1837): proxy: worker
>> proxy:reverse already initialized
>> [Sun Nov 07 16:43:41 2010] [debug] proxy_util.c(1934): proxy:
>> initialized single connection worker 0 in child 16290 for (*)
>> [Sun Nov 07 16:43:41 2010] [info] mod_wsgi (pid=16290): Python home /
>> usr/local.
>> [Sun Nov 07 16:43:41 2010] [info] mod_wsgi (pid=16290): Initializing
>> Python.
>> [Sun Nov 07 16:43:41 2010] [info] mod_wsgi (pid=16290): Attach
>> interpreter ''.
>> [Sun Nov 07 16:43:41 2010] [info] mod_wsgi (pid=16290): Adding '/usr/
>> local/lib/python2.6' to path.
>> [Sun Nov 07 16:48:56 2010] [info] [client 94.218.24.87]
>> (104)Connection reset by peer: core_output_filter: writing data to the
>> network
>>
>> On Nov 7, 4:56 pm, Graham Dumpleton <graham.dumple...@gmail.com>
>> wrote:
>>
>>
>>
>> > If:
>>
>> > 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
>>
>> > On 8 November 2010 08:45, sh4d0w <ad...@servqc.net> wrote:
>>
>> > > Sorry i missed the one question in the prior most yes .. it does this
>> > > every time .. only for this pinax app.
>>
>> > > The initial error message was this:
>>
>> > > Internal Server Error
>> > > The server encountered an internal error or misconfiguration and was
>> > > unable to complete your request.
>>
>> > > Please contact the server administrator,
>> > > webmas...@ourislandgeorgia.net and inform them of the time the error
>> > > occurred, and anything you might have done that may have caused the
>> > > error.
>>
>> > > More information about this error may be available in the server error
>> > > log.
>>
>> > > Additionally, a 500 Internal Server Error error was encountered while
>> > > trying to use an ErrorDocument to handle the request.
>>
>> > > The wsgi file looks like this:
>> > > import os, sys
>> > > import site
>> > > site.addsitedir('/home/ourianet/public_html/virtfs/lib/python2.6/site-
>> > > packages')
>> > > site.addsitedir('/home/ourianet/public_html')
>> > > sys.path.append('/home/ourianet/public_html/virtfs/lib/python2.6/site-
>> > > packages')
>> > > sys.path.append('/home/ourianet/public_html/virtfs/lib/python2.6')
>>
>> > > #os.environ['DJANGO_SETTINGS_MODULE'] = 'hello.settings'
>> > > os.environ['DJANGO_SETTINGS_MODULE'] = 'testpinax.settings'
>> > > import django.core.handlers.wsgi
>> > > application = django.core.handlers.wsgi.WSGIHandler()
>>
>> > > I know it's ugly .. but this same setup works on all the other sites.
>> > > The hello app works fine also when i change it to load that instead of
>> > > the pinax site.
>>
>> > > Here is my vhost include:
>> > > <IfModule mod_alias.c>
>> > > Alias /robots.txt /home/ourianet/public_html/fcabinet/media/robots.txt
>> > > Alias /favicon.ico /home/ourianet/public_html/fcabinet/media/
>> > > favicon.ico
>> > > Alias /media /home/ourianet/public_html/fcabinet/media
>> > > Alias /adminmedia /home/ourianet/public_html/fcabinet/media/adminmedia
>> > > </IfModule>
>>
>> > > <IfModule mod_wsgi.c>
>> > > WSGIScriptAlias / /home/ourianet/public_html/django/django.wsgi
>> > > WSGIDaemonProcess ourianet processes=2 threads=1 display-name=%{GROUP}
>> > > WSGIProcessGroup ourianet
>> > > WSGIApplicationGroup %{GLOBAL}
>> > > </IfModule>
>>
>> > > <Location />
>> > > SetHandler None
>> > > </Location>
>>
>> > > <LocationMatch />
>> > > SetHandler None
>> > > </LocationMatch>
>>
>> > > AddHandler fastcgi-script .fcgi .fcg .fpl
>> > > ErrorDocument 401 "Authentication Error"
>> > > ErrorDocument 403 "Forbidden"
>>
>> > > Again not sexy but working in most cases.
>>
>> > > On Nov 7, 4:39 pm, Graham Dumpleton <graham.dumple...@gmail.com>
>> > > wrote:
>> > >> On 8 November 2010 08:35, sh4d0w <ad...@servqc.net> wrote:
>>
>> > >> > So i did exactly as you said did a full stop and start of the apache
>> > >> > web server.
>> > >> > Then revisted the domain in question. I instantly got a 500 error
>>
>> > >> 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
>>
>> > >> > On Nov 7, 4:31 pm, Graham Dumpleton <graham.dumple...@gmail.com>
>> > >> > wrote:
>> > >> >> Usually this is because of:
>>
>> > >> >> http://code.google.com/p/modwsgi/wiki/ConfigurationIssues#Location_Of...
>>
>> > >> >> 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/8d72119604fe...
>>
>> > >> >> 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
>>
>> > >> >> On 8 November 2010 08:26, sh4d0w <ad...@servqc.net> wrote:
>>
>> > >> >> > Using mod_wsgi 3.3 with python 2.6 on centos 5
>> > >> >> > O.K not sure where to ask this but if anyone can give any input i'd
>> > >> >> > much appreciate it. trying to setup pinax on a server i already
>> > >> >> > have
>> > >> >> > like 30 django sites working perfectly fine on. and with a pinax
>> > >> >> > app
>> > >> >> > i get. the following messages in my error log:
>>
>> > >> >> > 1.[Sun Nov 07 16:11:24 2010] [info] mod_wsgi (pid=12090): Shutdown
>> > >> >> > requested 'ourianet'.
>> > >> >> > 2.[Sun Nov 07 16:11:24 2010] [info] mod_wsgi (pid=12090): Stopping
>> > >> >> > process 'ourianet'.
>> > >> >> > 3.[Sun Nov 07 16:11:24 2010] [info] mod_wsgi (pid=12090):
>> > >> >> > Destroying
>> > >> >> > interpreters.
>> > >> >> > 4.[Sun Nov 07 16:11:24 2010] [info] mod_wsgi (pid=12090): Cleanup
>> > >> >> > interpreter ''.
>> > >> >> > 5.[Sun Nov 07 16:11:24 2010] [info] mod_wsgi (pid=12090):
>> > >> >> > Terminating
>> > >> >> > Python.
>> > >> >> > 6.[Sun Nov 07 16:11:24 2010] [info] mod_wsgi (pid=12089): Shutdown
>> > >> >> > requested 'ourianet'.
>> > >> >> > 7.[Sun Nov 07 16:11:24 2010] [info] mod_wsgi (pid=12090): Python
>> > >> >> > has
>> > >> >> > shutdown.
>> > >> >> > 8.[Sun Nov 07 16:11:27 2010] [error] [client 24.37.183.231]
>> > >> >> > Premature
>> > >> >> > end of script headers: django.wsgi
>> > >> >> > 9.[Sun Nov 07 16:11:27 2010] [error] [client 24.37.183.231] (2)No
>>
>> ...
>>
>> read more »- Hide quoted text -
>>
>> - Show quoted text -
>
> --
> You received this message because you are subscribed to the Google Groups
> "modwsgi" group.
> To post to this group, send email to modw...@googlegroups.com.
> To unsubscribe from this group, send email to
> modwsgi+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/modwsgi?hl=en.
>
>
--
You received this message because you are subscribed to the Google Groups
"modwsgi" group.
To post to this group, send email to modw...@googlegroups.com.
To unsubscribe from this group, send email to
modwsgi+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/modwsgi?hl=en.
