Linux OMS agent - Two successive configuration applications from OMS Settings failed

[keymonster90]

Hi everyone.

I keep getting entries from a Linux into my log analytics workspace with the following:
Two successive configuration applications from OMS Settings failed – please report issue to github.com/Microsoft/PowerShell-DSC-for-Linux/issues

I do get heartbeat from this host, but not custom logs from /var/log/remote/* and /var/log/remote/*.txt. I have python 2 and 3 installed on this host and tried to purge and re-install the agent a couple of times according to the following article - https://docs.microsoft.com/en-us/azure/azure-monitor/agents/agent-linux-troubleshoot.

The only error I got while running the troubleshooter (sudo /opt/microsoft/omsagent/bin/troubleshooter) is

Checking if all files installed correctly (may take some time)...
WARNING(S) FOUND.

[anthelmintics]

We are also seeing this across our Linux machines, both Azure and non-Azure VMs in two separate LGA instances. Same behavior, heartbeats but no data except the error message:

OperationStatus
Warning

Detail
Two successive configuration applications from OMS Settings failed – please report issue to github.com/Microsoft/PowerShell-DSC-for-Linux/issues

[ghost]

Exactly the same here. Receiving heartbeats just fine, but no data whatsoever except for the error message. The troubleshooting command on the machine running the agent also provides no clue as to why it's not working.

[AkosBatorfi]

Getting this too. I have 2 linux VMs in Germany West Central that are in Azure Automation account with updates. Those machines keep saying "Not assessed", and in Operation log in Log Analytics workspace, every 30 minutes these messages keep appearing. I'm thinking the two are connected.

[si-kotic]

I'm also experiencing exactly the same.
Heartbeat is present but no Syslogs except for this exact error message and a recommendation to log it here in github.

[siva-az103]

We have the same error message - Workspace Status appears as 1 Warning since 7 days with the error message mentioned above by others.

Awaiting a resolution from MS please.

[veerendra903]

I am also facing the same in my Log analytics workspace. Can some one please help

[Mokatsu]

Is there any movement on this issue? I am also seeing this error, started few days ago. Heartbeat sends logs, CEF logs are flowing but custom logs are not being send. In addition the agent no longer is receiving updates

[jberk1202]

just added another issue for this before I noticed this one. Also receiving this error now.