How to fix the issue Virtual Machine Agent Status Not Ready Isuue

Question

How to fix the issue Virtual Machine Agent Status Not Ready Isuue

Mithila Lishan 121

Recently, I've been encountering an issue when starting my Linux machine. After powering it on, I receive the following error, and it takes around 10–20 minutes before I can successfully log in to the server. During this time, I’ve checked the activity logs and found no activities being initiated after the virtual machine starts. This issue has only started occurring in the past week. I'm trying to understand what's causing it.

User's image

can some one advice me, how can i avoid this issue and what i can do to find the issue ?

Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-23T00:10:20+00:00

Hi Mithila Lishan,
Are you facing this issue only one VM or multiple VM and are you able to connect through SSH once the 10-20 minutes window is completed. Is there any messages displaying that the agent is in ready state or the VM agent is not ready message is just removed?
In the mean while you can check the service status of the Azure Linux Agent to make sure it's running, and make sure auto-update is enabled
and for more troubleshooting steps you can refer
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/linux-azure-guest-agent

Feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-23T22:12:00.35+00:00

Hi Mithila Lishan,
Just checking to if there are any updated on your issue
Feel free to reach out if you have any further queries.
Mithila Lishan 121 Reputation points

2025-04-24T10:16:29.4066667+00:00

Dear @Vamsi Ram Annepu ,

Thank you for addressing my questions. I’ve noticed this issue occurring only on one VM. During the time the issue appears, I'm unable to access the VM via SSH Completely Unresponsive. Even after restarting the VM, the reboot process takes over 7 minutes to complete—whereas under normal conditions, it typically restarts within seconds. However, I couldn’t find any suspicious or relevant entries in the activity logs that could explain the behavior.

At the time of issue occurred, i cannot log in to the VM then how could I troubleshoot the issue?
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-24T18:18:43.0266667+00:00

Hi Mithila Lishan,
It appears that the VM is of the standard B1s (1Gb) size which can go into agent not ready state when the traffic is high, you can try changing the size of the VM which can resolve the issue.
Here is a document on how to resize the VM
https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/resize-vm?tabs=portal

Feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.
Mithila Lishan 121 Reputation points

2025-04-25T03:25:09.7433333+00:00

Dear @Vamsi Ram Annepu ,

if this issue occurred frequently, I could resize the Virtual machine and check issue is fixed,

If the issue occurred due to high traffic or insufficient memory, there should be evidence to support that. Without concrete data or logs indicating that resource limitations caused the "agent not ready" issue, how can we be certain that this is the root cause?
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-26T00:48:01.9633333+00:00

Hi Mithila Lishan,
When there is high traffic on a VM with low size it might behave in this way hence to rule out the issue the suggestion of increasing the size was given.

Feel free to reach out if you have any further queries.
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-28T23:13:18.6+00:00

Hi Mithila Lishan,
Just checking in to see if there is any update in your situation.
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-29T17:24:53.9766667+00:00

Hi Mithila Lishan,
Just checking in to see if you need any further assistance and feel free to reach out if you have any further queries.

1 answer

Your answer

Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-23T00:10:20+00:00

Hi Mithila Lishan,
Are you facing this issue only one VM or multiple VM and are you able to connect through SSH once the 10-20 minutes window is completed. Is there any messages displaying that the agent is in ready state or the VM agent is not ready message is just removed?
In the mean while you can check the service status of the Azure Linux Agent to make sure it's running, and make sure auto-update is enabled
and for more troubleshooting steps you can refer
https://learn.microsoft.com/en-us/troubleshoot/azure/virtual-machines/linux/linux-azure-guest-agent

Feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-23T22:12:00.35+00:00

Hi Mithila Lishan,
Just checking to if there are any updated on your issue
Feel free to reach out if you have any further queries.
Mithila Lishan 121 Reputation points

2025-04-24T10:16:29.4066667+00:00

Dear @Vamsi Ram Annepu ,

Thank you for addressing my questions. I’ve noticed this issue occurring only on one VM. During the time the issue appears, I'm unable to access the VM via SSH Completely Unresponsive. Even after restarting the VM, the reboot process takes over 7 minutes to complete—whereas under normal conditions, it typically restarts within seconds. However, I couldn’t find any suspicious or relevant entries in the activity logs that could explain the behavior.

At the time of issue occurred, i cannot log in to the VM then how could I troubleshoot the issue?
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-24T18:18:43.0266667+00:00

Hi Mithila Lishan,
It appears that the VM is of the standard B1s (1Gb) size which can go into agent not ready state when the traffic is high, you can try changing the size of the VM which can resolve the issue.
Here is a document on how to resize the VM
https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/resize-vm?tabs=portal

Feel free to reach out if you have any further queries.

If you found the information useful, please click "Upvote" on the post to let us know.
Mithila Lishan 121 Reputation points

2025-04-25T03:25:09.7433333+00:00

Dear @Vamsi Ram Annepu ,

if this issue occurred frequently, I could resize the Virtual machine and check issue is fixed,

If the issue occurred due to high traffic or insufficient memory, there should be evidence to support that. Without concrete data or logs indicating that resource limitations caused the "agent not ready" issue, how can we be certain that this is the root cause?
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-26T00:48:01.9633333+00:00

Hi Mithila Lishan,
When there is high traffic on a VM with low size it might behave in this way hence to rule out the issue the suggestion of increasing the size was given.

Feel free to reach out if you have any further queries.
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-28T23:13:18.6+00:00

Hi Mithila Lishan,
Just checking in to see if there is any update in your situation.
Vamsi Ram Annepu 740 Reputation points Microsoft External Staff Moderator

2025-04-29T17:24:53.9766667+00:00

Hi Mithila Lishan,
Just checking in to see if you need any further assistance and feel free to reach out if you have any further queries.

Answer 1

Divyesh Govaerdhanan 4,435

Hello,

Welcome to Microsoft Q&A,

Essentially, if the agent is not in a ready state, it is usually due to some corruption of the agent.

Please consider the following troubleshooting steps:

Try stopping and then starting the virtual machine (VM). Stopping the VM will deallocate it, which is different from a reboot, and this action often resolves the issue.
Verify whether the VM agent is running on the virtual machine. You can do this by logging into the VM and checking if the Windows Azure Guest Agent service is active. If it is not running, please attempt to start the service manually.
If necessary, you can uninstall and then reinstall the VM agent.

For more detailed guidance, please refer to the following troubleshooting document: Azure Virtual Machines Windows Azure Guest Agent.

Please Upvote and accept the answer if it helps!!

Mithila Lishan 121 Reputation points

2025-04-25T03:52:10.5766667+00:00
Thank you so much for attending my questions

Yes, I restarted, after that stop start, but it Tooks more than 20 minutes to become responsive, because of this non-production VM this is not a problem, if this happened to production VM what will happen? 20 minutes

at the time issue occurred, I cannot log in to the VM then how can i perform the action 2 steps ?

Share via

How to fix the issue Virtual Machine Agent Status Not Ready Isuue

1 answer

Your answer