rsyslod throwing the error "omazuremds error at connect(). errno=No such file or directory [v8.24.0]"

[kailashms]

The customer is running redhat 7.3 and he upgraded the vm to 7.4 After that he is constantly seeing the error: " omazuremds error at connect(). errno=No such file or directory [v8.24.0]" which is stopping the rsyslogd from its functionality/

Also apart from these errors, we could see these errors as well. Nov 9 18:09:57 tbs-devsvr02 azsecd: 2017-11-09T18:04:14.3252370Z: MdsAutoKey: Error occurred while downloading bootstrapKey command blob: Error resolving address Nov 9 18:09:57 tbs-devsvr02 azsecd: 2017-11-09T18:04:44.3326400Z: MdsAutoKey: Error occurred while downloading bootstrapKey command blob: Error resolving address Nov 9 18:09:57 tbs-devsvr02 azsecd: 2017-11-09T18:04:44.3326700Z: MdsAutoKey: MdsAutoKey: unable to download or parse any keys: Nov 9 18:09:57 tbs-devsvr02 azsecd: 2017-11-09T18:04:44.3326750Z: GetLatestMdsAutoKeys returned Failure

checked the extension logs and could see that" OMS: 1.4.56.5 version is installed

Also the LAD verions: 2.3.9027 is installed: and from the extension.log and the mdsd.err file we could see the below error:

extension.log 2017/09/20 21:00:26 2017-09-20T20:55:22.0008820Z: Error: Unable to connect to OMI service. (Is OMI installed and started?) 2017/09/20 21:00:26 2017-09-20T20:55:22.0009130Z: Connection to OMI server failed; query task (SELECT PercentAvailableMemory, AvailableMemory, UsedMemory, PercentUsedSwap FROM SCX_MemoryStatisticalInformation) not started. Will try to start the task again in 20 seconds. 2017/09/20 21:00:26 2017-09-20T20:55:22.0009190Z: Connection to OMI server failed; query task (SELECT PercentProcessorTime, PercentIOWaitTime, PercentIdleTime FROM SCX_ProcessorStatisticalInformation WHERE Name='_TOTAL') not started. Will try to start the task again in 20 seconds. 2017/09/20 21:00:26 2017-09-20T20:55:22.0009520Z: Error: Unable to connect to OMI service. (Is OMI installed and started?) 2017/09/20 21:00:26 2017-09-20T20:55:22.0009700Z: Connection to OMI server failed; query task (SELECT AverageWriteTime,AverageReadTime,ReadBytesPerSecond,WriteBytesPerSecond FROM SCX_DiskDriveStatisticalInformation WHERE Name='_TOTAL') not started. Will try to start the task again in 20 seconds. 2017/09/20 21:00:26

mdsd.err file:

2017-09-19T22:08:21.5489000Z: Error: Unable to connect to OMI service. (Is OMI installed and started?) 2017-09-19T22:08:21.5489340Z: Connection to OMI server failed; query task (SELECT PercentAvailableMemory, AvailableMemory, UsedMemory, PercentUsedSwap FROM SCX_MemoryStatisticalInformation) not started. Will try to start the task again in 10 seconds. 2017-09-19T22:08:21.5489750Z: Error: Unable to connect to OMI service. (Is OMI installed and started?) 2017-09-19T22:08:21.5489820Z: Connection to OMI server failed; query task (SELECT PercentProcessorTime, PercentIOWaitTime, PercentIdleTime FROM SCX_ProcessorStatisticalInformation WHERE Name='_TOTAL') not started. Will try to start the task again in 10 seconds. 2017-09-19T22:08:21.5490110Z: Error: Unable to connect to OMI service. (Is OMI installed and started?)

As far as the last update there seems to be some issue with LAD and OMS but it was only for 3.0 version.

can you please confirm if the same implies for the same version : 2.3.?

Also could you please let us know how we can proceed further on the same.

Thanks Kailash

[jasonzio]

omsagent introduced an incompatibility in 1.4.1-123 which was quickly fixed and released in 1.4.2-124. LAD 2.3 doesn't use or interact with OMS or the omsagent; LAD 3.0 does.

To resolve the OMI issue, uninstall LAD 2.3 and then re-install it.

[kailashms]

Thanks Jason, we have done the same and it did resolve the issue. Cheers !!!

Regards,

Kailash B Microsoft Azure Linux Support Support Engineer

Working Hours: Working Days: Email: Manager: Office Phone:

14:30 – 23:30 IST Tuesday-Saturday v-kaib@microsoft.commailto:v-kaib@microsoft.com v-madka@microsoft.com +91 40 67230584 Ext: 30584

From: Jason Zions [mailto:notifications@github.com] Sent: Tuesday, November 21, 2017 2:07 AM To: Azure/azure-linux-extensions azure-linux-extensions@noreply.github.com Cc: Kailash B (MINDTREE LIMITED) v-kaib@microsoft.com; Author author@noreply.github.com Subject: Re: [Azure/azure-linux-extensions] rsyslod throwing the error "omazuremds error at connect(). errno=No such file or directory [v8.24.0]" (#488)

omsagent introduced an incompatibility in 1.4.1-123 which was quickly fixed and released in 1.4.2-124. LAD 2.3 doesn't use or interact with OMS or the omsagent; LAD 3.0 does.

To resolve the OMI issue, uninstall LAD 2.3 and then re-install it.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-linux-extensions%2Fissues%2F488%23issuecomment-345823674&data=02%7C01%7Cv-kaib%40microsoft.com%7C4ea7a366288143173cbd08d530567b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636468070343036537&sdata=en14GZ9egVCqCk6um9ioZZsFToM6U55hlwezvGKH8qY%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAYbOO1-xd8UwT-zHb11NJWAWfATyhZfrks5s4eL4gaJpZM4QZFwY&data=02%7C01%7Cv-kaib%40microsoft.com%7C4ea7a366288143173cbd08d530567b30%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636468070343036537&sdata=KhSh5iWcGvr43SVDzgVOfdt5qyo3F%2FkptKp4vvdtiGA%3D&reserved=0.

[dcbrown16]

@jasonzio

LAD 2.3 doesn't use or interact with OMS or the omsagent; LAD 3.0 does.

Does this mean that updating to LAD 3.0 will also fix the issue? I have another customer who has run into this exact message.

[jasonzio]

LAD 3.0 needs to be updated to include the correct package; until that happens, the same issue may arise.

[dcbrown16]

On closer inspection, I may have read the earlier comment wrong - does updating LAD (either 2.3 or 3.0) fix the error message below? "omazuremds error at connect(). errno=No such file or directory [v8.24.0]"

I see that you only explicitly mentioned it fixes the OMI issue, which I take to mean: "Error: Unable to connect to OMI service. "

[jasonzio]

The issue with omsagent 1.4.1-123 would often manifest with the rsyslogd/omazuremds error.

[ImranBijapuri]

Can you tell me how to upgrade the extension from 2.3 to 3.0 ?

[abhijeetgaiha]

@ImranBijapuri There is no direct upgrade path from 2.3 to 3.0. You can follow the instructions here to install LAD 3.0: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/diagnostic-extension. The docs also have a link to a public config that configures the same metrics as LAD 2.3. You can use that as your starting point.

[jasonzio]

Reminder: You must uninstall 2.3 before installing 3.0.

Second reminder: You can (and should) start with the “2.3-compatible config”, but you should also remove from it the metrics you don’t care about and consider if you want to collect some instanced metrics 2.3 didn’t support (E.g. per file system usage data).

Sent from my Windows 10 phone

---

From: Abhijeet Gaiha notifications@github.com Sent: Thursday, March 22, 2018 9:19:48 AM To: Azure/azure-linux-extensions Cc: Jason Zions; Mention Subject: Re: [Azure/azure-linux-extensions] rsyslod throwing the error "omazuremds error at connect(). errno=No such file or directory [v8.24.0]" (#488)

@ImranBijapurihttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fimranbijapuri&data=04%7C01%7CJason.Zions%40microsoft.com%7C3ec989612c1e4697f3fa08d59010bcd3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636573323915854464%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=ZXMnQ%2FjOshcpYiufsErbrXnE2rVwY2VzuXL47qiaISs%3D&reserved=0 There is no direct upgrade path from 2.3 to 3.0. You can follow the instructions here to install LAD 3.0: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/diagnostic-extensionhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fvirtual-machines%2Flinux%2Fdiagnostic-extension&data=04%7C01%7CJason.Zions%40microsoft.com%7C3ec989612c1e4697f3fa08d59010bcd3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636573323915854464%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=GuC9sSsa3EsnIU0PGZ1IeFXPaEQFysEbJt1Y62lKbhw%3D&reserved=0. The docs also have a link to a public config that configures the same metrics as LAD 2.3. You can use that as your starting point.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fazure-linux-extensions%2Fissues%2F488%23issuecomment-375366746&data=04%7C01%7CJason.Zions%40microsoft.com%7C3ec989612c1e4697f3fa08d59010bcd3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636573323915854464%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=yZj25kRxUhfdiZP%2FUqzd8X%2F1DiY8gTgEyNjbvZ0PdXY%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAIAi4SqLKvVwROcYvQ1r3dISrFm6LynCks5tg88kgaJpZM4QZFwY&data=04%7C01%7CJason.Zions%40microsoft.com%7C3ec989612c1e4697f3fa08d59010bcd3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636573323915854464%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwifQ%3D%3D%7C-1&sdata=e%2BW328wHROIxPVvfXWdynOi3WHYvOI6WD44A4gVva%2BA%3D&reserved=0.

[Mangaleshwar]

@jasonzio

I was going through this thread and we now have a similar issue. Linux VMDiagnostic extension is showing the status as "Provisioning Failed" with the below error.

Failed to set up mdsd dependencies: setup_omsagent(): Failed at restarting omsagent (fluentd). Exit code=1, Output=control_omsagent(restart) failed. Output: INFO: Configuring OMS agent service LAD

These are the current versions: OMS 1.6.42.0, successfully provisioned VMDiagnostics 3.0.111 provisioning failed

This error occurred only after the OMSagent extension update which occurred last week. Before that, OMS was 1.4.x and there were no issues with the diagnostics extension.

Any inputs or a possible workaround on this issue will be helpful for us. Please let me know if you require any other information as well.

Regards, Mangaleshwar

[abhijeetgaiha]

@Mangaleshwar Please try uninstalling LAD and then OMS (in that order) then re-installing LAD and then OMS.

[pmzone31]

@abhijeetgaiha - Any other work around for the same as i am facing this issue on my prod server and cannot proceed with this approach..

[pmzone31]

@Mangaleshwar - Have you been able to find any other way to solve the error you are facing as i am also facing exactly the same issue and infact on the same versions of OMS and LAD.

[abhijeetgaiha]

@pmzone31 What versions of LAD and OMS are you using?

[pmzone31]

@abhijeetgaiha -- OMS : 1.6.42.0 and LAD : 3.0.111

[abhijeetgaiha]

@pmzone31 1) Please run log collector and provide results: https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/tools/LogCollector/OMS_Linux_Agent_Log_Collector.md 2) Please zip up all files under /var/log/azure and provide that too.

[pmzone31]

@abhijeetgaiha putty.log

PFA the logs

[abhijeetgaiha]

Next version of LAD will fix this issue.

[dawsonrs]

Is this still an issue?
I have just deployed a VM with OMS and diagnostics (omsagent 1.7.3 and LAD 3.0.113) - the OMSExtension resource deployed fine but the LinuxDiagnostic resource failed, citing a conflict, with the same message as above: "message": "VM has reported a failure when processing extension 'LinuxDiagnostic'. Error message: \"Failed to set up mdsd dependencies: omsagent setup failed 5 times. Last exit code=3, Output=setup_omsagent_for_lad(): fluentd out_mdsd plugin install failed. Output: /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in require': cannot load such file -- rubygems/safe_yaml (LoadError)\n\tfrom /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:inrequire'\n\tfrom /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems.rb:702:in load_yaml'\n\tfrom /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/config_file.rb:340:inload_file'\n\tfrom /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/config_file.rb:202:in initialize'\n\tfrom /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/gem_runner.rb:75:innew'\n\tfrom /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/gem_runner.rb:75:in do_configuration'\n\tfrom /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/gem_runner.rb:40:inrun'\n\tfrom /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/fluentd-0.12.40/bin/fluent-gem:6:in <top (required)>'\n\tfrom /opt/microsoft/omsagent/ruby/bin/fluent-gem:23:inload'\n\tfrom /opt/microsoft/omsagent/ruby/bin/fluent-gem:23:in `

'\n\"."

This deployment has worked fine in the past, do I need to think about introducing an extension dependency or the like, or is it an issue due to be fixed?

[buckyguy33]

I am experiencing the same error message when deploying a VM (OpenLogic CentOS 7.5) with OMS and VM diagnostics (omsagent 1.7.3 and LAD 3.0.113).

[dawsonrs]

FYI, I worked around this issue successfully by adding an explicit extension dependency to the ARM template - in my case I had the OMSExtension depend on the LinuxDiagnostic extension so that they deployed in series, rather than in parallel.

[abhijeetgaiha]

@dawsonrs Which OS version were you using?

[dawsonrs]

@abhijeetgaiha I am using RHEL 7 latest (so 7.4)

[shkhisti]

We have identified the issue and we are in the process of releasing the hotfix.

[carct]

i`m also getting this:

Failed to set up mdsd dependencies: omsagent setup failed 5 times. Last exit code=3, Output=setup_omsagent_for_lad(): fluentd out_mdsd plugin install failed. Output: /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- rubygems/safe_yaml (LoadError) from /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require' from /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems.rb:702:in `load_yaml' from /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/config_file.rb:340:in `load_file' from /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/config_file.rb:202:in `initialize' from /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/gem_runner.rb:75:in `new' from /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/gem_runner.rb:75:in `do_configuration' from /opt/microsoft/omsagent/ruby/lib/ruby/2.4.0/rubygems/gem_runner.rb:40:in `run' from /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/fluentd-0.12.40/bin/fluent-gem:6:in `<top (required)>' from /opt/microsoft/omsagent/ruby/bin/fluent-gem:23:in `load' from /opt/microsoft/omsagent/ruby/bin/fluent-gem:23:in `<main>'
HANDLER STATUSReady
HANDLER STATUS LEVELInfo

from TYPE Microsoft.Azure.Diagnostics.LinuxDiagnostic VERSION 3.0.117

Other extensions present related to this (successfully installed):

• DependencyAgentLinux: VERSION 9.7.3.1475

• OmsAgentForLinux: VERSION 1.8.9

  @jasonzio

[andrewatfornax]

Can anyone please advise how to successfully complete the work around?

Having installed the LAD 3.0 agent, which reports as succeeding from the install process, but only some time later on shows up as not working in the Portal, I have performed the following:

• Uninstalled the LAD 3.0 Agent
• Uninstalled the OMS Agent
• Re-installed the LAD 3.0 Agent

At this point, the LAD 3.0 agent now appears to really have worked, and I see metrics appearing for the VM. However, it is not clear to me how to re-install the OMS agent.

The documentation at https://github.com/Microsoft/OMS-Agent-for-Linux/blob/master/docs/OMS-Agent-for-Linux.md suggests that I need to supply a Workspace ID and Shared Key for the installation. However, how do I find these?

I am not, in this case, looking to use a custom deployed Log Analytics instance, but to restore the VM to it's previous state. Looking at other VMs that I have not performed this action on, it looks like the OMS agent is normally deployed with the VM to a custom or hidden UUID based workspace ID?

How do I find that out, to be able to re-install the OMS agent as it was before I removed it to get the LAD 3.0 agent installed?

Thanks.

[Rangi-th]

The problem seems to be fixed in latest OMS release: 1.9.1 I tested this on CentOS 7.5 and RHEL 7.2 (installing OMS agent first and then installing LAD) and all the extensions are running and in provisioning succeeded status even after a reboot.

[dawsonrs]

hmmm - not working for me when I tested a fresh VM deployment (RHEL 7.6). For the OMSExtension, I have set typeHandlerVersion to 1.9 and can see that it is trying to install that, but it fails to do so:

[root@vm-ul-ap4 Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux]# cat CommandExecution.log 2019/02/28 12:42:11.502641 INFO [Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] Remove extension handler directory: /var/lib/waagent/Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1 [root@vm-ul-ap4 Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux]# [root@vm-ul-ap4 Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux]# [root@vm-ul-ap4 Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux]# cat extension.log 2019/02/28 12:39:24 [Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] sequence number is 0 2019/02/28 12:39:24 [Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] setting file path is/var/lib/waagent/Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1/config/0.settings 2019/02/28 12:39:24 [Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] JSON config: {"runtimeSettings": [{"handlerSettings": {"protectedSettings": " REDACTED ", "publicSettings": {"workspaceId": "d44c10d6-8cce-4389-95a8-5d31d41b66d2"}, "protectedSettingsCertThumbprint": " REDACTED "}}]} 2019/02/28 12:39:24 [Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] Config decoded correctly. 2019/02/28 12:39:24 [Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] Running command "/var/lib/waagent/Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1/packages/omsagent-1.9.0-0.universal.x64.sh --upgrade" 2019/02/28 12:42:08 ERROR:CalledProcessError. Error Code is 17 2019/02/28 12:42:08 ERROR:CalledProcessError. Command string was /var/lib/waagent/Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1/packages/omsagent-1.9.0-0.universal.x64.sh --upgrade 2019/02/28 12:42:08 ERROR:CalledProcessError. Command result was Checking host architecture ... 2019/02/28 12:42:08 ERROR:Extracting... 2019/02/28 12:42:08 ERROR:----- Upgrading package: omi (omi-1.6.0-0.ulinux.x64) ----- 2019/02/28 12:42:08 ERROR:Creating omiusers group ... 2019/02/28 12:42:08 ERROR:Creating omi group ... 2019/02/28 12:42:08 ERROR:Creating omi service account ... 2019/02/28 12:42:08 ERROR:Generating a 2048 bit RSA private key 2019/02/28 12:42:08 ERROR:.................................................................................................+++ 2019/02/28 12:42:08 ERROR:........................................................................................+++ 2019/02/28 12:42:08 ERROR:unable to write 'random state' 2019/02/28 12:42:08 ERROR:writing new private key to '/etc/opt/omi/ssl/omikey.pem' 2019/02/28 12:42:08 ERROR:----- 2019/02/28 12:42:08 ERROR:2019-02-28 12:40:00 : Crontab not configured to update omi keytab automatically. Skip unconfigure 2019/02/28 12:42:08 ERROR:2019-02-28 12:40:00 : Crontab configured to update omi keytab automatically 2019/02/28 12:42:08 ERROR:Configuring OMI service ... 2019/02/28 12:42:08 ERROR:Created symlink from /etc/systemd/system/multi-user.target.wants/omid.service to /usr/lib/systemd/system/omid.service. 2019/02/28 12:42:08 ERROR:Checking if cron is installed... 2019/02/28 12:42:08 ERROR:Checking if cron/crond service is started... 2019/02/28 12:42:08 ERROR:Set up a cron job to OMI logrotate every 15 minutes 2019/02/28 12:42:08 ERROR:System appears to have SELinux installed, attempting to install selinux policy module for logrotate 2019/02/28 12:42:08 ERROR: Trying /usr/share/selinux/packages/omi-logrotate/omi-logrotate.pp ... 2019/02/28 12:42:08 ERROR: Labeling omi log files ... 2019/02/28 12:42:08 ERROR:----- Upgrading package: scx (scx-1.6.3-659.universal.x64) ----- 2019/02/28 12:42:08 ERROR:warning: waiting for transaction lock on /var/lib/rpm/.rpm.lock 2019/02/28 12:42:08 ERROR:Generating certificate with hostname="vm-ul-ap4" 2019/02/28 12:42:08 ERROR:System appears to have SELinux installed, attempting to install selinux policy module for logrotate 2019/02/28 12:42:08 ERROR: Trying /usr/share/selinux/packages/scxagent-logrotate/scxagent-logrotate.pp ... 2019/02/28 12:42:08 ERROR:----- Upgrading package: omsagent (omsagent-1.9.0-0.universal.x64) ----- 2019/02/28 12:42:08 ERROR:warning: waiting for transaction lock on /var/lib/rpm/.rpm.lock 2019/02/28 12:42:08 ERROR: file /etc/opt/microsoft/omsagent/sysconf/omsagent.d/monitor.conf from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /etc/opt/microsoft/omsagent/sysconf/omsagent.ulinux from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/bin/configure_syslog.sh from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/bin/service_control from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/plugin/Libomi.so from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/plugin/docker_audits.xml from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/plugin/oms_audits.xml from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/plugin/oms_configuration.rb from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/plugin/omsbaseline from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/plugin/omsremediate from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/plugin/out_oms_blob.rb from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/plugin/security_baseline_lib.rb from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/libruby-static.a from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/cache/fluentd-0.12.40.gem from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/cool.io-1.5.3/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/http_parser.rb-0.6.0/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/json-2.1.0/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/msgpack-1.1.0/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/oj-2.17.0/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/string-scrub-0.0.5/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/yajl-ruby-1.3.1/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/cool.io-1.5.3/ext/cool.io/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/cool.io-1.5.3/ext/iobuffer/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/http_parser.rb-0.6.0/ext/ruby_http_parser/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/ext/generator/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/ext/parser/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/oj-2.17.0/ext/oj/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/string-scrub-0.0.5/ext/string/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/yajl-ruby-1.3.1/ext/yajl/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/fluentd-0.12.40/lib/fluent/plugin/in_exec.rb from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/buffer.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/buffer_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/core_ext.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/extension_value_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/factory_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/packer.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/packer_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/packer_ext_registry.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/rbinit.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/rmem.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/unpacker.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/unpacker_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/unpacker_ext_registry.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR: file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/specifications/fluentd-0.12.40.gemspec from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:08 ERROR:omsagent-1.9.0-0.universal.x64 package failed to upgrade and exited with status 1 2019/02/28 12:42:08 ERROR:Shell bundle exiting with code 17 2019/02/28 12:42:09 [Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] Output of command "/var/lib/waagent/Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1/packages/omsagent-1.9.0-0.universal.x64.sh --upgrade": 2019/02/28 12:42:09 Checking host architecture ... 2019/02/28 12:42:09 Extracting... 2019/02/28 12:42:09 ----- Upgrading package: omi (omi-1.6.0-0.ulinux.x64) ----- 2019/02/28 12:42:09 Creating omiusers group ... 2019/02/28 12:42:09 Creating omi group ... 2019/02/28 12:42:09 Creating omi service account ... 2019/02/28 12:42:09 Generating a 2048 bit RSA private key 2019/02/28 12:42:09 .................................................................................................+++ 2019/02/28 12:42:09 ........................................................................................+++ 2019/02/28 12:42:09 unable to write 'random state' 2019/02/28 12:42:09 writing new private key to '/etc/opt/omi/ssl/omikey.pem' 2019/02/28 12:42:09 ----- 2019/02/28 12:42:09 2019-02-28 12:40:00 : Crontab not configured to update omi keytab automatically. Skip unconfigure 2019/02/28 12:42:09 2019-02-28 12:40:00 : Crontab configured to update omi keytab automatically 2019/02/28 12:42:09 Configuring OMI service ... 2019/02/28 12:42:09 Created symlink from /etc/systemd/system/multi-user.target.wants/omid.service to /usr/lib/systemd/system/omid.service. 2019/02/28 12:42:09 Checking if cron is installed... 2019/02/28 12:42:09 Checking if cron/crond service is started... 2019/02/28 12:42:09 Set up a cron job to OMI logrotate every 15 minutes 2019/02/28 12:42:09 System appears to have SELinux installed, attempting to install selinux policy module for logrotate 2019/02/28 12:42:09 Trying /usr/share/selinux/packages/omi-logrotate/omi-logrotate.pp ... 2019/02/28 12:42:09 Labeling omi log files ... 2019/02/28 12:42:09 ----- Upgrading package: scx (scx-1.6.3-659.universal.x64) ----- 2019/02/28 12:42:09 warning: waiting for transaction lock on /var/lib/rpm/.rpm.lock 2019/02/28 12:42:09 Generating certificate with hostname="vm-ul-ap4" 2019/02/28 12:42:09 System appears to have SELinux installed, attempting to install selinux policy module for logrotate 2019/02/28 12:42:09 Trying /usr/share/selinux/packages/scxagent-logrotate/scxagent-logrotate.pp ... 2019/02/28 12:42:09 ----- Upgrading package: omsagent (omsagent-1.9.0-0.universal.x64) ----- 2019/02/28 12:42:09 warning: waiting for transaction lock on /var/lib/rpm/.rpm.lock 2019/02/28 12:42:09 file /etc/opt/microsoft/omsagent/sysconf/omsagent.d/monitor.conf from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /etc/opt/microsoft/omsagent/sysconf/omsagent.ulinux from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/bin/configure_syslog.sh from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/bin/service_control from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/plugin/Libomi.so from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/plugin/docker_audits.xml from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/plugin/oms_audits.xml from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/plugin/oms_configuration.rb from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/plugin/omsbaseline from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/plugin/omsremediate from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/plugin/out_oms_blob.rb from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/plugin/security_baseline_lib.rb from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/libruby-static.a from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/cache/fluentd-0.12.40.gem from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/cool.io-1.5.3/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/http_parser.rb-0.6.0/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/json-2.1.0/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/msgpack-1.1.0/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/oj-2.17.0/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/string-scrub-0.0.5/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/extensions/x86_64-linux/2.4.0-static/yajl-ruby-1.3.1/gem_make.out from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/cool.io-1.5.3/ext/cool.io/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/cool.io-1.5.3/ext/iobuffer/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/http_parser.rb-0.6.0/ext/ruby_http_parser/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/ext/generator/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/json-2.1.0/ext/json/ext/parser/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/oj-2.17.0/ext/oj/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/string-scrub-0.0.5/ext/string/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/yajl-ruby-1.3.1/ext/yajl/Makefile from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/fluentd-0.12.40/lib/fluent/plugin/in_exec.rb from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/buffer.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/buffer_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/core_ext.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/extension_value_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/factory_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/packer.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/packer_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/packer_ext_registry.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/rbinit.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/rmem.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/unpacker.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/unpacker_class.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/gems/msgpack-1.1.0/ext/msgpack/unpacker_ext_registry.o from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 file /opt/microsoft/omsagent/ruby/lib/ruby/gems/2.4.0/specifications/fluentd-0.12.40.gemspec from install of omsagent-1.9.0-0.x86_64 conflicts with file from package omsagent-1.6.1-3.x86_64 2019/02/28 12:42:09 omsagent-1.9.0-0.universal.x64 package failed to upgrade and exited with status 1 2019/02/28 12:42:09 Shell bundle exiting with code 17 2019/02/28 12:42:09 ERROR:Install failed with exit code 17 2019/02/28 12:42:09 ERROR:[Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] Install failed with exit code 17 2019/02/28 12:42:09 [Microsoft.EnterpriseCloud.Monitoring.OmsAgentForLinux-1.9.1] Install,failed,17,Install failed with exit code 17

[dawsonrs]

update - it does work in a specific scenario: When creating the VM, if I set typeHandlerVersion to 1.9 for the OMSExtension and deploy that extension first (i.e. all other extensions have an explicit dependency set on the OMSExtension), then that works. It does not work deployed alongside, or after, Linux diagnostics