I have " Instance reachability check failed". How can i solve this problem? There is logs.

0

Hello guys.

I cannot SSH into my instance. The status check shows a message saying "Instance reachability check failed."

At first, I thought it was a memory issue, so I changed the instance type, but the error is not resolved.

In the monitoring log, I can find a few failed messages. "mGRUB failed boot detection" "Failed to start Service for snap application lxd.activate" "Failed to start Service for amazon-ssm-agent.amazon-ssm-agent."

This instance only has Docker installed. How can I solve this problem?

Thank you.

  OK  ] Started irqbalance daemon.
         Starting Authorization Manager...
         Starting System Logging Service...
         Starting Login Service...
         Starting Disk Manager...
[  OK  ] Finished Record successful boot for GRUB.
         Starting GRUB **failed** boot detection...
[  OK  ] Started System Logging Service.
[  OK  ] Finished GRUB **failed** boot detection.
[  OK  ] Started Network Name Resolution.
[  OK  ] Reached target Network.
[  OK  ] Reached target Network is Online.
[  OK  ] Reached target Host and Network Name Lookups.
         Starting containerd container runtime...
         Starting EC2 Instance Connect Host Key Harvesting...
[  OK  ] Reached target Remote File Systems (Pre).
[  OK  ] Reached target Remote File Systems.
         Starting LSB: automatic crash report generation...
         Starting Deferred execution scheduler...
         Starting Availability of block devices...
[  OK  ] Started Regular background program processing daemon.
[  OK  ] Started Service for snap a…on-ssm-agent.amazon-ssm-agent.
         Starting Service for snap application lxd.activate...
         Starting Permit User Sessions...
[  OK  ] Started LSB: automatic crash report generation.
[  OK  ] Finished Availability of block devices.
[  OK  ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
[  OK  ] Started Deferred execution scheduler.
[FAILED] **Failed** to start Service fo…snap application lxd.activate.
See 'systemctl status snap.lxd.activate.service' for details.
[  OK  ] Started Authorization Manager.
         Starting Modem Manager...
[  OK  ] Finished Permit User Sessions.
         Starting Hold until boot process finishes up...
         Starting Terminate Plymouth Boot Screen...
[  OK  ] Finished Hold until boot process finishes up.
[  OK  ] Started Serial Getty on ttyS0.
         Starting Set console scheme...
[  OK  ] Finished Terminate Plymouth Boot Screen.
[  OK  ] Finished Set console scheme.
[  OK  ] Created slice system-getty.slice.
[  OK  ] Started Getty on tty1.
[  OK  ] Reached target Login Prompts.
[  OK  ] Started Login Service.
[  OK  ] Started Unattended Upgrades Shutdown.
[  OK  ] Started Disk Manager.
[  OK  ] Stopped Service for snap a…on-ssm-agent.amazon-ssm-agent.
[  OK  ] Started Service for snap a…on-ssm-agent.amazon-ssm-agent.
[  OK  ] Finished EC2 Instance Connect Host Key Harvesting.
         Starting OpenBSD Secure Shell server...
[  OK  ] Started OpenBSD Secure Shell server.
[  OK  ] Started Modem Manager.
[  OK  ] Stopped Service for snap a…on-ssm-agent.amazon-ssm-agent.
[  OK  ] Started Service for snap a…on-ssm-agent.amazon-ssm-agent.
[  OK  ] Started containerd container runtime.
         Starting Docker Application Container Engine...
[  OK  ] Stopped Service for snap a…on-ssm-agent.amazon-ssm-agent.
[  OK  ] Started Service for snap a…on-ssm-agent.amazon-ssm-agent.
[  OK  ] Stopped Service for snap a…on-ssm-agent.amazon-ssm-agent.
[  OK  ] Started Service for snap a…on-ssm-agent.amazon-ssm-agent.
[  OK  ] Stopped Service for snap a…on-ssm-agent.amazon-ssm-agent.
[FAILED] **Failed** to start Service fo…on-ssm-agent.amazon-ssm-agent.
See 'systemctl status snap.amazon-ssm-a….amazon-ssm-agent.service' for details.
[  OK  ] Started Docker Application Container Engine.
[  OK  ] Reached target Multi-User System.
[  OK  ] Reached target Graphical Interface.
         Starting Update UTMP about System Runlevel Changes...
[  OK  ] Finished Update UTMP about System Runlevel Changes.


Ubuntu 20.04.6 LTS ip-***-**-*-** ttyS0
asked a year ago418 views
1 Answer
1

Hi, most issues with ssh come from either ip routing or improper sec groups.

I would recommend to start connecting with Instance Connect by following this guidance: https://repost.aws/knowledge-center/ec2-instance-connect-troubleshooting.

That should fix potential sec group issues

Then try ssh from your laptop: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesConnecting.html

profile pictureAWS
EXPERT
answered a year ago
  • Thank you for your response. I've checked both the IP routing and security group, but there were no problems. I have also reviewed the content mentioned in the link you shared. I tried to solve the issue by accessing the EC2 Serial Console, but I can't even set up the login password for the Serial Console as I can't connect to the Instance Console. Do you know of any other ways to log into the Serial Console?

    Please feel free to let me know if you need any additional information.

    Thank you.

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