Merge pull request #235952 from msaenzbosupport/patch-18

[Doc-A-thon]Updating code block

Author: prmerger-automator[bot]

articles/automation/troubleshoot/update-agent-issues-linux.md

@@ -52,7 +52,7 @@ The operating system check verifies if the Hybrid Runbook Worker is running one
 
 To verify if a VM is an Azure VM, check for Asset tag value using the below command:
 
-```
+```bash
 sudo dmidecode
 ```
 
@@ -73,13 +73,13 @@ This task checks if the folder is present -
 
 To fix this issue, you must start the OMS Agent service by using the following command: 
 
-```
+```bash
  sudo /opt/microsoft/omsagent/bin/service_control restart
 ```
 
 To validate you can perform process check using the below command: 
 
-```
+```bash
 process_name="omsagent" 
 ps aux | grep %s | grep -v grep" % (process_name)" 
 ```
@@ -102,26 +102,26 @@ As they are the directories of workspaces, the number of directories equals the
 ### Hybrid Runbook Worker
 To fix the issue, run the following command: 
 
-```
+```bash
 sudo su omsagent -c 'python /opt/microsoft/omsconfig/Scripts/PerformRequiredConfigurationChecks.py'
 ```
 
 This command forces the omsconfig agent to talk to Azure Monitor and retrieve the latest configuration. 
 
 Validate to check if the following two paths exists:
 
-```
+```bash
 /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/VERSION </br> /opt/microsoft/omsconfig/modules/nxOMSAutomationWorker/DSCResources/MSFT_nxOMSAutomationWorkerResource/automationworker/worker/configuration.py
 ```
 
 ### Hybrid Runbook Worker status
 
 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.
-```
+```bash
 ps -ef | grep python
 ```
 
-```
+```output
 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>
@@ -131,7 +131,7 @@ Update Management downloads Hybrid Runbook Worker packages from the operations e
 
 To fix this issue, run the following command:
 
-```
+```bash
 sudo su omsagent -c 'python /opt/microsoft/omsconfig/Scripts/PerformRequiredConfigurationChecks.py'
 ```
 
@@ -149,7 +149,7 @@ To fix the issue, either remove the proxy or make sure that the proxy address is
 
 You can validate the task by running the below command:
 
-```
+```bash
 HTTP_PROXY
 ```
 
@@ -159,7 +159,7 @@ To fix this issue, allow access to IP **169.254.169.254**. For more information,
 
 After the network changes, you can either rerun the Troubleshooter or run the below commands to validate: 
 
-```
+```bash
  curl -H \"Metadata: true\" http://169.254.169.254/metadata/instance?api-version=2018-02-01
 ```
 
@@ -214,7 +214,7 @@ Curl on software repositories configured in package manager.
 
 Refreshing repos would help to confirm the communication. 
 
-```
+```bash
 sudo apt-get check
 sudo yum check-update
 ```