By using AWS re:Post, you agree to the Terms of Use
/ec2 (Spot instances) going from Runing - Initializing to Terminated/

ec2 (Spot instances) going from Runing - Initializing to Terminated

0

I do have an EC2 instance with a gitlab-manager runinc (it was working for the past year until this morning).

The gitlab-manager is configuerd to always keep 1 machine running on a spot instance.

"amazonec2-request-spot-instance=true",

This morning the Instances created from the manager aint working, It starts the instance but it stays with the "Status Check" Initializing. After some time the instance is shuted-down and a new request to create a new instance is made.

I tryed to debug the gitlab-manager but it seems that the problem is happening during the instance inicialization on AWS.

What can I do? How can I debug the reason for the instance to not initialize?

Felipe Colussi
asked 20 days ago2 views
1 Answers
0

Have you already looked into the different events for Spot to try and get more information? https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/spot-interruptions.html#spot-instance-termination-notices Typically it will tell you if there's insufficient capacity if it's Spot related. Issue could be related to other items like underlying EBS volume for the AMI not being accessible or a number of other items. Can you launch the instance outside the autoscaling group and not as spot?

EXPERT
Rob_H
answered 20 days ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions