I keep seeing these errors in the stackdriver logs for a google appengine app written in go:
2017/11/05 23:30:38 internal.flushLog: Flush RPC: service bridge
returned HTTP 400 ("App Engine APIs over the Service Bridge are
disabled.\nIf they are required, enable them by setting the following
to your app.yaml:\n\nbeta_settings:\n enable_app_engine_apis:
true\n")
Does anyone know the proper way to resolve this? I looked in the docs and the enable_app_engine_apis beta setting has been deprecated. The app does work but this continually clutters the logs.
I had the same problem and I asked Google Cloud Support. They replied that there is no way to avoid outputting it to the error log, as it requires a fix on their end. They raised a github issue. Here is the link:
https://github.com/GoogleCloudPlatform/appengine-sidecars-docker/issues/82
Related
I deployed Java 11 app on Google Cloud App Engine, and app is running fine, I can see the home page in the browser, but when the app tries to call Microsoft Graph API (the HTTP call is executed by using Microsoft Graph SDK), I am getting runtime failure.
The failure relates to Google debugger, but I didn't even enable debugger. I found information that debugger is enabled by default when Google builds the container image. I have two options - either to figure out why I am getting 401 error for the debugger, and configure debugger properly, or disable debugger completely.
I tried to find information how to disable Google debugger for container image generation, but didn't find anything helpful. I also tried to find information how to configure debugger properly for app engine, and also was not able to find complete working instructions. Does someone know what I need to configure on App Engine to bypass this error:
java.io.IOException: Server returned HTTP response code: 401 for URL: https://clouddebugger.googleapis.com/v2/controller/debuggees/register
at com.google.devtools.cdbg.debuglets.java.GcpHubClient.registerDebuggee
Assuming your Java app is in an App Engine Standard environment and using the bundled services, then you are still using appengine-web.xml file for app configuration. As stated in GAE standard Issuing HTTP(S) Request documentation:
URL Fetch will handle all outbound requests and cause requests that you send to your VPC network or the client libraries to fail. If any of these scenarios apply to you, make sure that the url-stream-handler field in your configuration is not set to urlfetch.
This scenario includes Google Cloud Debugger Client for Java hence the HTTP error. As a workaround, you can omit the following line in the appengine-web.xml file:
<url-stream-handler>urlfetch</url-stream-handler>
Recently one of our sites got suspended by Google Ads due to "Destination Not Working". When I talked with Google Support they told me that my site is not accessible from all location globally. Then I tried to investigate, the site is hosted on Google App Engine. And I didn't find any 500 errors. But sometimes some website checking tools like "Uptrends" showed me inconsistent error "Http Protocol Error"/500 error. Then I tried to see closely on Google stackdriver logging and ran several tests on Uptrends and on other tools. But I saw something like this.
And on App Engine logging, I saw something like -
And also sometimes some HTTP request is not hitting my app so my app logging is not working and it's bothering us so much. We are losing tons of our marketing budget due to this facts. So it would be great if anybody come forward and tell me any clue to test and help me to investigate.
204s mostly happen because of RAM issue, so boosting to a bigger instance type usually clears these up
https://issuetracker.google.com/issues/35900014
I've gotten a 204 before and it was because there was a memory leak in app engine's ssl library. I was passing it the string to a cert file and it wasn't closing those files. The work-around to fix it was to handle the opening and closing of the file myself and pass it the file handle instead.
If you pay for Google Cloud Support, they may be able to help dig into things that are not visible to you.
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.
Yesterday I try to disable "Google Cloud Datastore API (v1beta2)" API for two google cloud projects. Unfortunately it seems there was some kind of error as the popup window with something like "Sorry, there was an error on our side" appeared.
An API disapear from list of API but now when I try to enable either "Google Cloud Datastore API (v1beta2)" or "Google Cloud Datastore API" (which is v1beta3) I receive following error:
"Cannot ENABLE any API when there is a pending request to DISABLE any API"
Please help, thank you
Unfortunately, it looks like Google needs to manually solve this for you. I have the same issue, and it being Sunday, it's hard to get support.
Edit: I was directed here https://code.google.com/p/google-cloud-platform/issues/list
There is currently a bug with disabling v1beta2 that causes the operation to hang for a long time.
By design, you can't enable an API when there are other pending enable/disable operations.
We are actively working on the problem. Sorry for the inconvenience!
I am attempting to follow the tutorial at: http://www.youtube.com/watch?v=v9TG7OzsZqQ
My Cloud Endpoint REST API works well on my local development machine, but when I deploy to App Engine, I receive errors in my Admin Log that "API serving not allowed for this application".
Is this a paid feature that I must enable billing to receive? If not, is there documentation that explains this issue and how to fix this error?
To use Endpoints in production you need to be accepted into the trusted tester program. You can apply here. Mention this Stack Overflow post in your request and I'll see if I can expedite approval.