Background: the application worked for over a decade, no changes in code, infrastructure, or client profile. Request handling latency is somewhere between 15..200ms.
Then suddenly it takes 5+ seconds to fail to serve a request (returns 500), and produces no meaninful application logs for this request. The next log message is "Billing disabled. Shutting down instance."
And that's the end of it. All subsequent log entries indicate either a 500 on /_ah/warmup (with the error message being "The warmup request failed. Please check your warmup handler implementation and make sure it's working correctly."), followed by "Billing disabled. Shutting down instance.", or 500 to usual application requests, now taking several seconds. No application messages in the log at all, just GAE messages. Quotas are nowhere near their limits. No service messages of any kind indicating service terms change for any dependencies.
Where to go from here? This is a mission critical application, pretty painful not to have available.
--vt
Hi @climategadgets -- I'm not sure if maybe you're the user or maintainer of this application but I'm sorry to hear you're having trouble with this. From the brief description it sounds like you may want to contact Google Cloud Billing Support as you may be experiencing an issue with the billing for the associate project.
You can also start investigating yourself. Assuming that your app is an App Engine one then it should be that it is part of a GCP Project. Examine the project and see what Billing Account is associated with it. Validate that the billing account is in good state. I heard you say that the applications has been running for a decade. Are you by any chance paying for your expenses with a Credit Card that has now expired?
I had the same problem that happened few days before. My application is very small and uses very few kbytes in storage. Almost for my personal use. It was created long time ago as your
I solved it by filling the billing form in Google Cloud Platform for all my projects.
And in few minutes it was solved.
In my case it was solved first in some APP-hrd.appspot.com first. This project was created by myself to accomplish a mandatory migration of database (DB to NDB) years before.
I hope you have success too.
Any update on this post? I have been facing the exactly same issue "Billing disabled. Shutting down instance." from the same time point 8/14. The issue is still persisting. I tried to find how to setup billing but the Settings page does not give me the option. My project is also started almost a decade ago and it utilize a tiny resource.