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: docs/sql-server/azure-arc/troubleshoot-extension.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,9 +94,9 @@ To identify possible problems, review the value in the **RecommendedAction** or
94
94
95
95
| Recommended Action | Action Details |
96
96
|--------------------|----------------|
97
-
| Machine cert is expired.<br /><br />Go to the machine on the Azure portal for more information on how to resolve this issue. | The Arc-enabled machine must be re-onboarded to Arc because the certificate used to authenticate to Azure has expired. The Arc machine status is **Expired** in the Azure portal. Uninstall the agent by following the documentation [here](/azure/azure-arc/servers/manage-agent#uninstall-the-agent) and then re-onboard [here](/azure/azure-arc/servers/deployment-options). There is no need to delete the Arc-enabled SQL Server resources in the portal if you are just re-onboarding. The SQL extension will be automatically installed again as long as [auto-onboarding](connect.md) is enabled (default). |
98
-
| Machine is disconnected.<br /><br />Reconnect the machine. | The Arc machine is in a `state = Disconnected`. This state could be for a variety of reasons:<br /><br />Arc connected machine agent is stopped, disabled or constantly crashing<br /><br />or<br /><br />Connectivity is blocked between the agent and Azure.<br /><br />[Check the state of that Arc connected machine services/daemons to make sure they are enabled and running](/azure/azure-arc/servers/agent-overview#agent-resources).<br /><br />[Check the connectivity](/azure/azure-arc/servers/troubleshoot-agent-onboard).<br /><br />[Troubleshoot the agent using the verbose log](/azure/azure-arc/servers/troubleshoot-agent-onboard#agent-verbose-log). |
99
-
| Extension reported as unhealthy.<br /><br />View FailureReasons and LastExtensionStatusMessage for more information as to the cause of the failure.<br /><br />Last upload outside acceptable range (within the last 3 days). | Check the **LastExtensionUploadTimestamp** column. If it is **No timestamp**, it has never reported inventory or usage data to Azure. [Troubleshoot connectivity from the SQL extension to Azure](troubleshoot-telemetry-endpoint.md).<br /><br />If the last upload is outside the acceptable range (within the last 3 days) and everything else looks OK such as **LastExtensionUploadStatus**, **ExtensionProvisioningState**, and **MachineStatus**, then it is possible that the Arc SQL Extension service/daemon is stopped. Figure out why it is stopped and start it again. Check the **LastExtensionStatusMessage** for any other clues about the problem. |
97
+
| Machine cert is expired.<br /><br />Go to the machine on the Azure portal for more information on how to resolve this issue. | The Arc-enabled machine must be re-onboarded to Arc because the certificate used to authenticate to Azure expired. The Arc machine status is **Expired** in the Azure portal. Uninstall the agent by following the documentation [here](/azure/azure-arc/servers/manage-agent#uninstall-the-agent) and then re-onboard [here](/azure/azure-arc/servers/deployment-options). There is no need to delete the Arc-enabled SQL Server resources in the portal if you are re-onboarding. The SQL extension is automatically installed again as long as [auto-onboarding](connect.md) is enabled (default). |
98
+
| Machine is disconnected.<br /><br />Reconnect the machine. | The Arc machine is in a `state = Disconnected`. This state could be for various reasons:<br /><br />Arc connected machine agent is stopped, disabled, or constantly crashing<br /><br />or<br /><br />Connectivity is blocked between the agent and Azure.<br /><br />[Check the state of that Arc connected machine services/daemons to make sure they are enabled and running](/azure/azure-arc/servers/agent-overview#agent-resources).<br /><br />[Check the connectivity](/azure/azure-arc/servers/troubleshoot-agent-onboard).<br /><br />[Troubleshoot the agent using the verbose log](/azure/azure-arc/servers/troubleshoot-agent-onboard#agent-verbose-log). |
99
+
| Extension reported as unhealthy.<br /><br />View FailureReasons and LastExtensionStatusMessage for more information as to the cause of the failure.<br /><br />Last upload outside acceptable range (within the last three days). | Check the **LastExtensionUploadTimestamp** column. If it is **No timestamp**, it never reported inventory or usage data to Azure. [Troubleshoot connectivity from the SQL extension to Azure](troubleshoot-telemetry-endpoint.md).<br /><br />If the last upload is outside the acceptable range (within the last three days) and everything else looks OK such as **LastExtensionUploadStatus**, **ExtensionProvisioningState**, and **MachineStatus**, then it is possible that the Arc SQL Extension service/daemon is stopped. Figure out why it is stopped and start it again. Check the **LastExtensionStatusMessage** for any other clues about the problem. |
100
100
| Extension provisioning status is **Failed**.<br /><br />Investigate and resolve extension provisioning state. | Either the initial installation of the SQL extension or the update failed.[ Check the deployer and extension logs](troubleshoot-deployment.md).<br /><br />Check the value in the **LastExtensionStatusMessage**. |
101
101
| Upload status is not reported OK | Check the **LastExtensionMessage** column in the dashboard and look at the **uploadStatus** value and the **uploadMessage** value (if present, depending on version).<br /><br />The **uploadStatus** value is typically an HTTP error code. Review [Troubleshoot error codes](troubleshoot-telemetry-endpoint.md#error-codes).<br /><br />The **uploadMessage** may have more specific information. [General Arc SQL extension connectivity troubleshooting](troubleshoot-telemetry-endpoint.md). |
102
102
| Extension provisioning status is **Updating**<br /><br />or<br /><br />Extension provisioning state is **Creating**<br /><br />or<br /><br />Extension provisioning state is **Failed**<br /><br />or<br /><br />Extension provisioning state is **Deleting**| If a given extension stays one of these states for more than 30 minutes, there is likely a problem with provisioning. Uninstall the extension and reinstall it using the CLI or portal. If the problem persists, [check the deployer and extension logs](troubleshoot-deployment.md).<br /><br />If delete fails, try uninstalling the agent and deleting the Arc machine resource in the portal if needed and then redeploy.<br /><br />Uninstall the agent by following the documentation [here](/azure/azure-arc/servers/manage-agent#uninstall-the-agent) and then re-onboard [here](/azure/azure-arc/servers/deployment-options). |
@@ -203,7 +203,7 @@ resources
203
203
| order by ['agentHeartbeatLagInDays'] asc
204
204
```
205
205
206
-
This query returns a count of extensions grouped by the number of days since the extension last updated its status. A value of '-1' indicates that the extension has crashed and there is a callstack in the extension status.
206
+
This query returns a count of extensions grouped by the number of days since the extension last updated its status. A value of '-1' indicates that the extension crashed and there is a callstack in the extension status.
0 commit comments