Error code 202

[tarun2000]

I keep getting:  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 202)

It seems like the issue happens right after uploading a new version or on cold start.  It seems to disappear after a while.  The rpcs that fail may be returning a lot of data.  Any idea what's wrong?

[Ian Marshall]

I got this error a quarter of an hour ago. My app presented me with
the, in my view, unprofessional error 500 page (see my feature request
to change this at http://code.google.com/p/googleappengine/issues/detail?id=4674).

When a new instance of my app is created, an initialisation task is
enqueued for immediate execution. Both the original browser and the
enqueued task client web requests failed and generated the log warning
entries you describe below.

I request that the severity of this type of log entry be changed from
warning to error; it's not just a warning since a user has been unable
to access the site and got the GAE error 500 page instead.

Also, I echo Tarun's question: what is the cause of the problem? Can I
work around this?

Ian Marshall

[Tom Carchrae]

I'm getting these 202 errors also. It's driving me nuts. Most of the
requests are relatively benign looking (request for a static image).

Tom

[Amy Unruh]

For those of you seeing these errors, could you indicate whether you're using python or java, and whether you're using M/S or HRD?  It would also be helpful to get your app ids, if you're willing to share them (you can email me directly if you like).

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

[Amy Unruh]

On Thu, Mar 8, 2012 at 8:40 AM, Amy Unruh <amyu+...@google.com> wrote:

For those of you seeing these errors, could you indicate whether you're using python or java, and whether you're using M/S or HRD?  It would also be helpful to get your app ids, if you're willing to share them (you can email me directly if you like).

Thanks to those who sent me more info.  An internal issue has been filed, and it's being looked into.  

[Ian Marshall]

That's good to hear; I just had the error again when visiting my app's
home page to get you the app ID.

As well as the app ID, I sent to Amy: "I am using the Java version of
GAE, with the HRD."


On Mar 8, 5:51 pm, Amy Unruh <amyu+gro...@google.com> wrote:

[Raphael André Bauer]

On Thu, Mar 8, 2012 at 7:00 PM, Ian Marshall <ianmars...@gmail.com> wrote:
> That's good to hear; I just had the error again when visiting my app's
> home page to get you the app ID.
>
> As well as the app ID, I sent to Amy: "I am using the Java version of
> GAE, with the HRD."

Same here... the error went away for one hour and now the app does not
load any more again... I hope the team can sort this out quickly... I
would also be interested in a post-mortem describing the issue...

Best,

Raphael

[Thomas]

Same here: during the last days we've been getting lots of error logs like these: 

Request was aborted after waiting too long to attempt to service your request.

or

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 204)

Most of these requests take several minutes until they die, which is a disaster when it comes to user experience :-(

Please Google, do something about this! Our users are paying for the service, we want to serve their expectations!

[Nikolai]

+1 

same here

[Ronoaldo José de Lana Pereira]

Same here, my apps is Java, concurrent requests enabled, on MS (sadly ...)

[Takashi Matsuo ♟]

Sorry to chiming in a bit late here.
If anyone is still suffering from (Error code 202), please let me know
your app-ids and the time of the occurrence.

I'll try my best to solve the issue.

-- Takashi

> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.

> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine/-/vCTQyKvK20gJ.

>
> To post to this group, send email to google-a...@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.

--
Takashi Matsuo | Developer Advocate | tma...@google.com | 03-6384-9224

[Ikai Lan (Google)]

I've taken a look at some of the High Replication app IDs posted publicly and haven't found instances of this (instances exiting because of error code 202) recently. It looks to have stabilized as of ~15 hours ago. If you have a master/slave application that continues to exhibit this behavior, there might be a band aid we can apply, but please don't ask for it unless you are still seeing issues since there could be unintended consequences.

Side note: there are a few things going on at the same time, so if you are NOT seeing the symptoms reported in this thread (Error Code 202 exits), please don't post to this thread - you're just making it harder to collect information and address the issue.

--

Ikai Lan 
Developer Programs Engineer, Google App Engine

plus.ikailan.com

[tarun2000]

My issue is still not resolved. I am now getting a 203 instead of a
202 during what appears to be a cold start. The logs indicate that
the gwt rpcs timeout. When I refresh, everything seems to work until
an instance is brought up again.

2012-03-10 00:59:38.235 *********** 500 89571ms 0kb Mozilla/5.0 (X11;
Linux i686) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.78
Safari/535.11
128.12.114.16 - tarun [10/Mar/2012:00:59:38 -0800] "POST **********
HTTP/1.1" 500 106 "http://taruntest.webaleppo.appspot.com/" "Mozilla/
5.0 (X11; Linux i686) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/
17.0.963.78 Safari/535.11" "taruntest.webaleppo.appspot.com" ms=89572
cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000204 exit_code=203
instance=00c61b117c8629aa9ec396298c1de07ab8e3
I 2012-03-10 00:59:38.234
The process handling this request unexpectedly died. This is likely to

cause a new process to be used for the next request to your

application. (Error code 203)

I am running HRD, but the error occurs even when there is no datastore
access in the call. The commonality in the failures seems to be use
of gwt rpc. For google engineers with access to my logs, the entries
can be found by filtering for device-.

On Mar 9, 3:04 pm, "Ikai Lan (Google)" <ika...@google.com> wrote:
> I've taken a look at some of the High Replication app IDs posted publicly
> and haven't found instances of this (instances exiting because of error
> code 202) recently. It looks to have stabilized as of ~15 hours ago. If you
> have a master/slave application that continues to exhibit this behavior,
> there might be a band aid we can apply, but please don't ask for it unless
> you are still seeing issues since there could be unintended consequences.
>
> Side note: there are a few things going on at the same time, so if you are
> NOT seeing the symptoms reported in this thread (Error Code 202 exits),
> please don't post to this thread - you're just making it harder to collect
> information and address the issue.
>
> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>

> > Takashi Matsuo | Developer Advocate | tmat...@google.com | 03-6384-9224

[Tom Carchrae]

I can also confirm the appearance of 203 errors again - which I had
seen lots of earlier this week.

Tom

[Kyle Baley]

We've been getting these errors since Feb. 13. We did a deployment on that day and I've been tracing through the code trying to see if there's something in there that would cause this to no avail.

Our app is technically HR but we don't have any data in it. The app makes API calls to another AppEngine app mostly via URLFetch. 

That said, the errors occur almost exclusively on static files. Here's a sample:

• 1. 2012-03-10 11:42:06.052 /images/separator2.gif 500 124544ms 0kb Mozilla/5.0 (X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.60 Safari/535.11

     166.248.1.87 - - [10/Mar/2012:08:42:06 -0800] "GET /images/separator2.gif HTTP/1.1" 500 0 "http://www.bookedin.net/multimedia-solutions-llc" "Mozilla/5.0 (X11; CrOS i686 1412.205.0) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.60 Safari/535.11" "www.bookedin.net" ms=124544 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000058 exit_code=202 instance=

  2. W 2012-03-10 11:42:06.051

• 1. 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 202)

A request to that same image two minutes earlier (on the same instance) returned a 200. AppEngine ID is gunton-prod.

We're using Java. All requests are filtered through a servlet module via Guice but we let requests for static files pass through. Nothing in our configuration changed in the deployment we did. We're getting the problem daily though intermittently. 25 - 30 failures today out of over 1000 requests for these images. 

The other AppEngine app we have is also HR and Java. It's by far the more heavily used one. Haven't seen any issues with it.

Happy to provide more details if you want to contact me.

[Mauricio Aristizabal]

I'm getting 203s as well still, and what I'm seeing might be insightful to the G team.  Below are log entries for 3 failures.  All 3 happened in the same page load (page request itself returned fine, and all 50 or so resources loaded fine except these).  Of course, the user experience is that the whole page is blank for about 5 minutes until these 3 fail and the browser finally draws whatever it can and 'finishes'.  So from the user perspective the page took 5 minutes to load (and looks funny).

The interesting thing is that one request was a simple png file in my resources directory, another was a .js file that is actually in a jar, and the third was an xhr call that returns json (and involves db reads).  Also.. I got other failures over an hour period, typically 1-3 resources, and not the same ones. 

-----------------------

2012-03-10 16:35:47.306 /resources/images/body-background-gradient.png 500 89603ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11

67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET /resources/images/body-background-gradient.png HTTP/1.1" 500 0 "http://www.commentous.com/f/f/month" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11" "www.commentous.com" ms=89604 cpu_ms=70316 api_cpu_ms=0 cpm_usd=1.953321 exit_code=203 instance=00c61b117ccac38353c47d5376339060aca685

I 2012-03-10 16:35:47.287

The process handling this request unexpectedly died. This is likely to cause a new process to be used for the next request to your application. (Error code 203)

2012-03-10 16:35:47.288 /users/unreadcounts 500 89154ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11

67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET /users/unreadcounts HTTP/1.1" 500 0 "http://www.commentous.com/f/f/month" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11" "www.commentous.com" ms=89154 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000102 exit_code=203 instance=00c61b117ccac38353c47d5376339060aca685

I 2012-03-10 16:35:47.286

The process handling this request unexpectedly died. This is likely to cause a new process to be used for the next request to your application. (Error code 203)

2012-03-10 16:35:47.287 /resources/dijit/form/FilteringSelect.js 500 89140ms 0kb Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11

67.49.52.74 - - [10/Mar/2012:16:35:47 -0800] "GET /resources/dijit/form/FilteringSelect.js HTTP/1.1" 500 0 "http://www.commentous.com/f/f/month" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_2) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.65 Safari/535.11" "www.commentous.com" ms=89141 cpu_ms=0 api_cpu_ms=0 cpm_usd=0.000096 pending_ms=1343 exit_code=203 instance=00c61b117ccac38353c47d5376339060aca685

I 2012-03-10 16:35:47.286

The process handling this request unexpectedly died. This is likely to cause a new process to be used for the next request to your application. (Error code 203)

-------------------------------

[Mauricio Aristizabal]

Forgot to add to last post: I'm using java, HRD, Spring for MVC, JPA.  App id is commentousprod

[Mos]

Problem still exists. (No new deployment done; running on HRD).  Just got an 202 by requesting the robots.txt:

2012-03-11 11:32:06.207 /robots.txt 500 124564ms 0kb Pixray-Seeker/1.1 (Pixray-Seeker; http://www.pixray.com/pixraybot; cra...@pixray.com)

    88.198.67.197 - - [11/Mar/2012:03:32:06 -0700] "GET /robots.txt HTTP/1.1" 500 0 - "Pixray-Seeker/1.1 (Pixray-Seeker; http://www.pixray.com/pixraybot; cra...@pixray.com)" "www.krisentalk.de" ms=124565 cpu_ms=216 api_cpu_ms=0 cpm_usd=0.006053 exit_code=202 instance=00c61b117cca039212f00b84c513a2dc01ac

    W 2012-03-11 11:32:06.206

    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 202)

[Ashley Schroder]

We're getting this 202 error code as of a few minutes ago.

appid=order-pipe

(App is Java, HRD and using Spring MVC + JDO)

Would appreciate any workaround suggestions.

Thanks,
Ashley

On Mar 11, 11:45 pm, Mos <mosa...@googlemail.com> wrote:
> Problem still exists. (No new deployment done; running on HRD).  Just got
> an 202 by requesting the robots.txt:
>
> 2012-03-11 11:32:06.207 /robots.txt 500 124564ms 0kb Pixray-Seeker/1.1

> (Pixray-Seeker;http://www.pixray.com/pixraybot;craw...@pixray.com)

>
>     88.198.67.197 - - [11/Mar/2012:03:32:06 -0700] "GET /robots.txt

> HTTP/1.1" 500 0 - "Pixray-Seeker/1.1 (Pixray-Seeker;http://www.pixray.com/pixraybot;craw...@pixray.com)" "www.krisentalk.de"

> ms=124565 cpu_ms=216 api_cpu_ms=0 cpm_usd=0.006053 exit_code=202
> instance=00c61b117cca039212f00b84c513a2dc01ac
>
>     W 2012-03-11 11:32:06.206
>
>     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 202)
>
> On Sat, Mar 10, 2012 at 12:04 AM, Ikai Lan (Google) <ika...@google.com>wrote:
>
>
>
>
>
>
>
> > I've taken a look at some of the High Replication app IDs posted publicly
> > and haven't found instances of this (instances exiting because of error
> > code 202) recently. It looks to have stabilized as of ~15 hours ago. If you
> > have a master/slave application that continues to exhibit this behavior,
> > there might be a band aid we can apply, but please don't ask for it unless
> > you are still seeing issues since there could be unintended consequences.
>
> > Side note: there are a few things going on at the same time, so if you are
> > NOT seeing the symptoms reported in this thread (Error Code 202 exits),
> > please don't post to this thread - you're just making it harder to collect
> > information and address the issue.
>
> > --
> > Ikai Lan
> > Developer Programs Engineer, Google App Engine
> > plus.ikailan.com
>

> >> Takashi Matsuo | Developer Advocate | tmat...@google.com | 03-6384-9224

[Ikai Lan (Google)]

Okay, separating two topics here:

Java HRD applications: we've been working on the issue with instance deaths. Ideally, these issues will be resolved very shortly. Thanks to everyone who provided information. I know there's been some discussion about whether or not these questions go to StackOverflow or the groups, and the answer is that you should post issues like this here in Google Groups. 

Master/slave applications (all): I just announced a maintenance period for next Monday, March 19th at 4pm-6pm US/Pacific (23:00 GMT):

https://groups.google.com/forum/?fromgroups#!topic/google-appengine-downtime-notify/2a85vnzKdn4

--

Ikai Lan 
Developer Programs Engineer, Google App Engine

plus.ikailan.com

[Ikai Lan (Google)]

Quick update: the master/slave maintenance is at 6pm, not 4pm. I posted an update about it here:

https://groups.google.com/forum/?fromgroups#!topic/google-appengine-downtime-notify/CO_x02OF9Ak

--

Ikai Lan 
Developer Programs Engineer, Google App Engine

plus.ikailan.com

[Ryan Heinen]

When will the root cause of this issue be made public?

As of the 13th the issue is now resolved, but for at least a week
prior (probably longer, but we don't have hard data) our HRD
applications was seeing approximately 10% of requests failing with
error code 202 or 204 (~50/50 split).

Ryan

On Mar 12, 5:55 pm, "Ikai Lan (Google)" <ika...@google.com> wrote:
> Quick update: the master/slave maintenance is at 6pm, not 4pm. I posted an
> update about it here:
>

> https://groups.google.com/forum/?fromgroups#!topic/google-appengine-d...

> --
> Ikai Lan
> Developer Programs Engineer, Google App Engine
> plus.ikailan.com
>
> On Mon, Mar 12, 2012 at 1:57 PM, Ikai Lan (Google) <ika...@google.com>wrote:
>
>
>
>
>
>
>
> > Okay, separating two topics here:
>
> > Java HRD applications: we've been working on the issue with instance
> > deaths. Ideally, these issues will be resolved very shortly. Thanks to
> > everyone who provided information. I know there's been some discussion
> > about whether or not these questions go to StackOverflow or the groups, and
> > the answer is that you should post issues like this here in Google Groups.
>
> > Master/slave applications (all): I just announced a maintenance period for
> > next Monday, March 19th at 4pm-6pm US/Pacific (23:00 GMT):
>

> >https://groups.google.com/forum/?fromgroups#!topic/google-appengine-d...

[Aurelian]

Same here, my apps is Java, concurrent requests enabled, on HRD. APPID riparautonline-hrd

Error:

1. 2012-12-20 14:26:01.461 /_ah/warmup 500 380ms 0kb

   0.1.0.3 - - [20/Dec/2012:05:26:01 -0800] "GET /_ah/warmup HTTP/1.1" 500 0 - - "68.riparautonline-hrd.appspot.com" ms=381 cpu_ms=0 exit_code=202 instance=00c61b117cf9d0ae4fcf1be5d94ff76d2cf9653e

2. W2012-12-20 14:26:01.460

1. 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 202)

On Monday, December 10, 2012 9:46:22 AM UTC+1, aalku wrote:

Same here

El martes, 20 de noviembre de 2012 16:26:48 UTC+1, Rodrigo Barbaresco escribió:

Hey we are getting this issue too.

It's happening right now and our app id is astrea-aurum. Can you help us?

Best,

Rodrigo.

[Fabien Lenoir]

I am also facing this issue. It happens about twice a day. Please help.

[Manish Raje]

There is an issue logged for this problem: https://code.google.com/p/googleappengine/issues/detail?id=8560

Request everyone seeing this issue to vote for the issue.

Thanks,

Manish.

[Ian Marshall]

People might also want to star Issue 7972 (Error code 202: change
logging level from Warning to Error) at:

https://code.google.com/p/googleappengine/issues/detail?id=7972&q=Error%20202&sort=priority&colspec=ID%20Type%20Component%20Status%20Stars%20Summary%20Language%20Priority%20Owner%20Log

This feature request requests that the severity of this type of log

entry be changed from
warning to error; it's not just a warning since a user has been unable

to access the web site and got the GAE error 500 page instead.

[July G]

We are experiencing the same problem with Java / HRD / app id: gaetestsrv2, it's a billing app. please help, Thank you!

[Purushotham Rvv]

Any update on this issue, we are still experiencing the same problem with Java but it is random. 

[COde]

I am experiencing this issue as well. Has this been solved?