This is happening again.  I even made my application a paid
application this morning.  Everything was working fine and then around
8 am PST everything starting blowing up again.

Maybe it has something to with using django 1.0 with use_library
('django', '1.0')?

Please help.

I'm seeing this on the client side:

Error: Server Error
The server encountered an error and could not complete your request.
If the problem persists, please report your problem and mention this
error message and the query that caused it.

And this in the logs:

#

   1.
      09-03 08:38AM 01.904 /class/list 500 36197ms 1185cpu_ms
38api_cpu_ms 0kb Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1;
Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR
3.0.30729; Media Center PC 6.0; Tablet PC 2.0),gzip(gfe)
      See details

      - - [03/Sep/2009:08:38:38 -0700] "GET /class/list HTTP/1.1" 500
0 "http://easyschooladmin.appspot.com/class/list"; "Mozilla/4.0
(compatible; MSIE 8.0; Windows NT 6.1; Trident/4.0; SLCC2; .NET CLR
2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC
6.0; Tablet PC 2.0),gzip(gfe)" "easyschooladmin.appspot.com"

   2.
      E 09-03 08:38AM 38.069

      <class 'google.appengine.runtime.DeadlineExceededError'>:
      Traceback (most recent call last):
        File "/base/data/home/apps/easyschooladmin/
1.336079106509095336/django_bootstrap.py", line 64, in <module>
          main()
        File "/base/data/home/apps/easyschooladmin/
1.336079106509095336/django_bootstrap.py", line 61, in main
          util.run_wsgi_app(application)
        File "/base/python_lib/versions/1/google/appengine/ext/webapp/
util.py", line 76, in run_wsgi_app
          result = application(env, _start_response)
        File "/base/python_lib/versions/third_party/django-1.0/django/
core/handlers/wsgi.py", line 239, in __call__
          response = self.get_response(request)
        File "/base/python_lib/versions/third_party/django-1.0/django/
core/handlers/base.py", line 128, in get_response
          return self.handle_uncaught_exception(request, resolver,
exc_info)
        File "/base/python_lib/versions/third_party/django-1.0/django/
core/handlers/base.py", line 141, in handle_uncaught_exception
          from django.core.mail import mail_admins
        File "/base/python_lib/versions/third_party/django-1.0/django/
core/mail.py", line 5, in <module>
          import mimetypes



On Sep 2, 9:32 pm, Kenneth <[email protected]> wrote:
> Actually I did have two versions of my application.  Both of them went
> down, including the production version that hadn't been updated in
> nearly a week.  It was never a problem with my code; the problem is
> quite clearly with google's infrastructure, although I'm willing to be
> proven wrong.
>
> I uploaded my code (both production and latest) to a new application
> instance by changing the app.yaml file and it ran perfectly.  I pulled
> out all datastore touches from the code on the broken instance to see
> if that was the issue, it wasn't.
>
> If you look at the stack traces they appear to be happening during
> module import, not during my application running.
>
> I do appreciate the input though, it is good advice.
>
> On Sep 2, 8:40 pm, "Brandon N. Wirtz" <[email protected]> wrote:
>
> > > Google, how am I supposed to run a business on this platform?
>
> > That is why there is versioning.  Upload to one version, test that it works,
> > push the button to change the default version.  
>
> > Always have two copies of your application, so you don't risk corrupting
> > your live data.  
>
> > Make sure you only have one guy with the rights to deploy to your primary
> > app so that a momentary lapse in Yaml configuration doesn't bork your site.
>
> > "With Great power comes great responsibility"  :-)  so make sure that when
> > leveraging the Power of the Goog, you don't break the baby, cause it can be
> > a real pain if your have 100 megs of application and screw it up, cause it's
> > kind of slow to put back.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" 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/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to