Datastore on flex nodejs appengine isn't working

[Tony Stark]

Since yesterday does not work datastore through the flex evironment. Application just not receives the response from the datastore. If I run the application locally, everything works. If I try to do those operations in app engine - it does not work. The answer does not come from the server. If wait a long time, the message from the nginx is  "502 Bad Gateway".

There are no errors in the app; it works locally. And even before yesterday everything worked perfectly in the app engine.

https://lynkus-api-test.appspot.com/test - here is no request to the datastore, the answer comes from the application.
https://lynkus-api-test.appspot.com - here is a request, but there is no answer :(

if you go in the app engine instance, in /var/log/nginx/error.log there are reports like this:

2017/02/01 09:15:59 [error] 32#32: *736 upstream prematurely closed connection while reading response header from upstream, client: 130.211.3.225, server: , request: "GET / HTTP/1.1", upstream: "http://172.18.0.2:80/", host: "lynkus-api-test.appspot.com"

[Nicholas (Google Cloud Support)]

While this is important, I would recommend filing an issue on the App Engine public issue tracker as that seems like a more appropriate forum for such a report.  This discussion group is generally better suited for exchanging best practices and general guidance.

I'd suggest including or doing the following:

• Sample code of exactly what Nodejs code is running for each handler (/ and /test).  This will allow us to test this for ourselves.
  
• Are you using the nodejs runtime or a custom runtime with a Dockerfile importing a Node.js base image?
  
• In the flexible environment, the nginx process sits in front or your Nodejs application container proxying requests and responses to/from the user.  For the nginx process to serve 502 BAD GATEWAY to the user does not indicate much that's conclusive.  It may simply timeout while waiting for the application container and serve the user a 502.
  
• To be sure what might be going on, I'd suggest logging in you /test handler before and after each Datastore-related function to determine exactly where the application is hanging.  As there is currently no known outage for Cloud Datastore, it seems more likely that the application is hanging during some request to the Cloud Datastore than the instance not being able to communicate with it.
  

Once you've tested the above and included it in the public issue you filed, post a link to said issue here so that others in the community can follow through should they be experiencing the same issue.

Regards,

Nicholas

[ad...@novelty.media]

Hi Tony

I have the same issue, did you find a way to solve it?