App engine logs shows a bunch of warning "Exit 1 app"

[Duandz]

Hi, I'm hosting my Nodejs app on the GCloud App engine. It uses nodejs16 and a vpc_access_connector to connect with Redis.

The app works fine but the logs show many warning logs with a similar message: "[pid1-app] Exit 1 app (pid 11): /serve [session:*******]". The frequency is likely 500 warning/day. What is the meaning of these logs? What should I do to resolve them? 

Thanks in advance!

[anjelisa]

Hi @Duandz,

Welcome to Google Cloud Community!

I'd recommend checking your application logs, error and exception messages to check if there are any issues that could be causing these warnings.

You can also contact the Google Cloud Support team for assistance so they can look into your project and determine the cause of these warning messages.

[Duandz]

Hi @anjelisa ,

Thank you for your reply.

I did check the Logs Explorer and there are no error logs. The warning comes along with these info logs:

[pid1] Sending terminated signal to processes [session:V13923N]
[pid1] Waiting 2s to allow shutdown processing [session:V13923N]
[pid1-app] Propagating terminated signal to app (pid 12) [session:V13923N]
[pid1-nginx] Propagating terminated signal to nginx (pid 35) [session:V13923N]
[pid1-nginx] Exit 0 nginx (pid 35): /usr/sbin/nginx -c /tmp/nginxconf-4225687266/nginx.conf [session:V13923N]
[pid1-app] Exit 1 app (pid 12): /serve [session:V13923N]

Honestly, I can't afford the Google Cloud support because the price is too much for me. I think that these messages are produced by GCloud's internal services so GCloud should provide enough documents for us to debug. But seem like I can not find any document relate to it

[wpe_gtipley]

I'm getting the same thing on a long-running report that runs in GAE. Somebody devised a "stay alive" function but it doesn't work for me https://stackoverflow.com/questions/62713011/long-running-app-engine-script-quitting-on-terminated-s...

[Rahn]

I've had this app running smooth for a whole year, but since Monday, it's been acting up with this error

[wpe_gtipley]

I was eventually able to get this to work with a keep alive function.