为什么我的Google AppEngine实例会因'错误代码121'而崩溃? [英] Why are my Google AppEngine instances crashing with 'error code 121'?

查看:113
本文介绍了为什么我的Google AppEngine实例会因'错误代码121'而崩溃?的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我一直在Google AppEngine上运行一个java高级复制web应用程序。大约两天前 - 基本上没有任何地方 - 很多请求开始以 HTTP状态500 错误代码121 失败,这意味着相应的GAE实例崩溃或关闭



以下是一个示例性日志条目,我现在有很多:

  2013-02-15 06:44:00.909 / api 500 3770ms 0kb Mozilla / 5.0(Macintosh;英特尔Mac OS X 10_7_5)AppleWebKit / 537.17(KHTML,如Gecko)Chrome / 24.0.1312.57 Safari / 537.17 
###。###。###。### - - [14 / Feb / 2013:22:44:00 -0800]POST / api HTTP / 1.1500 0 - Mozilla / 5.0 (Macintosh; Intel Mac OS X 10_7_5)AppleWebKit / 537.17(KHTML,如Gecko)Chrome / 24.0.1312.57 Safari / 537.17###。########。###ms = 3770 cpu_ms = 1191 exit_code = 121 instance = 00c61b117c2c2b8fd8c433bc45a62183829f6484

W 2013-02-15 06:44:00.652
处理此请求的进程遇到问题,导致它退出。这很可能会导致下一个请求应用程序使用新的进程。 (错误代码121)

错误有时会发生在热身请求内,实例收到其第一个请求。关联的日志条目如下所示:

  2013-02-15 06:40:02.779 / _ah / warmup 500 2970ms 0kb 
0.1.0.3 - - [14 / Feb / 2013:22:40:02 -0800]GET / _ah / warmup HTTP / 1.1500 0 - - 2013-02-14-1438.flox-by- gamua.appspot.comms = 2971 cpu_ms = 671 loading_request = 1 exit_code = 121 instance = 00c61b117c48cb17ea555d1988c0db473c2390

I 2013-02-15 06:40:02.437
此请求导致了一个新进程为您的应用程序启动,并因此导致您的应用程序代码第一次加载。因此这个请求可能需要更长的时间,并且比使用应用程序的典型请求使用更多的CPU
W 2013-02-15 06:40:02.437
处理此请求的进程遇到问题,导致它退出。这很可能会导致下一个请求应用程序使用新的进程。 (错误代码121)

我一直在网上寻找这个问题, : http://code.google.com/p/googleappengine/issues/由于所有相关问题都被标记为已解决,因此我在此处提交了一个新的GAE生产问题: href =http://code.google.com/p/googleappengine/issues/detail?id=8812 =noreferrer> http://code.google.com/p/googleappengine/issues/detail?id = 8812



修改2013-04-29:以上链接无效,因为此问题已被标记为'限制'GAE团队。



不幸的是,我现在已经有两天没有注意到我的呼救声。这就是为什么我在绝望中寻求你的帮助! : - )



有谁知道是什么导致错误代码121?是否有某种形式的文件?我的应用有问题吗?有没有办法让AppEngine团队了解这个问题?



Thanksalot!

解决方案

检查您的日志保留限制,并且您没有超过它们。你不会期望绕过你的日志保留限制会导致一个异常,导致实例失败,但我增加了我的后,我不再看到这个错误突然出现,我的后端cron作业能够完成。

I have been running a java high-replication web application on Google AppEngine for some time now. About two days ago - basically out of nowhere - a lot of requests began to fail with HTTP status 500 and error code 121, meaning that the respective GAE instance crashes or is shut down.

Here is an exemplary log entry, which I now have tons of:

2013-02-15 06:44:00.909 /api 500 3770ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17
###.###.###.### - - [14/Feb/2013:22:44:00 -0800] "POST /api HTTP/1.1" 500 0 - "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.17 (KHTML, like Gecko) Chrome/24.0.1312.57 Safari/537.17" "###.########.###" ms=3770 cpu_ms=1191 exit_code=121 instance=00c61b117c2c2b8fd8c433bc45a62183829f6484

W 2013-02-15 06:44:00.652
    A 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. (Error code 121)

The error sometimes occurs right within a 'warmup' request, thus when a new instance receives its first request. An associated log entry looks like this:

2013-02-15 06:40:02.779 /_ah/warmup 500 2970ms 0kb
0.1.0.3 - - [14/Feb/2013:22:40:02 -0800] "GET /_ah/warmup HTTP/1.1" 500 0 - - "2013-02-14-1438.flox-by-gamua.appspot.com" ms=2971 cpu_ms=671 loading_request=1 exit_code=121 instance=00c61b117c48cb17ea555d1988c0db473c2390

I 2013-02-15 06:40:02.437
    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.
W 2013-02-15 06:40:02.437
    A 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. (Error code 121)

I have been searching the web for this problem and it looks like it happened before: http://code.google.com/p/googleappengine/issues/detail?id=7348.

Since all relevant issues have been marked as 'resolved', I did file a new GAE production issue over here: http://code.google.com/p/googleappengine/issues/detail?id=8812

Edit 2013-04-29: The link above does not work anymore, since this issue has been flagged as 'Restricted' by the GAE team.

Unfortunately my cries for help went unnoticed for over two days now. That's why I am, in my utter desperation, asking for your help! :-)

Does anyone know what's causing error code 121? Is there some form of documentation? Is something wrong with my app? Is there a way to nudge the AppEngine team to have a look into this issue?

Thanksalot!

解决方案

Check your log retention limits, and that you haven't exceeded them. You wouldn't expect that bypassing your log retention limits would cause an exception that caused the instance to fail, but after I increased mine, I stopped seeing this error crop up and my backend cron jobs were able to complete.

这篇关于为什么我的Google AppEngine实例会因'错误代码121'而崩溃?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆