I recently went to my App Engine site, which worked fine, and received no errors and got a large ugly error page. This error was logged in the App Engine admin application:
2012-09-06 10:53:43.938 Traceback (most recent call last): File "/base/python27_runtime/python27_lib/versions/1/google/appengine/runtime/wsgi.py", line 189, in Handle handler = _config_handle.add_wsgi_middleware(self._LoadHandler()) File "/base/python27_runtime/python27_lib/versions/1/google/appengine/runtime/wsgi.py", line 227, in _LoadHandler handler = __import__(path[0]) File "/base/data/home/apps/s~myapp/1.361555922666090832/main.py", line 3, in <module> from controllers.routes import api_routes, web_routes, admin_routes File "/base/data/home/apps/s~myapp/1.361555922666090832/controllers/routes/api_routes.py", line 3, in <module> from ..api import api_obj_controller, api_app_controller, api_path_controller, api_user_controller File "/base/data/home/apps/s~myapp/1.361555922666090832/controllers/api/api_obj_controller.py", line 2, in <module> from ..handlers.api_handler import ApiRequestHandler File "/base/data/home/apps/s~myapp/1.361555922666090832/controllers/handlers/api_handler.py", line 2, in <module> from ..handlers.content_handler import BaseRequestHandler File "/base/data/home/apps/s~myapp/1.361555922666090832/controllers/handlers/content_handler.py", line 3, in <module> from webapp2_extras import jinja2 File "/base/data/home/apps/s~myapp/1.361555922666090832/webapp2_extras/jinja2.py", line 15, in <module> import jinja2 File "/base/python27_runtime/python27_lib/versions/third_party/jinja2-2.6/jinja2/__init__.py", line 33, in <module> from jinja2.environment import Environment, Template File "/base/python27_runtime/python27_lib/versions/third_party/jinja2-2.6/jinja2/environment.py", line 13, in <module> from jinja2 import nodes ImportError: cannot import name nodes W 2012-09-06 10:53:43.967 After handling this request, the process that handled this request was found to have handled too many sequential errors, and was terminated. 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 are likely returning errors continously from your application.
Therefore, he continued to receive many errors, but then again began to work without publishing new code. My problems, obviously, are how I can prevent this from happening again. Why did this happen? And how is it possible, he corrected himself without me, deploying any code fixes? This mistake makes me nervous that this will happen to my clients by accident.
Edit:
In addition, the very first error I received was a DeadlineExceededError error, which includes the message “This request started a new process for your application and thus caused the loading of your application code for the first time. It may take more time and use more CPU than a typical request for your application. "
So, from this post, and what Tim commented on makes full sense, but how to fix it so that it does not happen again? What can I do to ensure that DeadlineExceededError does not basically throw an entire site error until a new instance is deployed? (that is, if I understand correctly)