1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Unfortunately, there's not really enough information to go on here. Please create a support case because our support team can help you troubleshoot this issue.
Note that we have documentation to help:
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html
https://aws.amazon.com/premiumsupport/knowledge-center/ec2-windows-system-status-check-fail/
Contenus pertinents
- demandé il y a 10 mois
- demandé il y a un an
- demandé il y a un an
AWS OFFICIELA mis à jour il y a 8 mois- AWS OFFICIELA mis à jour il y a 3 ans
Looking further into the system log, it shows the original IP address even though this changed after reboot - we had not set an elastic IP (Instance ID is i-0047e658913bb7c02) .
Creating a clone (i-0123f19b737b00af2) from the original does not help as it inherits the same IP address problem.
I assume this is set in the /etc/hosts file but we have no way of changing unless we can get the instance started.
Is there any other way we can wipe this? Perhaps create a new root volume and attach that to this system?
What you can do is create a new instance; mount the existing volume to that instance; edit the
/etc/hostsfile; then relaunch the (original) instance.