1 Answer
- Newest
- Most votes
- Most comments
0
I stopped/started the instances and I was able to connect. Don't know if they resumed the prior reboot command or what, so I attempted to reboot again and they completed this time. A big mystery. Doesn't instill confidence.
So, the solution Amazon provides us is the Microsoft mantra, reboot/restart/reboot/restart/re<verb>/re<verb>/re<verb>... until the thing starts working again. The future is here, people, and it requires frequent starts!
answered 2 years ago
Relevant content
- asked 7 months ago
- asked 3 months ago
- asked 3 years ago
- asked a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
Comon guys, this isn't a problem that I should need paid technical support for. Something is wrong with the boot process and I haven't tampered with it. Two instances of the same AMI booted and two failed. Can anyone look at this?
The two failed instances are in the "Running" state, so I am being billed for two instances that are not actually running.