更新代理准备(断开连接)混合工作者 - Linux VM [英] Update Agent Readiness (Disconnected) Hybrid Worker - Linux VM

查看:150
本文介绍了更新代理准备(断开连接)混合工作者 - Linux VM的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

想知道是否有人遇到过这个问题的可靠解决方案,其中Linux VM在Update Management中显示为"Disconnected";在更新代理准备情况下,并提到混合工作者没有运行。


我查看了几个链接但没有提到具体的修复。



在此处查看  https:// docs .microsoft.com / mt-mt / azure / automation / troubleshoot / update-agent-issues-linux


我在linux上看不到这些运行


nxautom +    8567      1  0 14:45?        00:00:00 python /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/DSCResources/MSFT_nxOMSAutomationWorkerResource/automationworker/worker/main.py /var/opt/microsoft/omsagent/state/automationworker/oms.conf
rworkspace: < workspaceId> < Linux混合工作者版本>

nxautom +  &NBSP; 8593&NBSP; &NBSP; &NBSP; 1&NBSP; 0 14:45?  &NBSP; &NBSP; &NBSP; 00:00:02 python /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/DSCResources/MSFT_nxOMSAutomationWorkerResource/automationworker/worker/hybridworker.py /var/opt/microsoft/omsagent/state/automationworker/worker.conf
managed rworkspace :其中workspaceId> rversion:< Linux混合工作者版本>

nxautom +  &NBSP; 8595&NBSP; &NBSP; &NBSP; 1&NBSP; 0 14:45?  &NBSP; &NBSP; &NBSP; 00:00:02 python /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/DSCResources/MSFT_nxOMSAutomationWorkerResource/automationworker/worker/hybridworker.py / var / opt / microsoft / omsagent /< workspaceId> / state / automationworker / diy / worker。 conf
托管的rworkspace:< workspaceId> rversion:< Linux混合工作者版本>


同样运行python脚本并且它提到混合工作者没有运行


调试:机器信息:  
静态主机名: 


   ;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;
图标名称:computer-vm


  &NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;
机箱:vm


    ;&NBSP;&NBSP;&NBSP;&NBSP;
机器ID: 


   ;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;
引导ID


   
虚拟化:microsoft


 
操作系统:Red Hat Enterprise Linux


  ;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;
CPE操作系统名称:cpe:/ o:redhat:enterprise_linux:7.3:GA:服务器


<跨度>&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;
内核:Linux 3.10.0-514.28.1.el7.x86_64


<跨度>&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;
架构:x86-64


 


 


通过:支持操作系统版本


 


已通过:已安装Microsoft Monitoring代理


 


调试:omsadmin.conf文件内容:


    &NBSP;&NBSP;&NBSP;&NBSP;
WORKSPACE_ID =


    &NBSP;&NBSP;&NBSP;&NBSP;
AGENT_GUID =


    &NBSP;&NBSP;&NBSP;&NBSP;
LOG_FACILITY = local0


    ;&NBSP;&NBSP;&NBSP;&NBSP;
CERTIFICATE_UPDATE_ENDPOINT = https://-187de645997d.oms.opinsights.azure.com/ConfigurationService.Svc/RenewCertificate


       
URL_TLD = opinsights.azure.com


  ;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;&NBSP;
DSC_ENDPOINT = https://cc-agentservice-prod-1.azure-automation.net/Accounts//Nodes\(AgentId =''\)


       
OMS_ENDPOINT = https://797e9107-35d2-4b9b-8a03-187de645997d.ods.opinsights.azure.com/OperationalData.svc/PostJsonDataItems


       
AZURE_RESOURCE_ID = / subscriptions / cresourceGroups // providers / Microsoft.Compute / virtualMachines / saskusis-ua-ssh


       
OMSCLOUD_ID =


    &NBSP;&NBSP;&NBSP;&NBSP;
UUID =


 


 


通过:Microsoft Monitoring代理正在运行


 


通过:使用日志分析工作区注册的计算机:['']


< p style ="margin:0in; font-family:Calibri; font-size:11.0pt"> 


通过:混合工人包存在


 


失败:混合工作者未运行


 


调试:未启用更新部署解决方案。资源设置:[{" WorkspaceId":""," AzureDnsAgentSvcZone":" agentsvc.azure-automation.net"," Solutions" ;:{" Updates":{" Enabled":false}," AzureAutomation":{" Enabled":false}}}}


 


通过:机器已连接到互联网


 


通过:{cc-agentservice-prod-1.azure-automation.net}(端口443)的TCP测试成功


 


通过:{cc-jobruntimedata-prod-su1.azure-automation.net}(端口443)的TCP测试成功


 


通过:{ods.opinsights.azure.com}(端口443)的TCP测试成功


 


通过:{.oms.opinsights.azure.com}(端口443)的TCP测试成功


 


通过:{ods.systemcenteradvisor.com}(端口443)的TCP测试成功



尝试修补失败,这就是我在更新管理中看到的内容




有没有人知道这个问题的解决方案才能正常使用我的工作已经找到了?目前我还没有想到这一点。任何帮助总是受到赞赏



干杯



解决方案





根据此消息判断:



调试:未启用更新部署解决方案。资源设置:[{" WorkspaceId": ""," AzureDnsAgentSvcZone":" agentsvc.azure-automation.net","解决方案":{"更新与QUOT;:{"启用":假}," AzureAutomation":{"启用" ;:假}}}]





似乎没有为该服务器添加更新管理解决方案。如果您转到Log Analytics并查看该服务器的Heartbeat数据,您可能会看到相同的结果。下面的示例显示了启用更新的单台机器的Heartbeat。







如果您不希望修补所有添加的计算机,则可以将更新管理作用于特定计算机。如果您在更新管理刀片中有或其他人选择加入该选项,您将有按钮来管理计算机。在那里,您可以配置
,使解决方案可用于哪些机器。您可以在所有计算机上或所选计算机上启用它。我认为你就是这种情况。如果是,并通过更改配置进行修复,请将此回复标记为答案



Wondering if anyone has come across a solid fix for this issue where Linux VMs show up in Update Management as "Disconnected" under Update Agent Readiness and mention Hybrid Worker is not running.

I have looked at several links but none mention a specific fix.

Looked here https://docs.microsoft.com/mt-mt/azure/automation/troubleshoot/update-agent-issues-linux

Where I don't see these running in linux

nxautom+   8567      1  0 14:45 ?        00:00:00 python /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/DSCResources/MSFT_nxOMSAutomationWorkerResource/automationworker/worker/main.py /var/opt/microsoft/omsagent/state/automationworker/oms.conf rworkspace:<workspaceId> <Linux hybrid worker version>
nxautom+   8593      1  0 14:45 ?        00:00:02 python /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/DSCResources/MSFT_nxOMSAutomationWorkerResource/automationworker/worker/hybridworker.py /var/opt/microsoft/omsagent/state/automationworker/worker.conf managed rworkspace:<workspaceId> rversion:<Linux hybrid worker version>
nxautom+   8595      1  0 14:45 ?        00:00:02 python /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/DSCResources/MSFT_nxOMSAutomationWorkerResource/automationworker/worker/hybridworker.py /var/opt/microsoft/omsagent/<workspaceId>/state/automationworker/diy/worker.conf managed rworkspace:<workspaceId> rversion:<Linux hybrid worker version>

As well ran the python script and it mentions the Hybrid Worker is not running

Debug: Machine Information:   Static hostname: 

         Icon name: computer-vm

           Chassis: vm

        Machine ID: 

           Boot ID

    Virtualization: microsoft

  Operating System: Red Hat Enterprise Linux

       CPE OS Name: cpe:/o:redhat:enterprise_linux:7.3:GA:server

            Kernel: Linux 3.10.0-514.28.1.el7.x86_64

      Architecture: x86-64

 

 

Passed: Operating system version is supported

 

Passed: Microsoft Monitoring agent is installed

 

Debug: omsadmin.conf file contents:

        WORKSPACE_ID=

        AGENT_GUID=

        LOG_FACILITY=local0

        CERTIFICATE_UPDATE_ENDPOINT=https://-187de645997d.oms.opinsights.azure.com/ConfigurationService.Svc/RenewCertificate

        URL_TLD=opinsights.azure.com

        DSC_ENDPOINT=https://cc-agentservice-prod-1.azure-automation.net/Accounts//Nodes\(AgentId=''\)

        OMS_ENDPOINT=https://797e9107-35d2-4b9b-8a03-187de645997d.ods.opinsights.azure.com/OperationalData.svc/PostJsonDataItems

        AZURE_RESOURCE_ID=/subscriptions/cresourceGroups//providers/Microsoft.Compute/virtualMachines/saskusis-ua-ssh

        OMSCLOUD_ID=

        UUID=

 

 

Passed: Microsoft Monitoring agent is running

 

Passed: Machine registered with log analytics workspace:['']

 

Passed: Hybrid worker package is present

 

Failed: Hybrid worker is not running

 

Debug: Update deployment solution is not enabled. ResourceSettings:[{"WorkspaceId":"","AzureDnsAgentSvcZone":"agentsvc.azure-automation.net","Solutions":{"Updates":{"Enabled":false},"AzureAutomation":{"Enabled":false}}}]

 

Passed: Machine is connected to internet

 

Passed: TCP test for {cc-agentservice-prod-1.azure-automation.net} (port 443) succeeded

 

Passed: TCP test for {cc-jobruntimedata-prod-su1.azure-automation.net} (port 443) succeeded

 

Passed: TCP test for {ods.opinsights.azure.com} (port 443) succeeded

 

Passed: TCP test for {.oms.opinsights.azure.com} (port 443) succeeded

 

Passed: TCP test for {ods.systemcenteradvisor.com} (port 443) succeeded

Attempting to patching fails and this is what I see in update management



Does anyone know the fix for this to get working properly with what I have found? At the moment I have not figured this out yet. Any help is always appreciated

Cheers

解决方案

Hi,

Judging by this message:

Debug: Update deployment solution is not enabled. ResourceSettings:[{"WorkspaceId":"","AzureDnsAgentSvcZone":"agentsvc.azure-automation.net","Solutions":{"Updates":{"Enabled":false},"AzureAutomation":{"Enabled":false}}}]


Seems like Update Management solution is not added for that server somehow. If you go to Log Analytics and look at the Heartbeat data for that server you might probably see the same result. Example below shows Heartbeat for single machine where updates is enabled.



Update Management can be scoped to specific machines in case you do not want every machine added to be patched. If you have or someone else opt-in for that option in the Update Management blade you will have button to manage machines. There you can configure on which machines to be available the solution. You can enable it on all, on all future machines or a selected computers. I would assume that is the case with you. If it is and you fix it by changing the configuration please mark this reply as answer


这篇关于更新代理准备(断开连接)混合工作者 - Linux VM的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆