Hey , why not remove all try-except block and set debug=False in
WSGIApplication,
Then Google will log the error for you .
On 8月31日, 下午11时42分, vp vivpu...@gmail.com wrote:
Can anyone from Google give me an update on this issue. Right now my
app is hovering at 1 Request/Second with an error
One of the new features of today's release is that if you expand the
logs for 500s in the admin console, you should see the reason.
On Sep 3, 6:00 pm, GIMME ba...@gimme.org wrote:
Hey , why not remove all try-except block and set debug=False in
WSGIApplication,
Then Google will log the error
Yes saw that. Nick had already contacted me via email about the same.
Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
Can anyone from Google give me an update on this issue. Right now my
app is hovering at 1 Request/Second with an error rate of .5 Errors/
Second. As i have mentioned earlier, 99% of these errors clearly say
...500 10096ms 0cpu_ms 0kb..., which from what i can understand
shows the request never
Right now almost 50% of pages in my app just fail to load. Here are
the stats from my app
http://tmpimages.s3.amazonaws.com/app_errors.jpg
If i click on each error link, it gives a picture similar to:
http://tmpimages.s3.amazonaws.com/request_log_1.jpg
As you can see, for reach request that
Nick, did you get a chance to look into my email? Let me know if i can
add any additional debugging somewhere...
Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group,
Hi vp,
We really need more details about your code in order to provide any useful
feedback.
Empty responses are often caused by leaving this stanza off your request
handler script:
if __name__ == __main__:
main()
-Nick Johnson
On Wed, Aug 19, 2009 at 6:23 PM, vp vivpu...@gmail.com wrote:
Nick, i sent you an email(your first_name.last_n...@google.com) with
some code. Let me know if you got it.
Thanks
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send
Since i am not able to find any real issues with my code, i want to
check with all appengine developers if their apps also throw up random
HTTP 500 - Internal Server Error. In my case this is happening mostly
where front-end template related code is involved.
To reiterate the issue, quite a few
There were loads of these yesterday during the outage.
The only times I've ever had Internal Server Errrors are:
- when GAE was having an outage
- when I had a syntax error in my code
- when I added a google apps account that matched my existing google
account
So unless you were seeing these
Joshua,
Thanks for your response. I see issues even when GAE is not reporting
an outage. In one instance, all i have setup is a redirect from one
page to another another. And quite a few times that redirect just
fails.
-V
--~--~-~--~~~---~--~~
You received this
It's been quite a few days but 500 errors still keep showing up. To
track down those errors, i have set debugging at each and every point
of my code, but none of the debug points are hit. Instead i think the
request is getting lost at the very start itself. Below is my setup
For a moment i thought this might be a DNS issue since i am on custom
domain. But since the logs show a HTTP 500, it clearly shows AppEngine
did see the request. It's just that the request gets lost from that
point on. Right now, almost 10-20 percent of all requests are ending
with HTTP 500. That
Hi, what is your app ID? I'm guessing that the 500 error is perhaps related
to a different exception, since it looks like the code that you shared
earlier will only handle a deadline exceeded error.
Cheers,
Jeff
On Fri, Aug 14, 2009 at 9:34 AM, vp vivpu...@gmail.com wrote:
For a moment i
Jeff,
Thanks for your reply. That was a good catch. I have now added the
following:
except Exception, e:
logging.critical(self.__class__.__name__+'. Error: '+str
(e))
self.redirect(/error)
return
Let's see if that catches the error
I will email you the app
15 matches
Mail list logo
