March 18, 2013, I updated my Go app with "appcfg.py update ." successfully. I verified it by going to *new_app_id.appspot.com*, made this new version the default and verified again that the new version is being served at * www.example.com*.
Later, a new instance was created automatically: 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. But failed right there with: Request failed because the app binary was missing. This can generally be fixed by redeploying your app. Is it expected behavior that new instances can fail with that error once the update was deployed successfully? I had this error a couple of times, but always only right after deploying an update. That wasn't problematic since I test updates before I make them the default version. The error above appeared half an hour after I deployed the update successfully. The working instances were shut down automatically and the failing one remained active. The instance that failed: 00c61b117c4bbad42f816ff10d6c52fee2ec50<https://appengine.google.com/instances?app_id=s~panoptikos3&version_id=2013-03-18-1.366050327424802611&key=00c61b117c4bbad42f816ff10d6c52fee2ec50#00c61b117c4bbad42f816ff10d6c52fee2ec50> Timestamp: 18/Mar/2013:15:34:17 -0700 -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-appengine?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
