Up until this morning I was able to migrate appengine traffic to different versions of my appengine app. I am now getting an error when I try and do this. Both the console and the command prevent me from migrating traffic. Is this a bug or intentional?
cloud app versions migrate master15166002 Migrating all traffic from version [default/master15141296] to [default/master15166002]
Do you want to continue (Y/n)? y
ERROR: (gcloud.app.versions.migrate) Issues migrating all traffic of service(s): [default]
INVALID_ARGUMENT: Invalid request.
- '#type': type.googleapis.com/google.rpc.BadRequest
fieldViolations:
- description: Traffic migration does not support Managed VMs.
field: service
- description: Traffic cannot be migrated to a version with basic or manual scaling.
field: service.split.allocations[master15141296]
- description: Traffic migration does not support Managed VMs.
field: service
- description: Traffic cannot be migrated to a version with basic or manual scaling.
field: service.split.allocations[master15166002]
- description: Warmup requests must be enabled for all versions that will gain additional
traffic as a result of the traffic migration.
field: service.split.allocations[master15166002]
Sounds like you are using the old Managed VMs environment that was deprecated over a year ago (Nov 15, 2016). The shutdown date was December 15th. This same page has information for how to upgrade your application from the old (and deprecated) Managed VM beta.
Turns out there was a bug with the API/Console. It fixed itself a day later.
Related
Over the past two weeks, I've discovered preview-mode no longer works on new GTM server-side deployments.
(I'm no stranger to setting up and configuring google tag manager browser and server. I've deployed MANY of these and implemented highly customized setups.)
I'm automatically provisioning Google Tag Manager server-side on GCP App Engine Flexible instance. Nothing custom.
Paid for GCP support. They said to get in contact with the GTM team or the community support group.
Tried lodging a support request on the Google Tag Manager community support group. No answer.
Can't find a way to contact the GTM development team.
To investigate, I tried pairing GTM browser with older GTM server setups I deployed months ago via the GA4 transport url method. Works without problem.
I narrowed the issue to some kind of server-related issue:
Debug memo dispatch to http://localhost:8081 failed:
Error: cacheableLookup ENOTFOUND localhost at CacheableLookup.lookupAsync (/workspace/node_modules/cacheable-lookup/source/index.js:199:18)
{code: 'ENOTFOUND', hostname: 'localhost'}
This is a known bug, has been diagnosed by the GTM team, and will hopefully be fixed very soon. The problem is that App Engine changed that localhost no longer responds to the requests from the tagging server, so Preview mode is unable to show the results.
We have setup our api service behind an App Engine's flexible environment. We are currently on the Bronze support plan.
We were recently audited by a security contractor and one of the issues reported back to us is the fact that our service accepts older versions of TLS.
I found a couple similar questions abound this topic, namely:
How to update TLS version
Google App Engine Node.js TLS 1.2
Is there a way to customize nginx proxy in google flexible appengine
So, the information I gathered by now is that cannout customize this, but I might be able to request for our load balancer to only support TLS >= 1.2. Is this info still valid as of 2020?
If it is, could someone help me figure out how? I seem to only find the chat and phone support for Billing issues. Do I need to request for someone to update our support plan for this kind of request?
I have read the document which says that gcloud app versions migrate operation can migrate traffics into another version, but it couldn't. The error description seems to say something informative, but no help to me. On GCP control panel, version migration works fine. What's happening on this?
$ gcloud app versions migrate 20190122-120543-ebbfbc9 -s q
Migrating all traffic from version [q/20190129-164614-09e8288] to
[q/20190122-120543-ebbfbc9]
Do you want to continue (Y/n)?
ERROR: (gcloud.app.versions.migrate) Issues migrating all traffic of service(s): [q]
INVALID_ARGUMENT: Invalid request.
- '#type': type.googleapis.com/google.rpc.BadRequest
fieldViolations:
- description: Warmup requests must be enabled for all versions that will gain additional
traffic as a result of the traffic migration.
field: service.split.allocations[20190122-120543-ebbfbc9]
When you use gcloud app versions migrate it will try to do a gradual migration. Gradual traffic migration is only supported for the Standard environment and you have to enable warmup requests on the target version for this to work.
It’s working on GCP Console because there you’ll be prompted to do an immediate migration if the above conditions are not met.
If you want to use gcloud to migrate traffic to a GAE Standard version set to warmup disabled, or Flex environment, you can use the following command which will actually split the traffic immediately (not gradually) 100% to the target version:
gcloud app services set-traffic [MY_SERVICE] --splits [MY_VERSION]=1
You can find more information here
Hope it helps! :)
Google Cloud Server suddenly stopped working. Yesterday I got the error , " Error establishing database connection".
Today it is "Request Timeout
Server timeout waiting for the HTTP request from the client"
Any suggestions to get over this issue??
This could happen based on the configuration you have on your app.yaml. If the instances are overloaded you might encounter a 408 when trying to communicate with the server, in that case changing the scaling configuration on your yaml file might fix the issue.
This document can help you with configuration of your yaml file, information with auto and manual scaling, healthcheck, readiness check etc.
And this article would give you general information on how scaling work on App Engine and best practices.
Also, if you’re using WordPress, this is a common issue with WordPress
My company is looking to set up a Sharepoint server for some of our internal users. We would like this to be accessible to external users using our current domain (www.companyname.com). The problem we are having is that www.companyname.com is set up using an IBM HTTP Server (basically Apache) and is based mostly around Java and Websphere. I was wondering if there was a plug-in available for Apache that would allow my to link up the Sharepoint server (running on IIS) with Apache, much like what is done with Websphere and Apache. Any help would be appreciated.
You could probably just use the generic HTTP reverse proxy support in Apache. If you use this in IHS to front-end sharepoint, it would not be supported by IBM and is technically in violation of the license.
If you receive IHS with an IBM product, it's only licensed and supported when used in direct support of the product it came with.