2008/10/6 gert <[EMAIL PROTECTED]>:
>
> On Oct 6, 10:33 am, gert <[EMAIL PROTECTED]> wrote:
>> On Oct 6, 10:18 am, "Graham Dumpleton" <[EMAIL PROTECTED]>
>> wrote:
>>
>> > 2008/10/6 gert <[EMAIL PROTECTED]>:
>>
>> > > Failed requests:        9993 But I did have 1564.21 requests per second
>> > > doh :-)
>> > > anywayhttp://87.98.218.86/gil.pyseemto work ?
>>
>> > >http://87.98.218.86/bench.txt(addedmy apache.conf)
>>
>> > >http://87.98.218.86/bench.htm
>>
>> > > So did we find a gil bug in Grahams mighty code ?
>>
>> > No one will never know because you never post enough information. If
>> > the script is generating a 500 error response, what was the traceback
>> > or other error in the Apache error log? Have you tried to debug what
>> > was causing the error?
>>
>> > Graham
>>
>> I have alooooot of this
>>
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1] Traceback (most
>> recent cal                                   l last):
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1]   File "/srv/www/
>> gil.py",                                    line 11, in application
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1]
>> db.query("SELECT test                                    FROM test")
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1] InterfaceError:
>> (0, '')
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1] mod_wsgi
>> (pid=1134): Excep                                   tion occurred
>> processing WSGI script '/srv/www/gil.py'.
>>
>> Cool I noticed that pressing f5 it sometimes works and sometimes
>> doesn't lol :) :) :)
>>
>> when it works i get
>>
>> [Mon Oct 06 10:30:46 2008] [info] [client 80.200.216.121] mod_wsgi
>> (pid=1542, process='', application=''): Loading WSGI script '/srv/www/
>> gil.py'.
>>
>> When it doesnt i get
>>
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1] Traceback (most
>> recent cal                                   l last):
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1]   File "/srv/www/
>> gil.py",                                    line 11, in application
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1]
>> db.query("SELECT test                                    FROM test")
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1] InterfaceError:
>> (0, '')
>> [Mon Oct 06 09:56:02 2008] [error] [client 127.0.0.1] mod_wsgi
>> (pid=1134): Excep                                   tion occurred
>> processing WSGI script '/srv/www/gil.py'.
>
> This is what i get in gdb with cflag -g in make file

Which says absolutely nothing.

Just because I suggested to someone else that gdb could be used to
debug an issue, doesn't mean it is then a magic bullet that is
applicable to every situation. It will only be of use it quite
specific situations.

I sincerely hope that the debug suggestions you give to people will
not now expand to, 'replace your whole Apache configuration with
yours' and 'run gdb to work out problem'. Both suggestions aren't
helpful. :-)

Graham

> Starting program: /usr/sbin/apache2 -X
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [Thread debugging using libthread_db enabled]
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> ---Type <return> to continue, or q <return> to quit---
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> (no debugging symbols found)
> [New Thread 0x7f304cb12760 (LWP 6503)]
> (no debugging symbols found)
> (no debugging symbols found)
>
> It seems that gil.py will work one time and then stops working until
> you reloading the WSGI script
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to modwsgi@googlegroups.com
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