Hey Deepak,

My apologies as we seem to have missed this post.  Nevertheless, if you 
believe some behavior to be an error with the platform, the best place to 
report it for App Engine is the App Engine public issue tracker 
<https://code.google.com/p/googleappengine/issues/list>.  In doing so, you 
can submit screenshot, logs, reproductions, etc. with privacy so that we 
can help identify the root cause and improve the platform accordingly 
should the source prove to be platform-related.

In the issue report, please include the following:

   - *Runtime used* (runtime: custom, vm: true or env: flex).  These 
   factors affect the serving infrastructure in the backend and knowing this 
   greatly helps us narrow down a possible point of error.
   - *Specific time frames*.  Having specific timestamps of the first 
   recorded occurrence and last recorded occurrence of a given error is very 
   helpful.  Knowing this range can help us correlate your report with issues 
   we might have filed internally accelerating our investigation.
   - *SDK versions*.  Knowing the code base can greatly trim down the 
   research required to know where an error might be occurring if it is in 
   fact with the platform.
   - *Relevant logs*.  *502*s are most often served by a nginx process in 
   each VM instance that sits in front of your application container.  It has 
   many uses including serving static resources according to handler rules 
   defined in your app.yaml and serving *502*s when the application 
   container is unresponsive or otherwise crashes.  Good places to look for 
   your logs:
   - *Application logs*. If your application encounters errors on specific 
      lines of code, it may still be logging other statements effectively so 
this 
      can help determine where in your handler code the error occurs
      - *stdout*, *stderr*.  If the runtime in the application container 
      encounters errors, they may be found here.  Accessing locked down 
libraries 
      for instance or attempting to write to a file-system withour write 
ability 
      may generate errors visible here.
      - *nginx.** logs.  If the application container is entirely 
      unresponsive (which could happen if busy, crashed, out of memory, etc.), 
      nginx should still get the requests and generate appropriate logs.  These 
      log entries may indicate what the nginx process sent to the application 
      container and what it received (or likely failed to receive)
      - *Cloud HTTP Load Balancer request logs*.  If the entire instance is 
      unreponsive including its nginx process, the load balancer may respond 
with 
      failure codes to ensure client requests don't hang forever.  This may 
      happen if the application occupies all of the VM's resources like CPU or 
      memory
   
I hope the above information is helpful to you and others in the community 
attempting to troubleshoot *502-3* errors.  After reporting a new issue on 
the tracker, feel free to post a link to it here so that others can follow 
through.

Regards,
Nicholas

On Monday, February 13, 2017 at 10:13:41 AM UTC-5, Deepak Singh wrote:
>
> I went out of app engine and now running better with Amazon.
> 502/503 errors are not guaranteed and even gae team dont accept it until 
> they reproduce it. 
>
> On Mon, Feb 13, 2017 at 7:36 PM, Attila-Mihaly Balazs <[email protected]> 
> wrote:
>
>> AFAIK "vm: true" has been deprecated and you now need to use "env: flex".
>>
>> Attila
>>
>> -- 
>> 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/ac54f425-b678-4e13-a206-7dcb1199af74%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/google-appengine/ac54f425-b678-4e13-a206-7dcb1199af74%40googlegroups.com?utm_medium=email&utm_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Deepak Singh
>

-- 
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/25c0fff9-5b4c-46c8-9aa8-9d9a2316515f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to