Azure VM agent status not ready.

Question

Azure VM agent status not ready.

Gikandi, Eric E (ER T0) 10

We're not able to ping or ssh to a linux vm. None of the recommended troubleshooting methods are working. I have tried redeploying VM too

User's image

kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2023-03-24T18:36:12.0266667+00:00

Hello, @Gikandi, Eric E (ER T0) !

Usually a last resort after clicking on the troubleshooting link and following all of the troubleshooting steps would be to redeploy the VM. This would reset all of the setup and configuration values and rule out any hardware anomalies you encountered.

While I might try one more redeploy just to be certain, it looks like there may be an issue with a value at creation, either in the setup configuration or in the image that was used. Can you provide more information on how the VM was initially deployed and what image/VM size you are using?
kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2023-03-27T16:04:50.9366667+00:00

Hello, @Gikandi, Eric E (ER T0) !

Are you able to provide more information about how the VM was initially deployed and what image/VM size you are using? I can provide an email if you would like to follow up directly. We'll need the additional information to continue to troubleshoot this.
Gikandi, Eric E (ER T0) 10 Reputation points

2023-03-28T06:54:35.8466667+00:00

Hello @kobulloc-MSFT ,

The VM was created normally on azure. I've cloned the OS disc and created a VM out of it but we're still experiencing the same VM agent error.
kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2023-03-28T21:22:40.98+00:00

Hello, @Gikandi, Eric E (ER T0) !

When you say that the VM was created normally on Azure, do you mean that you used an Azure marketplace image? It sounds like we may need to look at the VM image to determine what is going on.
kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2023-03-28T21:24:48.6366667+00:00

Hello, @Gikandi, Eric E (ER T0) !

To further troubleshoot this issue, we are going to take a closer look at your resources.

1 answer

Your answer

kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2023-03-24T18:36:12.0266667+00:00

Hello, @Gikandi, Eric E (ER T0) !

Usually a last resort after clicking on the troubleshooting link and following all of the troubleshooting steps would be to redeploy the VM. This would reset all of the setup and configuration values and rule out any hardware anomalies you encountered.

While I might try one more redeploy just to be certain, it looks like there may be an issue with a value at creation, either in the setup configuration or in the image that was used. Can you provide more information on how the VM was initially deployed and what image/VM size you are using?
kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2023-03-27T16:04:50.9366667+00:00

Hello, @Gikandi, Eric E (ER T0) !

Are you able to provide more information about how the VM was initially deployed and what image/VM size you are using? I can provide an email if you would like to follow up directly. We'll need the additional information to continue to troubleshoot this.
Gikandi, Eric E (ER T0) 10 Reputation points

2023-03-28T06:54:35.8466667+00:00

Hello @kobulloc-MSFT ,

The VM was created normally on azure. I've cloned the OS disc and created a VM out of it but we're still experiencing the same VM agent error.
kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2023-03-28T21:22:40.98+00:00

Hello, @Gikandi, Eric E (ER T0) !

When you say that the VM was created normally on Azure, do you mean that you used an Azure marketplace image? It sounds like we may need to look at the VM image to determine what is going on.
kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2023-03-28T21:24:48.6366667+00:00

Hello, @Gikandi, Eric E (ER T0) !

To further troubleshoot this issue, we are going to take a closer look at your resources.

Answer 1

Hello, @Gikandi, Eric E (ER T0) !

It sounds like in your scenario, we'll need to do some additional troubleshooting. Once we receive your email, we can take a closer look at your VM.

What should I do if my Azure virtual machine agent status is not ready?

Go to your virtual machine and check the status in VM > Settings > Properties > Agent status. If the status of the agent is not ready, then you can try the following troubleshooting steps:

Confirm that the Azure VM Agent service is installed. If Azure VM Agent is installed on the VM, the package will be saved in the following location: C:\windows\OEM\GuestAgent\VMAgentPackage.zip or you can run the following PowerShell command to check whether VM Agent has been deployed to the VM: Get-AzVM -ResourceGroupName "RGNAME" -Name "VMNAME" -DisplayHint expand
Check whether auto-update is working. The Azure VM Agent has an auto-update feature. It will automatically check for new updates and install them. If the auto-update feature doesn't work correctly, try uninstalling and installing the Azure VM Agent.
Check whether the VM can connect to the Fabric Controller. Use a tool such as PsPing to test whether the VM can connect to 168.63.129.16 on ports 80 and 32526. If the VM doesn’t connect as expected, check whether outbound communication over ports 80 and 32526 is open in your local firewall on the VM. If this IP address is blocked, VM Agent may display unexpected behavior in a variety of scenarios.
You can also try some advanced troubleshooting steps, including checking for specific version numbers, agent states, and error codes.
As a last resort, you can redeploy your VM to reset all of the setup and configuration values and rule out any hardware anomalies you encountered.

If none of that works, let us know so we can take a closer look at your VM and do some additional troubleshooting.

Panos Tsapralis 0 Reputation points

2024-11-03T20:15:05.9133333+00:00

This answer refers to Windows virtual machines while the issue is related to Linux.
kobulloc-MSFT 26,846 Reputation points Microsoft Employee Moderator

2024-12-03T23:45:31.8633333+00:00

Thank you for the correction! This would be the appropriate VM agent troubleshooting guide for Linux:

https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/linux-azure-guest-agent

Share via

Azure VM agent status not ready.

1 answer

Your answer