The problem seems to have gone away on its own… On Nov 22, 2011, at 2:52 PM, Joshua Smith wrote:
> We are experiencing an outage in our corporate web site, which is still > served by M/S. > > www.kaon.com (appspot id kaoncom) > > Looks like something is wrong in the infrastructure: > > 2011-11-22 19:49:20.534 / 500 95398ms 0kb Mozilla/5.0 (Macintosh; U; Intel > Mac OS X 10_6_3; en-us) AppleWebKit/531.21.11 (KHTML, like Gecko) > Version/4.0.4 Safari/531.21.10 > 75.147.50.1 - - [22/Nov/2011:11:49:20 -0800] "GET / HTTP/1.1" 500 0 - > "Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_3; en-us) > AppleWebKit/531.21.11 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10" > "www.kaon.com" ms=95399 cpu_ms=187 api_cpu_ms=0 cpm_usd=0.005245 > loading_request=1 exit_code=104 > instance=00c61b117cc34dd72b8bc34f827f4680d06c5076 > E2011-11-22 19:49:20.526 > <class 'google.appengine.runtime.DeadlineExceededError'>: > Traceback (most recent call last): > File "/base/data/home/apps/kaoncom/11.354865346370096803/main.py", line 26, > in <module> > from google.appengine.ext.webapp import template > File > "/base/python_runtime/python_lib/versions/1/google/appengine/ext/webapp/template.py", > line 68, in <module> > import django.template > File > "/base/python_runtime/python_lib/versions/third_party/django-1.2/django/template/__init__.py", > line 64, in <module> > from django.utils.formats import localize > File > "/base/python_runtime/python_lib/versions/third_party/django-1.2/django/utils/formats.py", > line 8, in <module> > from django.utils import dateformat, numberformat, datetime_safe > File > "/base/python_runtime/python_lib/versions/third_party/django-1.2/django/utils/dateformat.py", > line 17, in <module> > from django.utils.dates import MONTHS, MONTHS_3, MONTHS_AP, WEEKDAYS, > WEEKDAYS_ABBR > File > "/base/python_runtime/python_lib/versions/third_party/django-1.2/django/utils/dates.py", > line 1, in <module> > "Commonly-used date structures" > I2011-11-22 19:49:20.527 > This request caused a new process to be started for your application, and > thus caused your application code to be loaded for the first time. This > request may thus take longer and use more CPU than a typical request for your > application. > W2011-11-22 19:49:20.527 > A serious problem was encountered with the process that handled this request, > causing it to exit. This is likely to cause a new process to be used for the > next request to your application. If you see this message frequently, you may > be throwing exceptions during the initialization of your application. (Error > code 104) > > > -- > 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. -- 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.
