Virtual Machine Agent Status Not Ready

Question

Virtual Machine Agent Status Not Ready

sachidananda kini 6

Dear All,
Please help us , Now Status is Running Mode But We are Unable To connect our server and Ping Also No response but in azure level we checked and we got that error message Agent status is Not ready.
Please help us , How to solve this issue

Manu Philip 20,206 Reputation points MVP Volunteer Moderator

2021-12-16T08:30:20.137+00:00

Are you saying that VM Agent is running now and VM is not accessible? The description is bit confusing
sachidananda kini 6 Reputation points

2021-12-16T08:39:15.33+00:00

Hi Manu,
Server Is Started but we are unable to connect with our server. Due to that error message agent status is not ready.
sachidananda kini 6 Reputation points

2021-12-16T08:42:16.26+00:00

VM is Not accessible
Manu Philip 20,206 Reputation points MVP Volunteer Moderator

2021-12-16T08:45:07.09+00:00

Are you not able to connect through SSH? Hope, the NSG rule is set for port 22
sachidananda kini 6 Reputation points

2021-12-16T08:50:23.04+00:00

Yes We Tried to connect through putty SSH , Port is 22 only
Daniel Hajsadr 0 Reputation points

2023-06-27T12:04:42.7633333+00:00

Is there a way to monitor and create alerts for when VMs have Agent Status as "Not Ready"?
Tushar Kumar 3,371 Reputation points MVP

2023-06-27T12:58:26.0633333+00:00
Hi Daniel Hajsadr,

At first we need to understand the purpose of VM agent :

The Azure VM Agent manages interactions between an Azure VM and the Azure fabric controller. The agent is responsible for many functional aspects of deploying and managing Azure VMs, including running VM extensions. - likes of things that we do to reset password/run command etc.

This has nothing to do with your VM being not responsive it's possible it is showing up because your VM is not responding.

We are Unable To connect our server and Ping Also :

This issue can occur because of multiple issues :

Networking issue : Check your NSG and firewall setup 1st for any signs of traffic being blocked.

Check VM Status : Check boot diagnostic of your VM if it is showing any errors on loading the VM

If you see any anomly try Restart/Redeploy/troubleshoot on VM level. Once you have your VM responsive post that you can deal with the Agent not being ready issue. I can see below we have good troubleshooting links.

5 answers

Your answer

Manu Philip 20,206 Reputation points MVP Volunteer Moderator

2021-12-16T08:30:20.137+00:00

Are you saying that VM Agent is running now and VM is not accessible? The description is bit confusing
sachidananda kini 6 Reputation points

2021-12-16T08:39:15.33+00:00

Hi Manu,
Server Is Started but we are unable to connect with our server. Due to that error message agent status is not ready.
sachidananda kini 6 Reputation points

2021-12-16T08:42:16.26+00:00

VM is Not accessible
Manu Philip 20,206 Reputation points MVP Volunteer Moderator

2021-12-16T08:45:07.09+00:00

Are you not able to connect through SSH? Hope, the NSG rule is set for port 22
sachidananda kini 6 Reputation points

2021-12-16T08:50:23.04+00:00

Yes We Tried to connect through putty SSH , Port is 22 only
Daniel Hajsadr 0 Reputation points

2023-06-27T12:04:42.7633333+00:00

Is there a way to monitor and create alerts for when VMs have Agent Status as "Not Ready"?
Tushar Kumar 3,371 Reputation points MVP

2023-06-27T12:58:26.0633333+00:00

Hi Daniel Hajsadr,

At first we need to understand the purpose of VM agent :

The Azure VM Agent manages interactions between an Azure VM and the Azure fabric controller. The agent is responsible for many functional aspects of deploying and managing Azure VMs, including running VM extensions. - likes of things that we do to reset password/run command etc.

This has nothing to do with your VM being not responsive it's possible it is showing up because your VM is not responding.

We are Unable To connect our server and Ping Also :

This issue can occur because of multiple issues :

Networking issue : Check your NSG and firewall setup 1st for any signs of traffic being blocked.

Check VM Status : Check boot diagnostic of your VM if it is showing any errors on loading the VM

If you see any anomly try Restart/Redeploy/troubleshoot on VM level. Once you have your VM responsive post that you can deal with the Agent not being ready issue. I can see below we have good troubleshooting links.

Answer 1

Manu Philip 20,206 MVP Volunteer Moderator

From Azure Portal, you can try an SSH repair. Please refer the documentation here: troubleshoot-ssh-connection

Try Resetting the SSH (Reset configuration only)

bluetata 1 Reputation point

2022-08-10T08:10:45.677+00:00

I encountered the problem twice, and one of them work well after I used your solution

Answer 2

As per this issue,

The closest thing I have been able to find is the following doc:

https://learn.microsoft.com/en-us/azure/backup/backup-azure-troubleshoot-vm-backup-fails-snapshot-timeout#the-agent-installed-in-the-vm-but-unresponsive-for-windows-vms

Essentially, if the agent is not in a ready state, it is usually due to some corruption of the agent which can be resolved by simply manually reinstalling the agent. You can find the steps to do that here:

https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/agent-windows#manual-installation

If it is not working, you should reinstall it. If it is still not working after that, there is usually something wrong with the VM image itself which would require support to look into further.

Also, please share if your VM was deployed from a specialized image. When deploying a VM from image, a manual installation is required for the Guest Agent as described here: Azure Virtual Machine Agent Overview - Azure Virtual Machines | Microsoft Learn. Is that the process that was used for this Guest Agent's installation?

For a Windows VM, the Agent Installer should take care of everything as long as the prerequisites listed here: https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/agent-windows#prerequisites are followed.

Hope that helps.

Answer 3

Frank Röder 1

We see this occationally. We just stop and start the VM and it is working again. This is easy for us, as all AVD's is dedicated (not multi-session) so everyone can do this for their own "VM" via the Azure APP. The irritating part is though why this is happening that often (maybe 3 times pr. week for different AVD's and we have 75).

Mateo Fey 1 Reputation point

2022-03-10T15:38:33.547+00:00

Frank, my organization faces the exact same issue that you're describing. Just curious- have you found any type of solution to this?

The closest thing I found was to configure automated tasks to power off and on the VM on a weekly basis.
Lothar Schock 1 Reputation point

2022-10-04T07:37:43.303+00:00

Hi,

we have the same issue, Is there anay solution beside stopping and restarting the vm?

Answer 4

James 1

Just experienced the same issue, VM became unresponsive, and our production website was down for some hours.

A restart resolved the issue, but we are keen to understand the cause behind this and find a working solution. Can an automatic restart be scheduled should this event occur?

Answer 5

Renjan George 0

is this issue have any solution?

same issue i am facing

Share via

Virtual Machine Agent Status Not Ready

5 answers

Your answer