I am using GCP spanner as my project RDBMS . Lately I am getting a lot of error like the one mentioned above in the logs. Can someone help me figure out what is going wrong here ?
I tried going through google docs, but found very little on the above error . Is it something related to session pool configuration ? How this can be resolved ?
Note: I have only 1 spanner db, which is running on 1 instance on GCP.
Any help is deeply appreciated :)
Thanks
ps:
Error: Got unhandled rejection {"stack":"Error: Unable to release unknown resource.\n at SessionPool.release (/testProject/node_modules/#google-cloud/spanner/build/src/session-pool.js:241:19)\n at <anonymous>\n at process._tickCallback (internal/process/next_tick.js:189:7)","message":"Unable to release unknown resource.","resource":{}}
at process.on (/testProject/index.js:22:17)
Related
My group had a web application running using Elastic Beanstalk. For several months, it worked fine, but now the website shows the error
'radiology-ai-env.eba-wgmpba4k.us-west-2.elasticbeanstalk.com is currently unable to handle this request.'
When I try to rebuild the environment, I get two error messages:
1.) LaunchWaitCondition failed. The expected number of EC2 instances were not initialized within the given time. Rebuild the environment. If this persists, contact support.
2.) Stack named 'awseb-e-pw8nbmshem-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBInstanceLaunchWaitCondition].
I am wondering what can be changed to fix this issue, and would appreciate any help. Thank you so much in advance!! I can follow up with more info if it is helpful.
Following error is being shown:
Workflow failed. Causes: Error: Message: Invalid value for field 'resource.properties.networkInterfaces[0].subnetwork': 'regions/xxxxx-xxxx/subnetworks/xxxxx-xxxx-xxx'. The project 'projects' was not found. HTTP Code: 400
Please anyone suggest what caused this error.
Solution: Do not need to change anything. This error fix on its own after few times. Seems to be a google's global issue.
We had the same error and already solved it. Not sure what caused it but try our solution to see if it serves you.
We changed the Subnetwork parameter from short form to complete URL.
source: https://cloud.google.com/dataflow/docs/guides/specifying-networks#subnetwork_parameter
I'm getting errors when I try to deploy a Google Cloud Function. The process hangs for about 5-10 minutes and then an error appears:
"Deployment failure:
Operation interrupted."
I tried creating a new test function with nothing in it in two different projects of mine, both are timing out with that same error.
Anyone experiencing anything similar?
There was an incident related to Cloud Functions and Cloud Build that began at 2019-09-24 13:00 and ended at 2019-09-24 18:15 (all times are US/Pacific).
It should be all good now. Please try to deploy your function again.
In case it will not work for you. Please update your question to contain more information: minimum reproducible code, dependencies, timestamp.
Yes, having the same issue here. Tried to check status on their dashboard they mark it has ok but it's not.
can someone please share how can I get the error codes which can cause session failure to a Informatica cloud job or please share any document/website for the same.
Thanks
You can use the activityLog REST API to get the error messages related to the task if it has failed. You can take a look at the developer guide here:
https://network.informatica.com/docs/DOC-15641
Alos, you can parse the session log available after the task run to look for error messages and codes.
I'm trying to develop a system service, so I use the echo service as a test.
I developed the service by following the directions on the CF doc.
Now the echo node can be running, but the echo gateway failed with the error "echo_gateway - pid=15040 tid=9321 fid=290e ERROR -- Exiting due to NATS error: Could not connect to server on nats://localhost:4222/"
I got into this issue and struck for almost a week finally someone helped me to resolve it. The underlying problemn is something else and since errors are not trapped properly it gives a wrong message. You need to goto github and get the latest code base. The fix for this issue is http://reviews.cloudfoundry.org/#/c/8891 . Once you fix this issue, you will most likely encounter a timeout field issue. the solution for that is to define the timeout field gateway.yml
A few additional properties became required in the echo_gateway.yml.erb file - specifically, the latest were default_plan and timeout, under the service group. The properties have been added to the appropriate file in the vcap-services-sample-release repo.
Looks like the fix for the misleading error has been merged into github. I haven't updated and verified this myself just yet but the gerrit comments indicate the solution is the same as what the node base has had for some time. I did previously run into that error handling and it was far more helpful.