Hi Have VPC established between cloudhub and my netwrok and it was fine when i used to deploy the application there .
Suddenly , i have started getting the following error while deploying the application in the same environment .
Cannot update load balancer: java.io.IOException: com.amazonaws.AmazonServiceException: Rate for operation ChangeResourceRecordSets exceeded (Service: AmazonRoute53; Status Code: 400; Error Code: Throttling; Request ID: c811181f-0887-11e7-873f-5d34219fe6f8)
Can some one let me know whats happening here ?
please refer to this forum post .
https://forums.mulesoft.com/questions/60915/getting-javaioioexception-comamazonawsamazonservic.html
I think this may be related to this.
Amazon Route53 has issues since yesterday: (see https://status.aws.amazon.com/ for more info). Creation/update/delete queries are being throttled.
Related
Hi i have rds database hosted in aws , i try to update-database via asp.net web api
i get this error :
An exception has been raised that is likely due to a transient failure. Consider enabling transient error resiliency by adding 'EnableRetryOnFailure' to the 'UseSqlServer' call.
i try to add EnableRetryOnFailure and its just continue to execute the failed code nonstop until i stop it , long story short i cant find a solution i have custom security group in the rds DB and its avaiable for public . What could be the problem here ?
I am getting an error message while following this https://docs.aws.amazon.com/managed-blockchain/latest/hyperledger-fabric-dev/managed-blockchain-get-started-tutorial.html tutorial from Amazon Managed Blockchain for Hyperledger Fabric. I have followed all steps properly but I got stuck while trying to join a channel. I am a newbie in Hyperledger Fabric and Amazon Managed Blockchain. I have attached an image of the error message below. Help me!!!
Error Image
The error you are getting:
Failed to create new connection: context deadline exceeded
Can be caused by:
A misconfiguration of ChannelIDs. Make sure the ChannelIDs match and that you are attempting to join the peer to the correct channel.
Using the wrong root certificate file for TLS. Make sure the root certificate file and root certificate path are correct.
Here is a link to the question this answer was based on, involving the same error in a different context.
I tried to create a Google Cloud Composer environment but in the page to set it up I get the following errors:
Service Error: Failed to load GKE machine types. Please leave the field
empty to apply default values or retry later.
Service Error: Failed to load regions. Please leave the field empty to
apply default values or retry later.
Service Error: Failed to load zones. Please leave the field empty to apply
default values or retry later.
Service Error: Failed to load service accounts. Please leave the field
empty to apply default values or retry later.
The only parameters GCP lets me change are the region and the number of nodes, but still lets me create the environment. After 30 minutes the environment crashes with the following error:
CREATE operation on this environment failed 1 day ago with the following error message:
Http error status code: 400
Http error message: BAD REQUEST
Errors in: [Web server]; Error messages:
Failed to deploy the Airflow web server. This might be a temporary issue. You can retry the operation later.
If the issue persists, it might be caused by problems with permissions or network configuration. For more information, see https://cloud.google.com/composer/docs/troubleshooting-environment-creation.
An internal error occurred while processing task /app-engine-flex/flex_await_healthy/flex_await_healthy>2021-07-20T14:31:23.047Z7050.xd.0: Your deployment has failed to become healthy in the allotted time and therefore was rolled back. If you believe this was an error, try adjusting the 'app_start_timeout_sec' setting in the 'readiness_check' section.
Got error "Another operation failed." during CP_DEPLOYMENT_CREATING_STANDARD []
Is it a problem with permissions? If so, what permissions do I need? Thank you!
It looks like more of a temporary issue:
the first set of errors is stating you cannot load the metadata :
regions list, zones list ....
you dont have a clear
PERMISSION_DENIED error
the second error: is suggesting also:
This might be a temporary issue.
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.
This is a really strange one as it started throwing errors over night - it's been working fine up until yesterday - this morning it's been playing all day.
I'm using illuminate/filesystem in my project and for the endpoint I was using:
https://s3.eu-west-2.amazonaws.com
This morning we started getting errors saying:
Error executing "ListObjects" on "bucket-01.https://s3.eu-west-2.amazonaws.com"; AWS HTTP error: cURL error 1: Protocol "bucket-01.https" not supported or disabled in libcurl (see https://curl.haxx.se/libcurl/c/libcurl-errors.html)
File: .../vendor/aws/aws-sdk-php/src/WrappedHttpHandler.php
Line: 195
Seeing that it tries to prepend bucket name before the protocol of the endpoint I've decided to remove protocol from the endpoint - making it
s3.eu-west-2.amazonaws.com
Now I'm getting error saying
Error executing "ListObjects" on "//bucket-01.s3.eu-west-2.amazonaws.com/bucket-01.s3.eu-west-2.amazonaws.com";
AWS HTTP error: Client error: GET http://bucket-01.s3.eu-west-2.amazonaws.com/bucket-01.s3.eu-west-2.amazonaws.com resulted in a 404 Not Found response
NoSuchKey The specified key does not exist.
As you can see now it appends endpoint after the initial endpoint.
Does anyone know what might have happened?
After hours of searching for the solution I've came across this issue on laravel/framework repository https://github.com/laravel/framework/issues/36694