Unable to connect to Ubuntu VM a few minutes after its booted successfully

Andrew Jensen | Xuridisa 0 Reputation points
2023-03-26T06:38:03.3233333+00:00

Restored a Ubuntu 22.04 LTS VM from Azure Backup. VM boots completely fine (as does the source/backed up VM). Able to log into the VM fine once started. But after a few minutes (approx 10 minutes) The VM becomes unresponsive.

VM still responds to ping requests. But cannot access VM via SSH, Apache non responsive, and SNMP monitoring reports server down.

In the Azure portal the Agent Status changes to ‘Not Ready’.

Tried re-restoring from the source VM again, and same symptoms.

Restart the VM and it’s fine again, but then a short time later goes offline again. 100% repeatable.

Anyone have nay ideas on this, it’s really odd.

Azure Virtual Machines
Azure Virtual Machines
An Azure service that is used to provision Windows and Linux virtual machines.
7,130 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Ronen Ariely 15,096 Reputation points
    2023-03-26T22:22:13.12+00:00

    Hi,

    VM still responds to ping requests.

    I will assume that the VM is still running.

    But cannot access VM via SSH, Apache non responsive, and SNMP monitoring reports server down.

    As first step, I would monitor what happens in the VM level. Monitor the vents of changing firewall, stopping of Apache and all you find as not available.

    In first glance following the information provided it seems like an internal issue and not host level issue (but with the information we have it's more guessing than conclusion or assumption)

    In the Azure portal the Agent Status changes to ‘Not Ready’.

    This says not a lot since it is possible be a result of what's you have internal which close the the services

    100% repeatable.

    It might sound confusing but this is a very good information for you. A consistent behaviour which you can reproduce means that you can monitor and examine and you (or another experts) should be able to find the solution in most cases.

    next step is monitoring....