Azure LInux VM and extensions in provisioning failed state

Question

I have some questions with which i need help with : I have a linux VM and on that linux Vm i am configuring disaster recovery . What i find is that we fail at installing Mobility service and preparing target . And in the extensions blade for the VM i find is all the below extensions are in failed state .
Microsoft.Azure.Diagnostics.LinuxDiagnostic
Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux
Microsoft.Azure.Recoveryservices.Siterecovery.Linux
Microsoft.Azure.Recoveryservices.Siterecovery.LinuxRhel6

My questions are below :
1)If i understand it correct walinuxagent is responsible for getting the above extensions/package from internet and once the package is extracted and installed we basically then call Extension.sh to enable the extension. Am i correct on this ?
2)If the extension is in provisioning failed state can we look at the below log to understand why it is in failed state ?
/var/log/azure/Microsoft.Azure.Diagnostics.LinuxDiagnostic/extension.log

In the waagent.log i see the below : Does this mean that enable operation failed for some reason. Will extension.log help us in this case ?
[Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.131] cwd is /var/lib/waagent/Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.131
[Microsoft.Azure.Diagnostics.LinuxDiagnostic-3.0.131] Change log file to /var/log/azure/Microsoft.Azure.Diagnostics.LinuxDiagnostic/extension.log
ERROR ExtHandler ExtHandler Event: name=Microsoft.Azure.Diagnostics.LinuxDiagnostic, op=Enable, message=abcdbcnhgetip[[asdnnasdapfnafpsdfnapfnsfpnfspfnapfnafaf

In what all troubleshooting scenarios we have to use extension.log ?

3)Should i first go ahead and un-install Azure VM linux agent and install it back ?

In the error message where it fails installing mobility service It gives me the below error code

Protection failed because GRUB device doesn't exist (error code 151124)https://learn.microsoft.com/en-us/azure/site-recovery/azure-to-azure-troubleshoot-errors

Need help with this . Can some one help me please ?

Answer 1

@kumar kaushal
1- Yes, WALinuxAgent calls install/enable to install & enable the extension
2- Yes, extensions logs is the starting point. https://learn.microsoft.com/en-us/azure/virtual-machines/extensions/troubleshoot
You can usually decode the message with something like echo "<error_message>" | base64 -d | pigz -d
But when you see all extensions in failed state, then maybe you can look at the waagent.log to see if it’s working fine, or if it’s the one reporting issues. If it’s not working, then it can’t report right status for extensions.
https://learn.microsoft.com/en-us/azure/virtual-machines/troubleshooting/linux-azure-guest-agent
3- I’d refrain from uninstalling WALinuxAgent, especially if you’re trying to do that manually.
Who built that VM? Is it coming from Marketplace? Or a custom image? Which version of the Linux Agent?

You can open a Technical Support and our support professionals will help you.

----------------------------------------------------------------------------------------------------------------------

If the response helped, do "Accept Answer" and up-vote it

Answer 2

@SadiqhAhmed-MSFT .. Thanks for your response . I have looked at the extension.log for OMS agent and found the below

error Error resolving host during the onboarding request. Check the correctness of the workspace ID and the internet connectivity, or add a proxy.
ERROR:The agent could not connect to the Microsoft Operations Management Suite service. Please check that the system either has Internet access, or that a valid HTTP proxy has been configured for the agent. Please also check the correctness of the workspace ID.
ERROR:[Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.13.33] The agent could not connect to the Microsoft Operations Management Suite service. Please check that the system either has Internet access, or that a valid HTTP proxy has been configured for the agent. Please also check the correctness of the workspace ID.
[Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.13.33] Enable,failed,55,The agent could not connect to the Microsoft Operations Management Suite service. Please check that the system either has Internet access, or that a valid HTTP proxy has been configured for the agent. Please also check the correctness of the workspace ID.

Now i do see that i have a proxy configured on the machine and i found that by using the command echo $http_proxy but if i look at the waagent.conf file i don't see any proxy being configured .

My question here is :
When i have not configured any proxy settings for the waagent.conf file itself and on the server itself i have a configured a proxy , So when i am going to install any extension is that waagent will fall back to actual proxy that is configured on the server ?

This looks to me that i am not able to connect to the outside world from the VM Itself . Any pointers as to how should i proceed from here ?

Answer 3

Hi,
please have a look here https://github.com/microsoft/OMS-Agent-for-Linux/blob/master/docs/OMS-Agent-for-Linux.md#configuring-the-agent-for-use-with-an-http-proxy-server on how to configure the OMS Agent to work with a proxy.

proxyconf="https://proxyuser:proxypassword@proxyserver01:8080"
sudo echo $proxyconf >>/etc/opt/microsoft/omsagent/proxy.conf
sudo chown omsagent:omiusers /etc/opt/microsoft/omsagent/proxy.conf
sudo chmod 600 /etc/opt/microsoft/omsagent/proxy.conf
sudo /opt/microsoft/omsagent/bin/service_control restart