This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(156.8, 9%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBE%3C/text%3E%3C/svg%3E)
Hi,
Follwing up on my last question: https://learn.microsoft.com/en-us/answers/questions/1690671/syslog-through-ama-connector-not-showing-in-the-co
I have now installed Arc, and the machine is showing up on Azure Arc.
The AMA is installed and is correctly sending heartbeats to Sentinel.
I have onboarded a couple of network devices to forward syslog towards the Azure Arc enabled server.
Verified with tcpdump that the devices is sending syslog to UDP 514.
Verified with tcpdump that rsyslog is sending the syslog to AMA localhost TCP 28330
But logs does still not show up in LA/Sentinel.
After some investigation, I discovered some warning logs in /var/opt/microsoft/azuremonitoragent/logmdsd.warn:
2024-06-04T11:22:53.3910500Z: [/__w/1/s/external/WindowsAgent/src/shared/mcsmanager/lib/src/Configuration.cpp:410,ParseDataSources]Data source syslog is not implemented ErrorCode:-2146171897
2024-06-04T11:22:53.4435500Z: [/__w/1/s/external/WindowsAgent/src/shared/mcsmanager/lib/src/Configuration.cpp:410,ParseDataSources]Data source syslog is not implemented ErrorCode:-2146171897
2024-06-04T11:22:53.4435940Z: [/__w/1/s/external/WindowsAgent/src/shared/mcsmanager/lib/src/Configuration.cpp:410,ParseDataSources]Data source syslog is not implemented ErrorCode:-2146171897
2024-06-04T13:18:08.4699950Z: [/__w/1/s/external/WindowsAgent/src/shared/mcsmanager/lib/src/Configuration.cpp:410,ParseDataSources]Data source syslog is not implemented ErrorCode:-2146171897
And local error message in syslog is throwing:
azuremonitor-coreagent.service: Scheduled restart job, restart counter is at 3733.
Stopped Azure Monitor Agent CoreAgent daemon (on systemd).
Started Azure Monitor Agent CoreAgent daemon (on systemd).
amacoreagent[109235]: The required instruction sets are not supported by the current CPU.
this message throws at every restart counter.
I have tried to lookup this error message, but haven't found anything useful.
I don't either find specific technical requirements
The AMA is running on:
Operating System: Ubuntu 20.04.6 LTS
Kernel: Linux 5.4.0-182-generic
Architecture: x86-64
Viritualized, 4 cores and 8 G RAM.
Any advice?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(217.60000000000002, 70%, 31%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGB%3C/text%3E%3C/svg%3E)
I have a similar situation with the AMA coreagent continuously dumping and reporting The required instruction sets are not supported by the current CPU:
OS: Ubuntu 22.04.4 LTS
Kernel: 5.15.0-112-generic
Architecture: x86-64
Virtualized, 2 cores, 1 GB RAM
I've also checked the Arc extensions on the host are up to date:
MDE.Linux: 1.0.3.17
LinuxOsUpdateExtension: 1.0.43.0
LinuxPatchExtension: 1.6.54
AzureMonitorLinuxAgent: 1.31.1
I have the same issue on a slightly newer OS. Every few seconds the Azure Monitor Agent CoreAgent daemon restarts:
Jun 14 11:07:35 hostname audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=azuremonitor-coreagent comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 14 11:07:35 hostname systemd[1]: Started Azure Monitor Agent CoreAgent daemon (on systemd).
Jun 14 11:07:35 hostname audit[897956]: ANOM_ABEND auid=4294967295 uid=0 gid=0 ses=4294967295 subj=unconfined pid=897956 comm="amacoreagent" exe="/opt/microsoft/azuremonitoragent/bin/amacoreagent" sig=6 res=1
Jun 14 11:07:35 hostname amacoreagent[897956]: The required instruction sets are not supported by the current CPU.
Jun 14 11:07:36 hostname audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=azuremonitor-coreagent comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Jun 14 11:07:36 hostname systemd[1]: azuremonitor-coreagent.service: Main process exited, code=dumped, status=6/ABRT
Jun 14 11:07:36 hostname systemd[1]: azuremonitor-coreagent.service: Failed with result 'core-dump'.
Jun 14 11:07:39 hostname systemd[1]: azuremonitor-coreagent.service: Scheduled restart job, restart counter is at 249.
The system info:
OS: Ubuntu 22.04.4 LTS
Kernel: 5.15.0-112-generic
Architecture: x86-64
CPU: 2
RAM: 1GB
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(246.4, 8%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKR%3C/text%3E%3C/svg%3E)
Same problem with
Ubuntu 20.04.6 LTS, Kernel: Linux 5.4.0-186-generic
Ubuntu 22.04.4 LTS, Kernel: Linux 5.15.0-112-generic
The problem is only with Azure Monitor Agent for Linux version >=1.30, version 1.24.2 works fine.
So uninstalling Monitor Agent and, installing version 1.24.2 + disabling Automatic Upgrade is a workaround.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(89.60000000000001, 13%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EDN%3C/text%3E%3C/svg%3E)
Same problem on fresh new 20.04.6 LTS (8Gb/2CPU/x86-64).
/var/opt/microsoft/azuremonitoragent/log/mdsd.warn:
2024-06-21T17:19:06.4568380Z: [/__w/1/s/external/WindowsAgent/src/shared/mcsmanager/lib/src/Configuration.cpp:410,ParseDataSources]Data source syslog is not implemented ErrorCode:-2146171897
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(44.800000000000004, 52%, 14%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMN%3C/text%3E%3C/svg%3E)
We're seeing the same problem on Debian VMs running in VMWare vSphere.
On systems running Debian 11, we were able to downgrade to version 1.26.1 of the AMA extension as a workaround.
However, 1.26.1 doesn't support Debian 12, leaving us with no path to upgrade to Debian 12 without breaking the AMA extension.
I have installed azcmagent version 1.24.02147.540, and it worked for some time (logs collected), but after few minutes it stops with an old error:
2024-06-25T17:58:21.4440040Z: [/__w/1/s/external/WindowsAgent/src/shared/mcsmanager/lib/src/Configuration.cpp:409,ParseDataSources]Data source syslog is not implemented ErrorCode:-2146171897
Basically, the Linux monitoring is completely broken at the moment.
I found out that on VMware the VM compatibility setting is causing the problem.
When the compatibility setting is "ESXi 5.5 and later" amacoreagent crashes with the message "The required instruction sets are not supported by the current CPU".
VM Compatibility Upgrade resolves the issue.
This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Comments have been turned off. Learn more
On VMware problem can be solved by upgrading "VM Compatibility".