global apache ErrorLog:
[Thu Mar 03 13:57:15 2011] [error] GLOBAL SYS.STDOUT
[Thu Mar 03 13:57:15 2011] [error] GLOBAL SYS.STDERR
[Thu Mar 03 13:57:15 2011] [error] REQUEST SYS.STDOUT
[Thu Mar 03 13:57:15 2011] [error] REQUEST SYS.STDERR

I couldn't find the wsgi error logged anywhere.





On Mar 3, 1:24 pm, Graham Dumpleton <[email protected]>
wrote:
> On 4 March 2011 08:16, bc <[email protected]> wrote:
>
> > No change after upgrading to 3.3.
>
> As per parallel discussion going on on list (which unfortunately been
> too busy to followup on), create the following test WSGI script and
> see what output ends up in what log files.
>
> import sys
>
> print "GLOBAL SYS.STDOUT"
> print >> sys.stderr, "GLOBAL SYS.STDERR"
>
> def application(environ, start_response):
>
>    print "REQUEST SYS.STDOUT"
>    print >> sys.stderr, "REQUEST SYS.STDERR"
>
>    print >> environ["wsgi.errors"], "REQUEST WSGI.ERRORS"
>
>    status = '200 OK'
>    output = 'Hello World!'
>
>    response_headers = [('Content-type', 'text/plain'),
>                        ('Content-Length', str(len(output)))]
>    start_response(status, response_headers)
>
>    return [output]
>
> Graham
>
>
>
> > On Mar 1, 3:06 pm, Graham Dumpleton <[email protected]>
> > wrote:
> >> Can you upgrade to mod_wsgi 3.3.
>
> >> Fixed in 3.3 was:
>
> >> 3. Logging not appearing in Apache error log files when using daemon mode
> >> and have multiple virtual hosts against same server name. See:
>
> >>  http://code.google.com/p/modwsgi/issues/detail?id=204
>
> >> So, actually only fixed in most recent public release.
>
> >> Graham
>
> >> On 2 March 2011 09:56, bc <[email protected]> wrote:
>
> >> > On Mar 1, 2:47 pm, Graham Dumpleton <[email protected]>
> >> > wrote:
> >> >> What version of mod_wsgi are you using? Some older versions of
> >> >> mod_wsgi could see such logging go missing where HTTPS was used or
> >> >> other strange VirtualHost configurations.
>
> >> >> More details about your Apache configuration, use of VirtualHost,
> >> >> where setting ErrorLog directive etc would be helpful to understand
> >> >> the problem.
>
> >> > Version 3.2. We are using https. There's a virtualhost defined on the
> >> > server name. LogLevel is set in the global config and the ssl config.
> >> > There is a separate ErrorLog directive in the ssl config, however
> >> > there's no indication of the error in that log, either.
>
> >> > --
> >> > You received this message because you are subscribed to the Google 
> >> > Groups "modwsgi" group.
> >> > To post to this group, send email to [email protected].
> >> > To unsubscribe from this group, send email to 
> >> > [email protected].
> >> > For more options, visit this group 
> >> > athttp://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 [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en.

Reply via email to