Skip to content

Commit d1d2af1

Browse files
Acrolinx
1 parent 40d54f0 commit d1d2af1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/machine-learning/how-to-troubleshoot-online-endpoints.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -119,7 +119,7 @@ or
119119
az ml online-deployment get-logs --endpoint-name <endpoint-name> --name <deployment-name> --lines 100
120120
```
121121

122-
Add `--resource-group` and `--workspace-name` to the these commands if you have not already set these parameters via `az configure`.
122+
Add `--resource-group` and `--workspace-name` to these commands if you have not already set these parameters via `az configure`.
123123

124124
To see information about how to set these parameters, and if you have already set current values, run:
125125

@@ -222,7 +222,7 @@ This is a list of common image build failure scenarios:
222222

223223
#### Container registry authorization failure
224224

225-
If the error message mentions `"container registry authorization failure"` that means you can not access the container registry with the current credentials.
225+
If the error message mentions `"container registry authorization failure"` that means you cannot access the container registry with the current credentials.
226226
The desynchronization of a workspace resource's keys can cause this error and it takes some time to automatically synchronize.
227227
However, you can [manually call for a synchronization of keys](/cli/azure/ml/workspace#az-ml-workspace-sync-keys), which may resolve the authorization failure.
228228

@@ -548,7 +548,7 @@ In this case, you can check the cluster network policy and the workspace contain
548548

549549
The reason you might run into this error when creating/updating Kubernetes online deployments is the user container crashed initializing. There are two possible reasons for this error:
550550
* User script `score.py` has syntax error or import error then raise exceptions in initializing.
551-
* Or the deployment pod needs more memory than it's limit.
551+
* Or the deployment pod needs more memory than its limit.
552552

553553
To mitigate this error, first you can check the deployment logs for any exceptions in user scripts. If error persists, try to extend resources/instance type memory limit.
554554

0 commit comments

Comments
 (0)