Using Spinnaker-Ubuntu-14.04-42 (ami-cfb87eaf) AMI I have created an instance. I have followed the instructions given at here. Though my UI works, but when I click Actions and Create Application the New Application popup seems to take lot of time and it does not finish. What could be a problem?
Finally, I found the solution to the problem, by following the instructions given at following links:
Troubleshooting guide, by looking at the Javascript, I figured that the problem is caused due to the credentials of AWS account/user. The error was 429 Too Many Requests.
Then following the instructions given here, especially bulleted point 3, I was able to start the application.
When I was getting this. I found I actually needed to use a bigger sized instance. Try using one with more memory.
Related
Attempted a minor system update to WikiJS yesterday afternoon, and when the site came up for a restart... all I'm getting now is a site can't be reached failure.
Having issues SSH'ing into the box, and am looking for ways around that particular problem. It's hosted on an AWS EC2 instance that I can stop/start/reboot, but that's it.
At one point yesterday I did get an Unknown authentication strategy "jwt" error, but now it's showing nothing again.
While I'm working through the issues of getting into the box itself, is there anything that jumps out at y'all that I should be looking towards?
Many thanks in advance.
I'm newbie in AWS, with my free tier account I'm trying to build my nodeJS project with AWS CodeBuild but I get this error:
Build failed to start The build failed to start. The following error occured: Cannot have more than 0 builds in queue for the account
I followed the simple aws tutorial, leaving all default settings for let aws create all service, image etc for me.
Also I stored source code in a AwsCodeCommit repository.
Could anybody help me?
In my case, there was a security vulnerability in my account and AWS automatically raised a support ticket and suspended all resources that were linked to it. I had to fix it and then on chat with aws support they resumed my service.
I've seen a lot of answers around the web suggesting to call support, which is a great idea, but I was actually able to get around this on my own.
As the root user I went in and put in a current credit card. The one that was currently there was expired. I then deleted my CodeBuild project and create a new one. Now my builds work! It makes sense that AWS just needed a valid payment method before it allowed me to use premium services.
My solution may not work for you, but sure I hope it does!
My error was Project-level concurrent build limit cannot exceed the account-level concurrent build limit of 1 when I tried to increase the Concurrent build limit under checkbox Restrict number of concurrent builds this project can start in CodeBuild Project Configuration. I resolved it by writing to support to increase the limit. They increased it to 20 and it works now as expected. They increased it even though I'm on Basic plan on AWS if anyone's wondering.
My solution was to add new service role name and the concurrent build to 1. This worked
I think your issue is resolved at the moment. Any way I faced the same issue. In my case I had a "code build project" connecting to a GitHub repository. And then I added AWS Access Key and Secret hard coding the buildspec.yml file. With this AWS identified it as an unauthorized login. So they added security restrictions to the resources while opening a support issue. In such a case you can look for the emails from AWS in which they explain the reason for this behavior and the steps to get this corrected.
I've been using a Windows 2008R2 EC2 instance for some time. As of today, it still works. I started working with the AWS API, and I was unable to start my instance using the API, the error message being "not authorized for images", specifically : An error occurred (AuthFailure) when calling the RunInstances operation: Not authorized for images: [ami-088dab1e]
That's when I learned about deprecation.
From what I read, what this means is that the AMI being used is no longer publicly available. When using the API call "describe-images", this image cannot be queried. While it apparently can still be used from the console, the API simply doesn't support it and will not start an instance using that image ID. On the console, the AMI description reads : Cannot load details for ami-088dab1e. You may not be permitted to view it.
I understand how to find a new image and I think I understand how to launch my instance using a new image. However, I have lots of custom software installed on this instance. So before I try it, I want to know if I will lose that custom software installation if I launch my existing instance with a new AMI. I'm hoping that my custom software won't change, but I'm skeptical. I don't want to fire up a brand new version of Windows and start from scratch. Mostly, I don't want to lose what I've already got.
I know this is a basic question, but I've looked all over, and I haven't yet found a straightforward answer. I was hoping y'all would know. Thanks.
I think I've found an answer here: AWS EC2 new instance from image AMI
When launching an instance from an Amazon Machine Image (AMI), the disks will contain an exact copy of the disk at the time that the AMI was created.
In other words, if I start a new instance, I'll lose my installed software. WRONG!
Launching != starting. More editing to come once I get this completely figured out.
So, given that updated Windows images are created and deprecated all the time, and the Windows OS is constantly updated by Microsoft, one must wonder how it is a static Windows image can be used with other software? It seems like far more trouble than it's worth, if you've got to constantly reinstall your software to keep your Windows system up to date.
Amazon recently came up with a solution for that, here: Patching Windows
I don't know how to do it yet, but this seems like exactly what I need in order to keep Windows up to date, and keep my installed software intact.
I am actually experimenting with the new Machine Learning API on Google cloud. All tutorials work great, Machine Learning API is activated, I can train models and access the status of the Jobs in the command line. But for some reason, I can't open the page https://console.cloud.google.com/ml/ to manage my models and jobs online.
Also, I don't have the Machine Learning button in the "Product and Services" column on the left from https://console.cloud.google.com/home/dashboard.
Even if I can do without, I wish I could have access to this console to make my work easier.
I found the same question here: Where is the Google Cloud ML Console UI? but the problem seems to be fixed since one of my colleague have access to it. Is there something to update?
I think the fix to enabling public access to all is in the process of rolling out. Sorry for the inconvenience and thanks for patience!
Is it possible that your colleague was a member of our alpha program, and was previously whitelisted to the console functonality?
I am working on new project. Here in this new project I need to run only one instance of application at one time. Not two instance of application should run. If user tried to open another instance that time it should give error.
Can anybody help me out. how can I achieve this.
Thank You
I found this link.
This link is basically about to use CreateMutex for the same issue.
According to this link, you can use "CreateMutex" to find if your app is currently running. When your application tries to run 2nd application, it will get error.
There are some sample codes for this. I hope this helps.