You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/troubleshoot/update-agent-issues-linux.md
+17-18Lines changed: 17 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,39 +1,39 @@
1
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.
2
+
title: Understand the Linux Hybrid Runbook Worker health in Azure Update Management
3
+
description: Learn how to troubleshoot issues with the Hybrid Runbook Worker on Linux that supports Update Management.
4
4
services: automation
5
-
author: bobbytreed
6
-
ms.author: robreed
7
-
ms.date: 04/22/2019
5
+
author: mgoedtel
6
+
ms.author: magoedte
7
+
ms.date: 12/03/2019
8
8
ms.topic: conceptual
9
9
ms.service: automation
10
10
ms.subservice: update-management
11
11
manager: carmonm
12
12
---
13
13
14
-
# Understand the Linux agent check results in Update Management
14
+
# Understand the Linux Hybrid Runbook Worker health in Update Management
15
15
16
-
There may be many reasons your machine isn't 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 for Azure machines from the Azure portal and Non-Azure machines in the [offline scenario](#troubleshoot-offline).
16
+
There may be many reasons your machine isn't showing **Ready** in Update Management. In Update Management, you can check the health of a Hybrid Runbook Worker agent to determine the underlying problem. This article discusses how to run the troubleshooter for Azure machines from the Azure portal and non-Azure machines in the [offline scenario](#troubleshoot-offline).
17
17
18
18
The following list are the three readiness states a machine can be in:
19
19
20
-
***Ready** - The update agent is deployed and was last seen less than 1 hour ago.
21
-
***Disconnected** - The update agent is deployed and was last seen over 1 hour ago.
22
-
***Not configured** - The update agent isn't found or hasn't finished onboarding.
20
+
***Ready** - The Hybrid Runbook Worker is deployed and was last seen less than 1 hour ago.
21
+
***Disconnected** - The Hybrid Runbook Worker is deployed and was last seen over 1 hour ago.
22
+
***Not configured** - The Hybrid Runbook Worker isn't found or hasn't finished onboarding.
23
23
24
24
> [!NOTE]
25
25
> There may be a slight delay between what the Azure portal shows and the current state of the machine.
26
26
27
27
## Start the troubleshooter
28
28
29
-
For Azure machines, clicking the **Troubleshoot** link under the **Update Agent Readiness** column in the portal launches the **Troubleshoot Update Agent** page. For Non-Azure machines, the link brings you to this article. See the offline instructions to troubleshoot a Non-Azure machine.
29
+
For Azure machines, clicking the **Troubleshoot** link under the **Update Agent Readiness** column in the portal launches the **Troubleshoot Update Agent** page. For non-Azure machines, the link brings you to this article. See the offline instructions to troubleshoot a non-Azure machine.
30
30
31
31
32
32
33
33
> [!NOTE]
34
34
> The checks require the VM to be running. If the VM is not running you are presented with a button to **Start the VM**.
35
35
36
-
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.
36
+
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. When the troubleshooter is complete, it returns the result of the checks.
@@ -45,7 +45,7 @@ When complete, the results are returned in the window. The check sections provid
45
45
46
46
### Operating system
47
47
48
-
The OS check, verifies if the Hybrid Runbook Worker is running one of the following Operating Systems:
48
+
The operating system check verifies if the Hybrid Runbook Worker is running one of the following Operating Systems:
49
49
50
50
|Operating system |Notes |
51
51
|---------|---------|
@@ -56,9 +56,9 @@ The OS check, verifies if the Hybrid Runbook Worker is running one of the follow
56
56
57
57
## Monitoring agent service health checks
58
58
59
-
### OMS agent
59
+
### Log Analytics agent
60
60
61
-
This check ensures that the OMS Agent for Linux is installed. For instructions on how to install it, see [Install the agent for Linux](../../azure-monitor/learn/quick-collect-linux-computer.md#install-the-agent-for-linux
61
+
This check ensures that the Log Analytics agent for Linux is installed. For instructions on how to install it, see [Install the agent for Linux](../../azure-monitor/learn/quick-collect-linux-computer.md#install-the-agent-for-linux
62
62
).
63
63
64
64
### OMS Agent status
@@ -95,7 +95,7 @@ This check makes sure that the machine has access to the internet.
95
95
96
96
### Registration endpoint
97
97
98
-
This check determines if the agent can properly communicate with the agent service.
98
+
This check determines if the Hybrid Runbook Worker can properly communicate with Azure Automation the Log Analytics workspace.
99
99
100
100
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)
101
101
@@ -174,5 +174,4 @@ Passed: TCP test for {ods.systemcenteradvisor.com} (port 443) succeeded
174
174
175
175
## Next steps
176
176
177
-
To troubleshoot additional issues with your Hybrid Runbook Workers, see [Troubleshoot - Hybrid Runbook Workers](hybrid-runbook-worker.md)
178
-
177
+
To troubleshoot additional issues with your Hybrid Runbook Workers, see [Troubleshoot - Hybrid Runbook Workers](hybrid-runbook-worker.md)
# Understand the Windows agent check results in Update Management
14
+
# Understand the Windows Hybrid Runbook Worker health in Update Management
15
15
16
16
There may be many reasons your machine isn't showing **Ready** in Update Management. In Update Management, you can check the health of a Hybrid Runbook Worker agent to determine the underlying problem. This article discusses how to run the troubleshooter for Azure machines from the Azure portal and non-Azure machines in the [offline scenario](#troubleshoot-offline).
17
17
@@ -31,9 +31,9 @@ For Azure machines, clicking the **Troubleshoot** link under the **Update Agent
31
31
32
32
33
33
> [!NOTE]
34
-
> To check the health of an agent, the VM must be running. If the VM isn't running, a **Start the VM** button appears.
34
+
> To check the health of the Hybrid Runbook Worker, the VM must be running. If the VM isn't running, a **Start the VM** button appears.
35
35
36
-
On the **Troubleshoot Update Agent** page, select **Run checks** to start the troubleshooter. The troubleshooter uses [Run Command](../../virtual-machines/windows/run-command.md) to run a script on the machine to verify agent dependencies. When the troubleshooter is finished, it returns the result of the checks.
36
+
On the **Troubleshoot Update Agent** page, select **Run checks** to start the troubleshooter. The troubleshooter uses [Run Command](../../virtual-machines/windows/run-command.md) to run a script on the machine to verify dependencies. When the troubleshooter is finished, it returns the result of the checks.
0 commit comments