Azure Monitor Agent Troubleshooting Tool Reports Subcomponent Installation Errors

Question

Azure Monitor Agent Troubleshooting Tool Reports Subcomponent Installation Errors

Manjunadh Atcha 25

Hi Azure Support,

I'm encountering an issue with the Azure Monitor Agent (AMA) on my Linux VM (ARM Architecture Machine). When I run the AMA troubleshooting tool using the commandsudo sh ama_troubleshooter.sh -A, it reports the following error:

ERROR FOUND: Subcomponents(s) agentlauncher, amacoreagent not installed correctly.

Despite the binaries like mdsd, fluent-bit, and MetricsExtension being present under /opt/microsoft/azuremonitoragent/bin/, the tool still flags the subcomponents as not installed correctly.

ls -l /opt/microsoft/azuremonitoragent/bin/

total 79076

-rwxr-xr-x 1 root root 20125392 Apr 30 15:57 MetricsExtension

-rwxr-xr-x 1 root root 13638968 Apr 30 15:52 fluent-bit

drwxr-xr-x 2 root root 4096 Apr 30 15:52 kqlextension

-rwxr-xr-x 1 root root 25410456 Apr 30 15:52 mdsd

-rwxr-xr-x 1 root root 4153424 Apr 30 15:52 mdsdmgr

-rwxr-xr-x 1 root root 7245944 Apr 21 23:35 mdsdmgrctl

-rwxr-xr-x 1 root root 10380632 Apr 21 23:35 telegraf

Could you please assist in understanding:

Why this error might be occurring?

Whether any remediation steps are recommended beyond restarting AMA?

What to do to install agentlauncher and amacoreagent?
suggest how to resolve it?

Accepted answer

1 additional answer

Your answer

Answer 1

Ashok Gandhi Kotnana 6,675 Microsoft External Staff

Hi @Manjunadh Atcha

In certain Linux setups, especially with newer versions or Arc-connected machines, the Azure Monitor Agent (AMA) no longer relies on the agentlauncher or amacoreagent components. These components were more common in older deployments or on Azure VMs using the now-deprecated Log Analytics agent. The current AMA architecture is more modular.

For ARM-based VMs:

The AMA does not yet fully support ARM-based systems with all features and components (such as agentlauncher and amacoreagent). On ARM systems, other components like fluent-bit, mdsd, and others may still be functional, but agentlauncher and amacoreagent will not be installed.

User's image

For x64-based VMs:

The full set of AMA components, including agentlauncher and amacoreagent, is properly installed and fully functional.

User's image

If you're using AMA solely for collecting metrics and logs, it may not deploy agentlauncher or amacoreagent, and will instead rely on components such as:

mdsd (Azure Monitoring Diagnostic Service) telegraf (metrics collector) fluent-bit (log forwarder)

To verify that AMA is functioning correctly, even without the missing binaries, check for active AMA-related services by running:

 sudo systemctl list-units | grep -iE 'azuremonitor|mdsd|telegraf|fluent'

To summarize, ARM-based architecture does not fully support agentlauncher and amacoreagent in the Azure Monitor Agent (AMA), while x64 machines have full support for these components. If full monitoring functionality is required on ARM-based systems, consider using the deprecated Log Analytics Agent.

Please let me know if you face any challenge here, I can help you to resolve this issue further

Provide your valuable Comments.

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Manjunadh Atcha 25 Reputation points

2025-05-05T11:11:42.59+00:00

Hi Ashok,

Thanks for the detailed explanation.

Could you please try running the AMA troubleshooter yourself using the steps from this link?
https://learn.microsoft.com/en-us/azure/azure-monitor/agents/troubleshooter-ama-linux?tabs=redhat%2CGenerateLogs#run-the-troubleshooter

You’ll likely encounter the same issue I did on ARM-based machines.

After comparing an AMD (x64) VM with an ARM VM, I found that fluentd is not running on the ARM setup. This led me to discover that agentlauncher and amacoreagent are critical components in certain configurations. Their absence on ARM might explain the incomplete functionality.

Let me know your thoughts.
Ashok Gandhi Kotnana 6,675 Reputation points Microsoft External Staff

2025-05-05T12:59:10.2833333+00:00
Hi @Manjunadh Atcha ,

We’ve followed the troubleshooting steps using the link provided and were able to successfully generate logs on both machines. Please refer to the attached screenshots for confirmation.

To ensure Fluent Bit and other components are functioning correctly, please verify that the latest AMA version and Python are installed.

You can also validate the status of all related AMA services by running:

sudo systemctl list-units | grep -iE 'azuremonitor|mdsd|telegraf|fluent'

To confirm Fluent Bit is running:

ps aux | grep [f]luent-bit

Additionally, check for any relevant logs under the following directories:

Please let me know if you face any challenge here, I can help you to resolve this issue further

Provide your valuable Comments.

Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.
Manjunadh Atcha 25 Reputation points

2025-05-05T13:56:32.57+00:00
Hi,

Ubuntu version: 20.04
Python Version: 3.8.10

Machine Type: Standard_D4pds_v5

ps aux | grep [f]luent-bit => Empty output

sudo systemctl list-units | grep -iE 'azuremonitor|mdsd|telegraf|fluent'

enable_acf07141-b02a-4f30-9f62-a2e34e488124.scope loaded active running /var/lib/waagent/Microsoft.Azure.Monitor.AzureMonitorLinuxAgent-1.35.1/./shim.sh -enable

azuremonitoragent.service loaded active running Azure Monitor Agent daemon (on systemd)

metrics-sourcer.service loaded active running Custom Modified Telegraf service for Linux Agent metrics sourcing

azure-vmextensions-Microsoft.Azure.Monitor.AzureMonitorLinuxAgent.slice loaded active active azure-vmextensions-Microsoft.Azure.Monitor.AzureMonitorLinuxAgent.slice

When Ran

sudo sh ama_troubleshooter.sh -A
Ashok Gandhi Kotnana 6,675 Reputation points Microsoft External Staff

2025-05-05T17:09:01.8133333+00:00

Hi @Manjunadh Atcha ,

I have reached out to you in a private message

Answer 2

Hi ,

Thanks for reaching out to Microsoft Q&A.

Why this error might be occurring?

ARM Architecture: Official AMA support for ARM-based Linux VMs is still limited or not fully optimized. Some components may not install or function correctly on ARM.
Partial Installation: Even if binaries are present, the agentlauncher and amacoreagent might not be registered properly as services or may be missing dependencies.
Permission Issues: The tool may not have enough privilege to check service state or file ownerships.
Corrupted Installation: If the install was interrupted or used the wrong package type (x86 on ARM), the verification may fail.
Missing systemd service: agentlauncher usually runs as a systemd service; if it is not running or misconfigured, the tool may flag it.

Steps to Troubleshoot and Remediate:

A. Verify Service Status

Check whether the two main components are running or even installed. If the services do not exist or are inactive/failed, that is a clear sign of a broken installation.

systemctl status azuremonitoragent systemctl status agentlauncher

B. Check for logs

Inspect logs to see what failed. Look for errors around startup, missing files, or architecture mismatches.

journalctl -u azuremonitoragent journalctl -u agentlauncher cat /var/opt/microsoft/azuremonitoragent/log/agentlauncher.log

C> Reinstall Azure Monitor Agent (clean install)

Uninstall and reinstall the AMA using ARM-compatible packages

Go to official Microsoft AMA GitHub Releases or use the Azure CLI to install AMA only if it supports ARM officially.

If not supported, you will need to wait for official support or use Log Analytics agent (deprecated) as a workaround.

D. Manual Verification

Ensure the following are in place:

agentlauncher binary should exist: /opt/microsoft/azuremonitoragent/bin/agentlauncher

amacoreagent should be in: /opt/microsoft/azuremonitoragent/bin/amacoreagent

Both should be referenced by systemd unit files in /etc/systemd/system/.

If they are missing:

Try re-installing from a proper AMA ARM64-compatible bundle. If Microsoft does not yet provide an ARM64 AMA package, consider opening a GitHub issue or contacting Microsoft support.
Please feel free to click the 'Upvote' (Thumbs-up) button and 'Accept as Answer'. This helps the community by allowing others with similar queries to easily find the solution.

Srinivasa Reddy Jaggavarapu 710 Reputation points Microsoft External Staff

2025-05-02T13:35:29.3533333+00:00

Hi Manjunadh Atcha,

Just checking in to see if the below answer provided by @Vinodh247 helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Manjunadh Atcha 25 Reputation points

2025-05-05T11:10:32.24+00:00

Hi,

Thank you for checking in. Unfortunately, the answer provided does not resolve the issue I'm facing. The problem still persists specifically on ARM-based VMs, and the suggestions didn’t address the missing components or their impact on the AMA's functionality.
Ashok Gandhi Kotnana 6,675 Reputation points Microsoft External Staff

2025-05-06T08:45:15.1366667+00:00

Hi @Manjunadh Atcha

Thank you for accepting the changes as discussed over the call. Instead of using ARM, please proceed with the 64-bit version.

Additionally, a similar issue has been reported by another customer. We’ve escalated the matter further and will keep you updated once we have a resolution.

From our observations, the ARM version appears to be causing issues for a few customers.

Thank you for your understanding.

Share via

Azure Monitor Agent Troubleshooting Tool Reports Subcomponent Installation Errors

1 additional answer

Your answer