On 25 February 2011 19:04, chp <[email protected]> wrote:
> Hi,
>
> Yes it has. User error log:
>
> [Fri Feb 25 10:51:01 2011] [info] mod_wsgi (pid=11198): Create
> interpreter 'xxxxxxxxxx'.
> [Fri Feb 25 10:51:01 2011] [info] mod_wsgi (pid=11198): Adding '/path'
> to path.
> [Fri Feb 25 10:51:01 2011] [info] mod_wsgi (pid=11198): Adding '/path/
> app' to path.
> [Fri Feb 25 10:51:01 2011] [info] mod_wsgi (pid=11198): Adding '/path/
> morepath/someotherpath/site-packages/' to path.
>
>
> In the apache general errorlog i can see these ones:
>
> [Fri Feb 25 10:51:01 2011] [info] mod_wsgi (pid=11264): Initializing
> Python.
> [Fri Feb 25 10:51:01 2011] [info] mod_wsgi (pid=11264): Attach
> interpreter ''.
>
>
> If i comment the vhost error_log directive i can then see errors in
> the general apache error_log
>
>
> [client xx.xx.xx.xx] from xxxx import xxxx, someMethod
> [Fri Feb 25 10:56:40 2011] [error] [client xx.xx.xx.xx] File
> "dddddd", line 84, in <module>
> [Fri Feb 25 10:56:40 2011] [error] [client xx.xx.xx.xx]
> dddddddddddddddddddd())
> [Fri Feb 25 10:56:40 2011] [error] [client xx.xx.xx.xx]
> AttributeError: 'dddddddddd' object has no attribute 'dddddddddd'
>
>
> More Info:
>
> Mod_wsgi compiled with python 2.7.1 in custom location, Apache/2.0.63
>
>
>
> On 24 feb, 16:25, "Joonas Lehtolahti" <[email protected]> wrote:
>> Just a shot in the dark, but have you made sure that Apache has write
>> access to the specified errorlog path?
>>
>> On Thu, 24 Feb 2011 13:12:52 +0200, chp <[email protected]> wrote:
>> > Hi,
>>
>> > I have been testing mod_wsgi 3.3 with cpanel as control panel with
>> > successful results. However i have a problem with the error log and
>> > the vhosts . Configuration:
>>
>> > WSGIScriptAlias / /path/server.wsgi
>> > WSGIDaemonProcess vhostdomain processes=1 threads=1 user=myuser
>> > group=myuser
>> > WSGIProcessGroup vhostdomain
>> > WSGIApplicationGroup vhostdomain
>> > ErrorLog /path/to/user/errorlog
>>
>> > With this configuration errorlogs do not appear neither in the apache
>> > general error_log, nor in the customized vhost error log. The info
>> > logs do appear, though (LogLevel Debug in apache). Maybe there is
>> > something wrong with this config?
>>
>> > Thanks
Any particular reason why you are still using quite old Apache 2.0 and
not Apache 2.2? That version of Apache hasn't been tested against for
quite a long time and if it works it is more by luck than design.
Create a new test WSGI script file and point WSGIScriptAlias at it
instead. In that WSGI script file put:
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]
Make requests against the script and then look at Apache error logs
and work out what messages go to which logs. Post results here.
Graham
--
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.
