In past 3 - 4 days, I have been getting 503 whenever I deploy in Standard Environment. This happens very frequently, usually about 3 hours after new deployment
I checked https://status.cloud.google.com/ and there doesn't seem to be known incident. However, on October 6th, there seems to be an incident that sounds like the issue I'm facing right now https://status.cloud.google.com/incident/appengine/20007
Can somebody help guide us what to do?
Related
Over the past few weeks my gcloud app deploy has been failing regularly, today it fails even after attempting 10 times so far. According to the google cloud web interface, it is failing after build in the exporting phase:
7: exporter
/cnb/lifecycle/exporter asia.gcr.io/<project>/app-engine-tmp/app/ttl-2h:<uuid>
Is there anything we can do about this at all?
(The build itself takes just a few minutes, then this exporter phase runs until the 10m mark and is killed.)
Perhaps there is a way to make gcloud app deploy do the build in the asia region?
I deleted everything in the Google Cloud Console under the "Container Registry" menu option. Not sure why that helps, but builds now average 2 minutes instead of the historical 9-11 minutes for the past year or so.
(Although this technically doesn't answer why behind the question, this does solve the strange delays in building on appengine (standard). I am going to mark it as solved and leave this question here in case others encounter the error message above.)
Just started getting this error - having made no code change.
GAE/J on Datastore Datanucleus JDO/JPA version: v1
my app on EU servers don't run.
US unaffected currently.
Suspect Google have broken something internally.
can anyone concur?
Yes, I started seeing a similar problem starting around 40 minutes ago. EU-based servers for my app as well. Refreshing works about 50% of the time.
This question already has an answer here:
MEAN development stack failed to deploy
(1 answer)
Closed 7 years ago.
I tried to deploy MEAN stack using Google Developers Console, and failed after trying several times, the error is always the same. Is there any fix around this other than deploying the whole stack manually ?
Your MEAN development stack failed to deploy
Dec 1, 2014, 3:12:51 PM
meanStackBox: DEPLOYMENT_FAILED
Replica mean-zeuw failed with status PERMANENTLY_FAILING: Replica State changed to PERMANENTLY_FAILING. Replica was unhealthy 2 consecutive times.
What to do next:
Review the troubleshooting guide
Delete stack
I am getting the same error as well. Tried changing the Zone as well as other variables under the Advanced options but nothing is working so far. Googling shows the last time this happened a fix was needed to be deployed by Google - MEAN development stack failed to deploy. It took 2 days for that question to be posted and the reply from Brian who I assume must be working for Google in some capacity. So if this started to happen from yesterday then hopefully the fix will come tomorrow :)
It seems like this issue could be related to the zone/region settings in your instance.
Take a look at this answer, where my colleague found a successful workaround.
App engine (python 2.7, Mac OS X, latest version as of today) deployment seems to go fine (compilation completed) but deployment is stuck repeating "Will check again in 60 seconds" every 60 seconds until it finally fails, saying :
File "/Applications/GoogleAppEngineLauncher.app/Contents/Resources/GoogleAppEngine-default.bundle/Contents/Resources/google_appengine/google/appengine/tools/appcfg.py", line 2025, in Commit
raise Exception('Version not ready.')
Exception: Version not ready.
I've checked appengine status on code.google.com and nothing seems to go wrong.
Any idea if rollback is compulsory ? I had the same problem a couple of hours ago, but after a couple of tries it worked. This time it seems more serious, as i've been stuck in that state for a couple a hours now. Any advice ?
As mentioned in the comments, these types of issues are best served on the mailing list or issue tracker. However, for the particular issue you mentioned, a production issue was filed and resolved. You shouldn't be seeing this issue any longer.
I'm no longer able to upload code to my app engine app. The following are the symptoms that I'm experiencing:
Code compiles and files are uploaded. Update fails during "Verifying availability" Here's the specific stuff from the console:
Deploying new version.
Verifying availability:
Will check again in 1 seconds.
Will check again in 2 seconds.
Will check again in 4 seconds.
Will check again in 8 seconds.
Will check again in 16 seconds.
Will check again in 32 seconds.
Will check again in 60 seconds.
.
.
.
Will check again in 60 seconds.
Will check again in 60 seconds.
Will check again in 60 seconds.
on backend null.
java.lang.RuntimeException: Version not ready.
When I look in the Admin Console it indicates that the new version uploaded, however, the old code is still running. I tried using a different machine to upload a Hello World example to isolate my main development machine and project. I get the same result with the other machine/app. I also tried to upload the app from the command line but got the same result. I ran appcfg.sh rollback (I'm on a Mac) and it completes without error but still the problem persists.
I don't recall a specific change to my app engine configuration immediately before the problem began, but I had changed the version to 0.1 within a couple of hours of my problems starting. The app engine rejected the version number due to the period in the version number. It took a long time to figure this out because the feedback was cryptic. I mention this because a) the feedback was cryptic and b) the error specifically mentions "Version not ready".
Can anyone help me figure out what I did and how to undo it? If it helps, my app ID is milkmooseexperimental
Thank you.
It's a Server Side issue. I'm experiencing the same problem as well, and have been unable to deploy for the last 12 hours. I'm not sure whether this has anything to do with the scheduled outage window.