After health checks are disabled, /_ah/vm_health path is created for backend health checks. As far as I know, it should return 200. Issues such as these most of the times tend to be project/application specific. I would recommend to post on App Engine public issue tracker <https://issuetracker.google.com/issues/new?component=187191&template=0>so we can take a look at this at project level.
On Friday, September 1, 2017 at 11:48:09 AM UTC-4, Marco Galassi wrote: > > Hi everyone! > > Apparently we are experiences issue with the Health Checking system of App > Engine. > We have disabled the regular health check mechanism as explained in this doc > page > <https://cloud.google.com/appengine/docs/flexible/python/configuring-your-app-with-app-yaml#health_checks>. > And, > in fact, we do not receive any logs of requests pointing to */_ah/health*. > > But if we filter by *nginx.health_check* logs we see logs for health > check requests to */_ah/vm_health*. > > First of all, we do not know what this is exactly. > Second, we see a long sequence of requests to */_ah/vm_health* that are > answered *200* and then suddenly it become *503*. And after some of them, > like 15ish requets > that answered *503*, the server reboots. > > What could be the causes of this? Where can I point my eye to search for > answers and possibly solutions? > > Any help is very appreciated. > > Thank you very much > -- 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 google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. 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/948453cf-06db-485b-99ef-003778ed00ab%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
