|
| 1 | +--- |
| 2 | +title: Understand the Linux agent check results in Azure Update Management |
| 3 | +description: Learn how to troubleshoot issues with the Update Management agent. |
| 4 | +services: automation |
| 5 | +author: georgewallace |
| 6 | +ms.author: gwallace |
| 7 | +ms.date: 11/06/2018 |
| 8 | +ms.topic: conceptual |
| 9 | +ms.service: automation |
| 10 | +ms.component: update-management |
| 11 | +manager: carmonm |
| 12 | +--- |
| 13 | + |
| 14 | +# Understand the Linux agent check results in Update Management |
| 15 | + |
| 16 | +There may be many reasons your machine is not showing **Ready** in Update Management. In Update Management, you can check the health of a Hybrid Worker agent to determine the underlying problem. This article discusses how to run the troubleshooter from the Azure portal and in offline scenarios. |
| 17 | + |
| 18 | +## Start the troubleshooter |
| 19 | + |
| 20 | +By clicking the **Troubleshoot** link under the **Update Agent Readiness** column in the portal, you launch the **Troubleshoot Update Agent** page. This page shows you problems with the agent and a link to this article to assist you in troubleshooting your issues. |
| 21 | + |
| 22 | + |
| 23 | + |
| 24 | +> [!NOTE] |
| 25 | +> The checks require the VM to be running. If the VM is not running you are presented with a button to **Start the VM**. |
| 26 | +
|
| 27 | +On the **Troubleshoot Update Agent** page, click **Run Checks**, to start the troubleshooter. The troubleshooter uses [Run command](../../virtual-machines/linux/run-command.md) to run a script on the machine to verify the dependencies that the agent has. When the troubleshooter is complete, it returns the result of the checks. |
| 28 | + |
| 29 | + |
| 30 | + |
| 31 | +When complete, the results are returned in the window. The [check sections](#pre-requisistes-checks) provide information on what each check is looking for. |
| 32 | + |
| 33 | + |
| 34 | + |
| 35 | +## Prerequisite checks |
| 36 | + |
| 37 | +### Operating system |
| 38 | + |
| 39 | +The OS check, verifies if the Hybrid Runbook Worker is running one of the following Operating Systems: |
| 40 | + |
| 41 | +|Operating system |Notes | |
| 42 | +|---------|---------| |
| 43 | +|CentOS 6 (x86/x64) and 7 (x64) | Linux agents must have access to an update repository. Classification-based patching requires 'yum' to return security data which CentOS does not have out of the box. | |
| 44 | +|Red Hat Enterprise 6 (x86/x64) and 7 (x64) | Linux agents must have access to an update repository. | |
| 45 | +|SUSE Linux Enterprise Server 11 (x86/x64) and 12 (x64) | Linux agents must have access to an update repository. | |
| 46 | +|Ubuntu 14.04 LTS, 16.04 LTS, and 18.04 LTS (x86/x64) |Linux agents must have access to an update repository. | |
| 47 | + |
| 48 | +## Monitoring agent service health checks |
| 49 | + |
| 50 | +### OMS agent |
| 51 | + |
| 52 | +This checks ensures that the OMS Agent for Linux is installed. For instructions on how to install it, see [Install the agent for Linux](../../log-analytics/log-analytics-quick-collect-linux-computer.md#install-the-agent-for-linux). |
| 53 | + |
| 54 | +### OMS Agent status |
| 55 | + |
| 56 | +This check ensures that the OMS Agent for Linux is running. If the agent is not running you can run the following command to attempt to restart it. For additional information on troubleshooting the agent, see [Linux Hybrid Runbook worker troubleshooting](hybrid-runbook-worker.md#linux) |
| 57 | + |
| 58 | +```bash |
| 59 | +sudo /opt/microsoft/omsagent/bin/service_control restart |
| 60 | +``` |
| 61 | + |
| 62 | +### Multihoming |
| 63 | + |
| 64 | +This check determines if the agent is reporting to multiple workspaces. Multi-homing is not supported by Update Management. |
| 65 | + |
| 66 | +### Hybrid Runbook Worker |
| 67 | + |
| 68 | +This checks to ensure the OMS Agent for Linux has the Hybrid Runbook Worker package. This package is required for Update Management to work. |
| 69 | + |
| 70 | +### Hybrid Runbook Worker status |
| 71 | + |
| 72 | +This check makes sure the Hybrid Runbook Worker is running on the machine. The following processes should be present if the Hybrid Runbook Worker is running correctly. To learn more, see [troubleshooting the Log Analytics Agent for Linux](hybrid-runbook-worker.md#oms-agent-not-running). |
| 73 | + |
| 74 | +```bash |
| 75 | +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> |
| 76 | +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> |
| 77 | +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> |
| 78 | +``` |
| 79 | + |
| 80 | +## Connectivity checks |
| 81 | + |
| 82 | +### General internet connectivity |
| 83 | + |
| 84 | +This check makes sure that the machine has access to the internet. |
| 85 | + |
| 86 | +### Registration endpoint |
| 87 | + |
| 88 | +This check determines if the agent can properly communicate with the agent service. |
| 89 | + |
| 90 | +Proxy and firewall configurations must allow the Hybrid Runbook Worker agent to communicate with the registration endpoint. For a list of addresses and ports to open, see [Network planning for Hybrid Workers](../automation-hybrid-runbook-worker.md#network-planning) |
| 91 | + |
| 92 | +### Operations endpoint |
| 93 | + |
| 94 | +This check determines if the agent can properly communicate with the Job Runtime Data Service. |
| 95 | + |
| 96 | +Proxy and firewall configurations must allow the Hybrid Runbook Worker agent to communicate with the Job Runtime Data Service. For a list of addresses and ports to open, see [Network planning for Hybrid Workers](../automation-hybrid-runbook-worker.md#network-planning) |
| 97 | + |
| 98 | +### Log Analytics endpoint 1 |
| 99 | + |
| 100 | +This check verifies that your machine has access to the endpoints needed by the Log Analytics agent. |
| 101 | + |
| 102 | +### Log Analytics endpoint 2 |
| 103 | + |
| 104 | +This check verifies that your machine has access to the endpoints needed by the Log Analytics agent. |
| 105 | + |
| 106 | +### Log Analytics endpoint 3 |
| 107 | + |
| 108 | +This check verifies that your machine has access to the endpoints needed by the Log Analytics agent. |
| 109 | + |
| 110 | +## Troubleshoot offline |
| 111 | + |
| 112 | +You can use the troubleshooter offline on a Hybrid Runbook Worker by running the script locally. The python script, [update_mgmt_health_check.py](https://gallery.technet.microsoft.com/scriptcenter/Troubleshooting-utility-3bcbefe6) can be found in Script Center. An example of the output of this script is shown in the following example: |
| 113 | + |
| 114 | +```output |
| 115 | +Debug: Machine Information: Static hostname: LinuxVM2 |
| 116 | + Icon name: computer-vm |
| 117 | + Chassis: vm |
| 118 | + Machine ID: 00000000000000000000000000000000 |
| 119 | + Boot ID: 00000000000000000000000000000000 |
| 120 | + Virtualization: microsoft |
| 121 | + Operating System: Ubuntu 16.04.5 LTS |
| 122 | + Kernel: Linux 4.15.0-1025-azure |
| 123 | + Architecture: x86-64 |
| 124 | +
|
| 125 | +
|
| 126 | +Passed: Operating system version is supported |
| 127 | +
|
| 128 | +Passed: Microsoft Monitoring agent is installed |
| 129 | +
|
| 130 | +Debug: omsadmin.conf file contents: |
| 131 | + WORKSPACE_ID=00000000-0000-0000-0000-000000000000 |
| 132 | + AGENT_GUID=00000000-0000-0000-0000-000000000000 |
| 133 | + LOG_FACILITY=local0 |
| 134 | + CERTIFICATE_UPDATE_ENDPOINT=https://00000000-0000-0000-0000-000000000000.oms.opinsights.azure.com/ConfigurationService.Svc/RenewCertificate |
| 135 | + URL_TLD=opinsights.azure.com |
| 136 | + DSC_ENDPOINT=https://scus-agentservice-prod-1.azure-automation.net/Accou nts/00000000-0000-0000-0000-000000000000/Nodes\(AgentId='00000000-0000-0000-0000-000000000000'\) |
| 137 | + OMS_ENDPOINT=https://00000000-0000-0000-0000-000000000000.ods.opinsights .azure.com/OperationalData.svc/PostJsonDataItems |
| 138 | + AZURE_RESOURCE_ID=/subscriptions/00000000-0000-0000-0000-000000000000/re sourcegroups/myresourcegroup/providers/microsoft.compute/virtualmachines/linuxvm 2 |
| 139 | + OMSCLOUD_ID=0000-0000-0000-0000-0000-0000-00 |
| 140 | + UUID=00000000-0000-0000-0000-000000000000 |
| 141 | +
|
| 142 | +
|
| 143 | +Passed: Microsoft Monitoring agent is running |
| 144 | +
|
| 145 | +Passed: Machine registered with log analytics workspace:['00000000-0000-0000-0000-000000000000'] |
| 146 | +
|
| 147 | +Passed: Hybrid worker package is present |
| 148 | +
|
| 149 | +Passed: Hybrid worker is running |
| 150 | +
|
| 151 | +Passed: Machine is connected to internet |
| 152 | +
|
| 153 | +Passed: TCP test for {scus-agentservice-prod-1.azure-automation.net} (port 443) succeeded |
| 154 | +
|
| 155 | +Passed: TCP test for {eus2-jobruntimedata-prod-su1.azure-automation.net} (port 4 43) succeeded |
| 156 | +
|
| 157 | +Passed: TCP test for {00000000-0000-0000-0000-000000000000.ods.opinsights.azure. com} (port 443) succeeded |
| 158 | +
|
| 159 | +Passed: TCP test for {00000000-0000-0000-0000-000000000000.oms.opinsights.azure. com} (port 443) succeeded |
| 160 | +
|
| 161 | +Passed: TCP test for {ods.systemcenteradvisor.com} (port 443) succeeded |
| 162 | +
|
| 163 | +``` |
| 164 | + |
| 165 | +## Next steps |
| 166 | + |
| 167 | +To troubleshoot additional issues with your Hybrid Runbook Workers, see [Troubleshoot - Hybrid Runbook Workers](hybrid-runbook-worker.md) |
0 commit comments