deepblue/windows-itpro-docs
1
0
Fork 0
mirror of https://github.com/MicrosoftDocs/windows-itpro-docs.git synced 2025-06-15 18:33:43 +00:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

Added proxy, WSL, scheduled task sections to troubleshooting page

Browse Source
This commit is contained in:
chrisjlin
2024-10-25 15:10:02 -07:00
parent 1f7cae57d9
commit 9cd06356e0
1 changed files with 27 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

33
windows/deployment/do/mcc-ent-troubleshooting.md
View File

@ -28,7 +28,7 @@ This article contains instructions on how to troubleshoot different issues you m
[Connected Cache Azure resource creation](mcc-ent-create-resource-and-cache.md) can be initiated using either the Azure portal user interface or the Azure CLI command set.
If you're encountering an error during resource creation, check that you have the necessary RPaaS permissions and have filled out all required fields during the resource creation process.
If you're encountering an error during resource creation, check that you have the necessary permissions to create Azure resources under your subscription and have filled out all required fields during the resource creation process.
## Troubleshooting cache node configuration
@ -38,6 +38,8 @@ If you're encountering a validation error, check that you have filled out all re
If your configuration doesn't appear to be taking effect, check that you have clicked the "Save" button at the top of the configuration page in the Azure portal user interface.
If you have changed the proxy configuration, you will need to re-provision the Connected Cache software on the host machine for the proxy configuration to take effect.
## Troubleshooting cache nodes created during early preview
Cache nodes created and deployed during the [Microsoft Connected Cache for Enterprise and Education early preview](mcc-ent-private-preview.md) should continue to function but can no longer be managed or monitored remotely via the Connected Cache Azure service.
@ -46,6 +48,8 @@ As such, we strongly recommend you [recreate your existing resources in Azure](m
## Troubleshooting cache node deployment to Windows host machine
### Collecting Windows-hosted installation logs
[Deploying a Connected Cache node to a Windows host machine](mcc-ent-deploy-to-windows.md) involves running a series of PowerShell scripts contained within the Windows provisioning package. These scripts will attempt to write log files to the installation directory specified in the provisioning command (`C:\mccwsl01\InstallLogs` by default).
There are three types of installation log files:
@ -56,15 +60,32 @@ There are three types of installation log files:
The Registered Task Transcript is usually the most useful for diagnosing the installation issue.
### Updating the WSL2 kernel
If the Connected Cache installation is failing due to WSL-related issues, try running `wsl.exe --update` to get the latest version of the WSL kernel.
### Checking if the Connected Cache container is running
Once the Connected Cache software has been successfully deployed to the Windows host machine, you can check if the cache node is running properly by doing the following on the Windows host machine:
1. Launch a PowerShell process as the account specified as the runtime account during the Connected Cache install
1. Run `wsl -d Ubuntu-22.04-Mcc-Base` to access the Linux distribution that hosts the Connected Cache container
1. Run `sudo iotedge list` to show which containers are running within the IoT Edge runtime
If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs --f`.
If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs -- -f`.
You can also reboot the IoT Edge runtime using `sudo iotedge restart`.
You can also reboot the IoT Edge runtime using `sudo systemctl restart iotedge`.
### Checking Connected Cache scheduled tasks
Once the Connected Cache container is running, a scheduled task is periodically run under the Connected Cache runtime account to keep WSL from cleaning up the Connected Cache container.
You can use Task Scheduler on the host machine to check the status of this scheduled task.
1. Open Task Scheduler on the host machine
1. Navigate to the Active Tasks section and double-click on "MCC_Monitor_Task"
1. Select the scheduled task "MCC_Monitor_Task"
1. Select the "Triggers" tab and confirm that the Status is "Enabled"
## Troubleshooting cache node deployment to Linux host machine
@ -74,9 +95,9 @@ Once the Connected Cache software has been successfully deployed to the Linux ho
1. Run `sudo iotedge list` to show which containers are running within the IoT Edge runtime
If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs --f`.
If it shows the **edgeAgent** and **edgeHub** containers but doesn't show **MCC**, you can view the status of the IoT Edge security manager using `sudo iotedge system logs -- -f`.
You can also reboot the IoT Edge runtime using `sudo iotedge restart`.
You can also reboot the IoT Edge runtime using `sudo systemctl restart iotedge`.
## Troubleshooting cache node monitoring
@ -84,7 +105,7 @@ Connected Cache node status and performance can be [monitored using the Azure po
If the [basic monitoring](mcc-ent-monitoring.md#basic-monitoring) visuals on the Overview tab are showing unexpected or erroneous values, refresh the browser window.
If the issue persists, check that you have configured the Timespan and Cache nodes as desired.
If the issue persists, check that you have configured the Timespan and Cache node filters as desired.
## Diagnose and Solve