For advice on troubleshooting, I would suggest posting to a new thread as the original underlying issue for this thread may not be related to issues you may be having. In general, *500*s and *502*s are very generic error messages. When using the flexible environment, your application is built into docker image using a preset Dockerfile <https://cloud.google.com/appengine/docs/flexible/custom-runtimes/build#configuring_the_dockerfile> and then deployed to App Engine with an added docker entrypoint so the application container can be run. If using a custom runtime, the image is built using your own custom Dockerfile. In front of your resulting application container sits a separate container with an nginx process for serving static content and observing the handlers specified in your app.yaml.
- When posting to a new thread, I recommend the following: - Where are you testing? Is this your App Engine application in production or in development? - Are you using the flexible environment or standard environment? - If using the flexible environment, are you using an App Engine-provided runtime or a custom runtime? (This and the previous question help us identify where the issue may be originating and how you can investigate the source for yourself) - Is the error served from every handler or only a specific subset? - If you only get errors with a subset of handlers, are those static assets or handlers served by your application? - Is your application successful in responding to requests for a given handler? The above are good starting points for investigating *500*s served from your application. When posting new threads about such errors, please try to include as much of this information as possible so that others in the community can have a better defined picture of your the architecture at play and know what you've already looked at. Should you decide to post a new thread, feel free to include a link to it here so that others in the community can follow through. On Wednesday, November 23, 2016 at 1:04:04 PM UTC-5, Jeff Payne wrote: > > I had this same problem using a memory intensive Flask based flex env app. > I finally investigated this locally at the system level and realized that > a function, which I had not yet thought to optimize, was loading a huge > file (500+ Gb) into memory. I couldn't find anything in the logs to > support this (I probably wasn't looking in the right logs), but I figured > that the process/thread handling the request was choking behind the scenes. > > My solution was: > > 1) Move the code that loaded the file into memory outside of the function > so it was only loaded once, as the resulting object is thread safe. > 2) Increase the memory of the VM used by the flex env. app using the > resource settings explained here: > https://cloud.google.com/appengine/docs/flexible/python/configuring-your-app-with-app-yaml#resource-settings > > Hope that helps! > > On Monday, November 7, 2016 at 12:58:34 PM UTC-8, Suresh V wrote: >> >> >> >> Any update on this? My instance, https://vplan-147418.appspot.com is >> doing this since last night. >>> >>> >> Any tips to troubleshoot? This also uses the flexible environment, >> > -- 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 https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/fa59c718-2815-4597-9032-45bdc136f48f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
