i can;t deploy app to GAE anymore.
App deploy was always stuck with time out.
Some days ago app was working fine. I was able to deploy. I'm sure.
I pickup old version, just to eliminate possibility that something wrong with app
I try to deploy with all reasonable parameters.
I try delete all services (except default which i can't delete, however i uploaded basic one line app)
I already try most of advice which i found on web
I try to disable App engine.. It failed, however after some time i was able to Disable it.
Now i'm not able to enable GAE.. i see folowing error:
ERROR: (gcloud.app.deploy) Unable to deploy to application [**************] with status [USER_DISABLED]: Deploying to stopped apps is not allowed.
Any advice is welcome:
- How to enable GAE
- How to avoid time outs during deploy App to GAE
Thanks a lot
The public issue tracker is a good place to put bugs and/or feature requests. For faster and more urgent issues, contact the Google Cloud Platform support team directly and they will be able to assist you.
Your issue could also simple be a propagation delay, so if in 24/48 hours and you still can't, then it's likely a bug. Furthermore, you can always deploy to another project if it's all the same to you.
Related
I have a Quarkus application already deployed on Google Cloud Run.
It depends on MySQL, hence there is an instance started on Cloud SQL.
Next step in my deployment process is to add keycloak. From what I've read the best option seems to be Google App Engine.
The approved answer in this question gave me some good insight of what needs to be done ... mostly.
What I did was:
Locally I made a sub-directory in the main project.
In that directory I added the app.yaml and the Dockerfile (as described here for instance).
There I executed the said two commands: gcloud init and gcloud app deploy.
I had my doubts about this set up and they were backed up by the error I got eventually:
ERROR: (gcloud.app.deploy) INVALID_ARGUMENT: The first service (module) you upload to a new application must be the 'default' service (module). Please upload a version of the 'default' service (module) before uploading a version for the 'morph-keycloak-service' service (module).
I understand my set up breaks the overall structure of the project but I'm not sure how to mix those two application with the right services.
I understand keycloak is a stateful application, hence cannot live on Cloud Run (by the way the intention is for keycloak to use the same database instance shared with the application).
So does any one know a more sensible set up, or what can I move in mine in order to fix it?
In short:
The answer really is in reading the error message (thanks #gaefan) - about the error itself it explains enough. So I just commented out the service: my-keycloak-service line in the app.yaml (thus leaving gcloud to implicitly mark it as the default one) and the deployment continued.
Eventually keycloak didn't connect to the database but if I don't manage to adjust the configurations that would probably be a subject to a different question.
On the point of project structure and functionality:
First off, thanks #NoCommandLine and #guillaume-blaquiere for your input!
#NoCommandLine the application on Cloud Run is sort of a headless REST API enabled backend. Most of the API calls are secured by keycloack. A next step in the deployment process would be to port an existing UI (React) client on the Firebase hosting (or on another suitable service - I'm still not completely sure which approach is best) and in order for the users to work with this client properly they must make an SSO through keycloak first.
I'm quite new to GCP and the number and variants of the available options are still overwhelming to me - one must get familiar with the nuances but I guess it takes time. So I'm still taking suggestions on how to adjust my project structure to fit better the services stack. Thanks!
I've setup Google App Engine to run my AdonisJS API for my website. I update the code using the CLI for google cloud services ("gcloud app deploy"). I get a success message from the terminal, and I have checked both the cloud build and version number, and both are the most recent deployment. However, when I try to use my website, I get an error due to the API using old code and trying to access table columns from my database that no longer exist. I have downloaded the most recent cloud build file and checked the codebase within it and the updated code is there. I have also tried deploying multiple times, and it still is using the old code. Does anyone know why this is happening and/or how to fix this?
If you need more information, let me know. Thanks
ANSWER:
Fixed this a while ago, but wanted to update here just in case others ran into this. I discovered that when deploying to GAE through the command line, my build command wasn't running prior to the deploy since my script had an error, so it was uploading updated code, but not an updated build. So just make sure to run the build command prior to uploading to GAE and everything should work.
In console.cloud.google.com, go to your GAE project and check which version of your project is running I.e. which one is receiving traffic
Clear your cache.
My questions is in two folds: issue with app engine:update and with the app cfg.sh.
I looked on the web and could not find any workaround or potential answer that could help me fixing this issue.
My application is working with not much issue locally. Time now to give it a shot on production and upload it to google app engine. At first I tried doing this by using the 'app engine:update' from gradle (I'm using Android Studio). The execution failed with the following error message: "toolkit not found: apple.awt.ctoolkit. Why is this toolkit required and where can we find it?
While searching on the internet there were suggestions to use the appcfg.sh script to upload the application. It seemed to work at first until it asked for email and password. I used the exact same email/password I use to connect to goole-appengine and for some reasons it does not work.
Thanks.
After few hours investigating this issue I found out what the issues were. First thing, my account was compromised and received an email from Google. All I had is to confirm that was me trying to upload application to GAE. Secondly, my primary email address linked to my Google account belongs to another ISP. There is a security feature to disable and for security being a bit more loose. Creating a gmail account did the trick.
As soon as I figured out how to invoke my app as a Backends app, my log messages stopped appearing.
I found this helpful post which says the Backends logs are kept separately and that I need to switch to Backends view by selecting the named backend from the dropdown at the top of the admin console, but I don't see anything Backends specific in that list to select.
Perhaps this is a clue... when I invoke my app via myapp.appspot.com/dostuff, in the log I see I'm getting the DeadlineExceededError after 60 secs, indicating it's not running as a Backends app. But when I invoke it via mybackend.myapp.appspot.com/dostuff, it continues running as needed, but no log entries!
Seems like I'm missing something. Thanks.
Somehow my app wasn't fully recognized by GAE as a Backend app. And therefore my backend instances weren't available in the drop-list. Seeing that others had similar trouble with a Python 2.7 app (ex.) that had been initially uploaded as a 2.5 app, I created a new app in GAE and uploaded to there and it worked. Sorry I don't have a more definitive answer.
Before all was working well, I also ended up creating an empty /_ah/start handler as suggested by someone in this thread. Also if you're deploying a multi-threaded backend, make sure to check this post out -- there's some important stuff I didn't run across in the docs.
I use Google AppEngine plugin for eclipse. It works fine every time, but when I updated to the new plugin yesterday, I could not deploy my application, and it shows an error box CAN NOT SIGN IN [com.google.api.client.http.HttpResponseException: 400 Bad Request] :
I can't figure what is the problem.
My system time was wrong, and this problem have been solved for me when I synchronize time on my computer with internet.
May be it also will be useful for you.