@@ -52,7 +52,7 @@ The operating system check verifies if the Hybrid Runbook Worker is running one
52
52
53
53
To verify if a VM is an Azure VM, check for Asset tag value using the below command:
54
54
55
- ```
55
+ ``` bash
56
56
sudo dmidecode
57
57
```
58
58
@@ -73,13 +73,13 @@ This task checks if the folder is present -
73
73
74
74
To fix this issue, you must start the OMS Agent service by using the following command:
75
75
76
- ```
76
+ ``` bash
77
77
sudo /opt/microsoft/omsagent/bin/service_control restart
78
78
```
79
79
80
80
To validate you can perform process check using the below command:
81
81
82
- ```
82
+ ``` bash
83
83
process_name=" omsagent"
84
84
ps aux | grep %s | grep -v grep" % (process_name)"
85
85
```
@@ -102,26 +102,26 @@ As they are the directories of workspaces, the number of directories equals the
102
102
### Hybrid Runbook Worker
103
103
To fix the issue, run the following command:
104
104
105
- ```
105
+ ``` bash
106
106
sudo su omsagent -c ' python /opt/microsoft/omsconfig/Scripts/PerformRequiredConfigurationChecks.py'
107
107
```
108
108
109
109
This command forces the omsconfig agent to talk to Azure Monitor and retrieve the latest configuration.
110
110
111
111
Validate to check if the following two paths exists:
112
112
113
- ```
113
+ ``` bash
114
114
/opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/VERSION < /br> /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/DSCResources/MSFT_nxOMSAutomationWorkerResource/automationworker/worker/configuration.py
115
115
```
116
116
117
117
### Hybrid Runbook Worker status
118
118
119
119
This check makes sure the Hybrid Runbook Worker is running on the machine. The processes in the example below should be present if the Hybrid Runbook Worker is running correctly.
120
- ```
120
+ ``` bash
121
121
ps -ef | grep python
122
122
```
123
123
124
- ```
124
+ ``` output
125
125
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>
126
126
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>
127
127
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>
@@ -131,7 +131,7 @@ Update Management downloads Hybrid Runbook Worker packages from the operations e
131
131
132
132
To fix this issue, run the following command:
133
133
134
- ```
134
+ ``` bash
135
135
sudo su omsagent -c ' python /opt/microsoft/omsconfig/Scripts/PerformRequiredConfigurationChecks.py'
136
136
```
137
137
@@ -149,7 +149,7 @@ To fix the issue, either remove the proxy or make sure that the proxy address is
149
149
150
150
You can validate the task by running the below command:
151
151
152
- ```
152
+ ``` bash
153
153
HTTP_PROXY
154
154
```
155
155
@@ -159,7 +159,7 @@ To fix this issue, allow access to IP **169.254.169.254**. For more information,
159
159
160
160
After the network changes, you can either rerun the Troubleshooter or run the below commands to validate:
161
161
162
- ```
162
+ ``` bash
163
163
curl -H \" Metadata: true\" http://169.254.169.254/metadata/instance? api-version=2018-02-01
164
164
```
165
165
@@ -214,7 +214,7 @@ Curl on software repositories configured in package manager.
214
214
215
215
Refreshing repos would help to confirm the communication.
216
216
217
- ```
217
+ ``` bash
218
218
sudo apt-get check
219
219
sudo yum check-update
220
220
```
0 commit comments