Error code 121

[Rik]

Getting a lot of 500s with this error:

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)

Anyone else?

[Kenny]

Yeah, I've been getting a lot of these as well.

[Albert]

Me too. Same errors.

[Al Murauski]

Me also. Getting error 121 for 12 hours. The app not working. All the calls return 500 server error.

[Al Murauski]

As for now it's ok.

[Christopher Ritter]

Same problem for us on one of our applications.

- Chris

[Rik]

I haven't seen one for over 24 hours at this point.

[Christopher Ritter]

We've been down for the last few hours (app id: gfmcommonview).

The lack of any official Google response is frustrating.

We're a long time customer of GAE with many apps deployed but these errors and the non-existent responses from Google when problems like this occur make me start to question the future of the platform.

[Christopher Ritter]

After some hacking...

Backends work like normal always.

A trick to resolve frontend instances is temporarily to set the number of resident instances to a static number like

Idle Instances: ( 3 – 3 )

This seems to fix the issue (essentially disabling the scheduler) but is undesirable for many reasons. I'd love to hear Google's opinion on the matter.

[Christopher Ritter]

We're still getting the error and it's been 24 hours... no response from anyone Google!

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)

[sco...@referabuyer.com]

We were getting a lot of these errors and eventually noticed that they were all happening on a particular instance(instance #19 for us).  By deleting the backend that the errors were occurring on and then bringing it back up the issue was put to rest.  

[Francois Masurel]

Same here four several java apps: prncts2 (a few hours ago) and bblcts2 recently.

Hey Google, what's going on?  Preparing the next update?

[Michael Collins]

I have been working on an app for the last 5 days, all was fine until this morning.  Since then I'm getting nothing but "Error code 121" for requests

coming from my Android devices.  Web pages are being served properly.  Tried rolling back to a previous working version of the device and server

code, same problem.  Tried building and deploying the pure Android/AppEngine app, same error.

Killed the GAE instances, cranked the GAE version, nothing helps.

What can I do to help you figure out if it's my problem or your problem?  Below is from the pure Google sample code.

1. 2013-12-11 14:08:14.625 /_ah/spi/com.ebay.mike.test.DeviceInfoEndpoint.getDeviceInfo 500 2057ms 0kb Google-HTTP-Java-Client/1.16.0-rc (gzip) module=default version=2

   216.113.168.148 - - [11/Dec/2013:14:08:14 -0800] "POST /_ah/spi/com.ebay.mike.test.DeviceInfoEndpoint.getDeviceInfo HTTP/1.1" 500 0 - "Google-HTTP-Java-Client/1.16.0-rc (gzip)" "blue2smog.appspot.com" ms=2057 cpu_ms=1082 loading_request=1 exit_code=121 app_engine_release=1.8.8 instance=00c61b117c6ea0963d970075075c6b13db57d7

2. I2013-12-11 14:08:14.573

   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.

3. W2013-12-11 14:08:14.573

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

[Francois Masurel]

Hi Michael,

I have exactly the same problem with one of my Java app at the moment (bblcts2).

I had the same problem yesterday on another app and it lasted for more than 2 hours.  It's now fixed.

François

[Michael Collins]

I did just start getting a stack trace with the error 121, that should help, if somebody fixed something thanks...

[Michael Collins]

Spoke too soon.  The stack trace was from a misguided attempt to correct a benign warning.
Still getting error 121 with no stack trace. 

[Michael Collins]

And now this morning all is back to normal...gack

[Francois Masurel]

Same here, everything is back to normal.

[Mohammed Sameer]

My app (kudufinance) is down for about 12 hours now