azure agent not ready

Question

Hello,

We noticed for about 3 or 4 weeks a strange behaviour our VMs,

We've created a runbook in order to stop and start Vm during the night,

This runbook allow us to save Azure costs :)

And from time to time some VMs are in a state : agent azure not ready but working, only the networking is unavailable.

We must each time start over the Vms to recover them.

And the strange behaviour we've noticed, ecach time it's a new VM which is impacted and never one of those impacted before by this event : azure agent not ready.

is there some maintenance on azure actually ? or sth like that ?

we got nothing about that on our Health and Maintenance portal, and nothing on the windows event

thanks in advance

Regards

Louis

Answer 1

Hi @Da SILVA Louis

It is the best practice to use azure automation to Start/Stop VMs during off-hours. The feature provides a decentralized low-cost automation option for users who want to optimize their VM costs.

The Azure Virtual Machine (VM) Agent is a component installed by default on each Azure VM that is created from Azure marketplace. The agent is responsible for enabling communication between the Azure platform and the VM. Hence it is important to make sure, that the agent is up-to-date and running.

If you are seeing issues with VM guest agent state being Not Ready post a restart, this could be due to one of the below common reasons:

• The agent might have been corrupted, or the service might have been stopped as part of reboot and there is a delay in start during the restart of the VM
• The agent might be out of date.
• The agent might not have enough permissions on the VM.
• The agent might not have access to IP address 168.63.129.16.
• DHCP might not be enabled inside the guest VM.

Recommendations:

1. If the guest agent did not start and stays in a Not Ready state. You can check whether these services are running by examining Task Manager for the following processes (For windows) For linux, see

• WindowsAzureGuestAgent.exe: Azure VM Agent service
• WaAppAgent.exe: RD Agent service
• WindowsAzureTelemetryService.exe: Windows Azure Telemetry Service

2. Check whether auto-update is working
3. Check whether the VM can connect to the Fabric Controller
4. Advanced troubleshooting

Events for troubleshooting Azure VM Agent are recorded in the following log files:

• C:\WindowsAzure\Logs\WaAppAgent.log
• C:\WindowsAzure\Logs\TransparentInstaller.log

Hope this helps!

Please accept as answer and upvote if the above information is helpful for the benefit of the community.