Unable to access EC2 after upgrade from Ubuntu 18 to 20

Question

I recently upgraded and EC2 instance from Ubuntu 18 to 20.

After the upgrade was complete the server performed a reboot. I have not bee able to connect to the server via SSH or web site since then.

I double checked the security groups, they have not changed.

I have executed an image screen shot of the server and there are no errors.

Unfortunately I did not create a non ssh user/pass so I can't access the server via the serial console. 
However I do see via the serial console the server appears to start up, but I know it's not starting all the way up because there are some cron jobs on the server that would be making some external server to server connections and those are not happening either.

Is there any way that I or perhaps AWS support and get a terminal up on this server to see what has caused the hang up and get it up and running again?

Riku_Kobayashi · Answer

Hello.

Have you tried connecting with Systems Manager Session Manager instead of SSH?  
If SSM Agent is installed on EC2 and the appropriate IAM role is set, you can connect.  
https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager.html

Although it may not be possible to obtain this information depending on the instance type you are using with EC2, I also recommend checking the system log.  
https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/troubleshoot-unreachable-instance.html#instance-console-console-output

Garre Sandeep · Answer

Hi jeff
Check these troubleshoot to resolve the issue:

The issue is likely related to the upgrade from Ubuntu 18.04 to 20.04 causing the EC2 instance to hang during boot. Here's how to troubleshoot and potentially fix it:

Check boot logs: While you can't access the server directly, you can leverage AWS serial console access (even without a configured user). This will display boot logs which might indicate the reason for the hang AWS Troubleshoot Linux instances with failed status checks

Identify the culprit: Look for errors or warnings in the boot logs around the time the instance hangs. This might point you towards a specific service or driver causing the issue.

Recovery Instance: If the logs aren't clear, consider launching a recovery instance. Attach the original instance's root disk to the recovery instance and access it as a secondary volume. This allows you to diagnose the issue from a functional system.

AWS Support: If these steps don't resolve the issue, consider contacting AWS support. They have deeper access to instance logs and can provide further guidance.

https://docs.aws.amazon.com/ec2/

https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstances.html

Unable to access EC2 after upgrade from Ubuntu 18 to 20

Add your answer

Relevant content