[google-appengine] Re: Missing logs (for 12 hours) on Node.js Google App Engine Flexible Environment

October 11, 2017 at 4:00:19 AM UTC-4, Marco Galassi wrote: >> >> Hi Yannick, >> >> I think you gave me the wrong link because it bring me to "MOMA inside >> Google" that looks like something for Google Employees >> >> Marco >> >> >&g

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Hi Jordan, thank you for your detailed response. Node.js is a single threaded runtime, this means that your code must be properly > coded to take full advantage of Node.js's event loop > in > order to be asynchronous. >

[google-appengine] Re: Missing logs (for 12 hours) on Node.js Google App Engine Flexible Environment

the affected time frame (with time zone). > > On Tuesday, October 10, 2017 at 3:47:21 AM UTC-4, Marco Galassi wrote: >> >> We have noticed that a couple of days ago we have no logs for more than >> 12 hours. >> The only logs we see in those 12 hours are *vm.events*

[google-appengine] Missing logs (for 12 hours) on Node.js Google App Engine Flexible Environment

We have noticed that a couple of days ago we have no logs for more than 12 hours. The only logs we see in those 12 hours are *vm.events* that look something like this: *00:55:01.649Health checks: instance=aef-[our-service]--v3-rf5g start=2017-09-29T22:52:00+00:00 end=2017-09-29T22:52:59+00:00

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Hello Jordan, we are back because we have found the problem again. We have deleted the custom health check handler, disabled the health check in the *app.yaml* configuration file, but the problem is still there. Just to recap, what we keep seeing is the following. - From the proxy

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Hi Jordan, we would like to share with you what we have found. We have delete our custom health check that was an handler responding with 200 OK as follows: app.get('/_ah/health', function (req, res) { res.sendStatus(200); }); It looks like this has solved the problem as we *do not* see any

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

So, we took a step back in our project and deployed an Hello World application to see if the problem would still happen. We used the hello-world example in the Google App Engine code examples and edited it (our file is attached): there are no differences, but the fact that we don't have a

[google-appengine] Re: Google App Engine, Nodejs, 502 Bad Gateway

Attaching a graphic description or current backend. On Monday, September 25, 2017 at 10:00:13 AM UTC+2, Marco Galassi wrote: > > We are performing a migration to a new backend hosted on Google App Engine > and based on Node.js. > > Before performing the switch from the old to

[google-appengine] Google App Engine, Nodejs, 502 Bad Gateway

We are performing a migration to a new backend hosted on Google App Engine and based on Node.js. Before performing the switch from the old to the new backend, we need to do tests and see if packets that the legacy server receives are correctly processed by the new backend. So, on the old

[google-appengine] Health Checking Issues and Confusion

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 . And,

[google-appengine] Re: Too many GoogleHC/1.0 /_ah/vm_health entries in the log

Any update on this? I also get tons of */_ah/vm_health* entries. I have disabled other health checks to */_ah/health (notice it is NOT vm_health)* as suggested in the docs , but I still get those. On

[google-appengine] Re: Google App Engine NodeJS log severity

erenced to update winston-gae, or implement a > different solution). > > On Monday, April 3, 2017 at 3:00:19 AM UTC-4, Marco Galassi wrote: >> >> Yes, but that basically is just the same as doing >> console.log('stdout'); >> console.error('stderr'); >> >>

[google-appengine] Re: Google App Engine NodeJS log severity

use to implement your own logger or use directly in > your code (or which can be referenced to update winston-gae, or implement a > different solution). > > On Monday, April 3, 2017 at 3:00:19 AM UTC-4, Marco Galassi wrote: >> >> Yes, but that basically is just the same as do

[google-appengine] Re: Google App Engine NodeJS log severity

but only outputs to stdout and as such you don't get proper severity > in the Logs Viewer. > > On Friday, March 31, 2017 at 11:03:20 AM UTC-4, Marco Galassi wrote: >> >> >> I am using nodejs on App Engine and I would like to have the ability to >> log my application in

[google-appengine] Google App Engine NodeJS log severity

I am using nodejs on App Engine and I would like to have the ability to log my application in an easy manner. Possibily, I would like to be able to log as easy as in python standard environment : import logging > import webapp2 >

[google-appengine] Re: Please give me my quick links back!

You can still pin down the links, they will just show in the left pane. On Wednesday, March 29, 2017 at 11:03:47 AM UTC+2, Gwyn Howell wrote: > > The cloud

[google-appengine] where do I find the build logs?

I am not able to deploy for some error. At the end of the deployment process i get: ERROR: (gcloud.app.deploy) Error Response: [2] Build failed; check build logs for details This is very stupid, but where do I find the build logs? -- You received this message because you are subscribed to

[google-appengine] Re: !!!URGENT!!! Billing Error in App Engine Instance Hours, charges skyrocketing

Contact the billing support here: https://support.google.com/cloud/contact/cloud_platform_billing On Wednesday, March 15, 2017 at 3:20:17 AM UTC+1, Lawrence Mok wrote: > > Since the beginning of this month, the charges for Instance Hours are > calculated wrongly. The 28 hours free quota were

[google-appengine] Re: Google App Engine went GA

ker container support. App Engine standard > environment has been GA for some time. > > Regards, > Zach > > On Friday, March 10, 2017 at 1:25:29 AM UTC-8, Marco Galassi wrote: >> >> Google App Engine went GA. >> This was announced on Google Next '17 >

[google-appengine] Google App Engine went GA

Google App Engine went GA. This was announced on Google Next '17 http://www.infoworld.com/article/3179151/application-development/google-app-engine-adds-c-nodejs-and-ruby-options.html -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To

[google-appengine] Scheduling Tasks with User params

I would like to find a way to run repeated jobs (such as cron jobs) with some parameters. For example, if I would like to have an email service that every day sends out emails to every user of the application. This could be done via cron, but I would like to add a layer of "personalization"

[google-appengine] Re: Need help: I can't shutdown app engine version. Keeps billing.

ng>. > > Best of luck! > > Nick > Cloud Platform Community Support > > On Tuesday, March 7, 2017 at 10:02:30 AM UTC-5, Marco Galassi wrote: >> >> I am not able to stop and consequently delete a app engine version. >> I have 3 different versions at the mom

[google-appengine] Need help: I can't shutdown app engine version. Keeps billing.

I am not able to stop and consequently delete a app engine version. I have 3 different versions at the moment, under the same default service: 1. gappa-v1, which is currently serving 100% of the traffic 2. mg-v1, which is currently stopped 3. 20170223t163224 I am able to stop,