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
In this article, you'll troubleshoot allocation failures where Azure Cloud services (classic) can't deploy because of allocation constraints.
18
+
In this article, you troubleshoot allocation failures where Azure Cloud services (classic) can't deploy because of allocation constraints.
19
19
20
20
When you deploy instances to a Cloud service (classic) or add new web or worker role instances, Microsoft Azure allocates compute resources.
21
21
@@ -30,21 +30,21 @@ In Azure portal, navigate to your Cloud service (classic) and in the sidebar sel
30
30
31
31
32
32
33
-
When you're inspecting the logs of your Cloud service (classic), you'll see the following exception:
33
+
When you inspect the logs of your Cloud service (classic), you see the following exception:
34
34
35
35
|Exception Type |Error Message |
36
36
|---------|---------|
37
-
|ConstrainedAllocationFailed |Azure operation '`{Operation ID}`' failed with code Compute.ConstrainedAllocationFailed. Details: Allocation failed; unable to satisfy constraints in request. The requested new service deployment is bound to an Affinity Group, or it targets a Virtual Network, or there is an existing deployment under this hosted service. Any of these conditions constrains the new deployment to specific Azure resources. Retry later or try reducing the VM size or number of role instances. Alternatively, if possible, remove the aforementioned constraints or try deploying to a different region.|
37
+
|ConstrainedAllocationFailed |Azure operation '`{Operation ID}`' failed with code Compute.ConstrainedAllocationFailed. Details: Allocation failed; unable to satisfy constraints in request. The requested new service deployment is bound to an Affinity Group, or it targets a Virtual Network, or there's an existing deployment under this hosted service. Any of these conditions constrains the new deployment to specific Azure resources. Retry later or try reducing the virtual machine (VM) size or number of role instances. Alternatively, if possible, remove the constraints or try deploying to a different region.|
38
38
39
39
## Cause
40
40
41
41
When the first instance is deployed to a Cloud service (in either staging or production), that Cloud service gets pinned to a cluster.
42
42
43
-
Over time, the resources in this cluster may become fully utilized. If a Cloud service (classic) makes an allocation request for more resources when insufficient resources are available in the pinned cluster, the request will result in an allocation failure. For more information, see the [allocation failure common issues](cloud-services-allocation-failures.md#common-issues).
43
+
Over time, the resources in this cluster may become fully utilized. If a Cloud service (classic) makes an allocation request for more resources when insufficient resources are available in the pinned cluster, the request results in an allocation failure. For more information, see the [allocation failure common issues](cloud-services-allocation-failures.md#common-issues).
44
44
45
45
## Solution
46
46
47
-
Existing cloud services are *pinned* to a cluster. Any further deployments for the Cloud service (classic) will happen in the same cluster.
47
+
Existing cloud services are *pinned* to a cluster. Any further deployments for the Cloud service (classic) happen in the same cluster.
48
48
49
49
When you experience an allocation error in this scenario, the recommended course of action is to redeploy to a new Cloud service (classic) (and update the *CNAME*).
50
50
@@ -76,4 +76,4 @@ For more allocation failure solutions and background information:
76
76
> [!div class="nextstepaction"]
77
77
> [Allocation failures - Cloud service (classic)](cloud-services-allocation-failures.md)
78
78
79
-
If your Azure issue isn't addressed in this article, visit the Azure forums on [MSDN and Stack Overflow](https://azure.microsoft.com/support/forums/). You can post your issue in these forums, or post to [@AzureSupport on Twitter](https://twitter.com/AzureSupport). You also can submit an Azure support request. To submit a support request, on the [Azure support](https://azure.microsoft.com/support/options/) page, select *Get support*.
79
+
If your Azure issue isn't addressed in this article, visit the Azure forums on [the Microsoft Developer Network (MSDN) and Stack Overflow](https://azure.microsoft.com/support/forums/). You can post your issue in these forums, or post to [@AzureSupport on Twitter](https://twitter.com/AzureSupport). You also can submit an Azure support request. To submit a support request, on the [Azure support](https://azure.microsoft.com/support/options/) page, select *Get support*.
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-troubleshoot-default-temp-folder-size-too-small-web-worker-role.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Default TEMP folder size is too small for a role | Microsoft Docs
3
3
description: A cloud service role has a limited amount of space for the TEMP folder. This article provides some suggestions on how to avoid running out of space.
4
4
ms.topic: troubleshooting
5
5
ms.service: cloud-services
6
-
ms.date: 02/21/2023
6
+
ms.date: 07/24/2024
7
7
author: hirenshah1
8
8
ms.author: hirshah
9
9
ms.reviewer: mimckitt
@@ -20,7 +20,7 @@ The default temporary directory of a cloud service worker or web role has a maxi
The standard Windows environment variables TEMP and TMP are available to code that is running in your application. Both TEMP and TMP point to a single directory that has a maximum size of 100 MB. Any data that is stored in this directory is not persisted across the lifecycle of the cloud service; if the role instances in a cloud service are recycled, the directory is cleaned.
23
+
The standard Windows environment variables TEMP and TMP are available to code that is running in your application. Both TEMP and TMP point to a single directory that has a maximum size of 100 MB. Any data stored in this directory isn't persisted across the lifecycle of the cloud service. If the role instances in a cloud service are recycled, the directory is cleaned.
Copy file name to clipboardExpand all lines: articles/cloud-services/cloud-services-troubleshoot-deployment-problems.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Troubleshoot cloud service (classic) deployment problems | Microsoft Docs
3
3
description: There are a few common problems you may run into when deploying a cloud service to Azure. This article provides solutions to some of them.
4
4
ms.topic: troubleshooting
5
5
ms.service: cloud-services
6
-
ms.date: 02/21/2023
6
+
ms.date: 07/24/2024
7
7
author: hirenshah1
8
8
ms.author: hirshah
9
9
ms.reviewer: mimckitt
@@ -18,7 +18,7 @@ When you deploy a cloud service application package to Azure, you can obtain inf
18
18
19
19
You can find the **Properties** pane as follows:
20
20
21
-
* In the Azure portal, click the deployment of your cloud service, click**All settings**, and then click**Properties**.
21
+
* In the Azure portal, choose the deployment of your cloud service, select**All settings**, and then select**Properties**.
22
22
23
23
> [!NOTE]
24
24
> You can copy the contents of the **Properties** pane to the clipboard by clicking the icon in the upper-right corner of the pane.
@@ -27,44 +27,44 @@ You can find the **Properties** pane as follows:
## Problem: I cannot access my website, but my deployment is started and all role instances are ready
31
-
The website URL link shown in the portal does not include the port. The default port for websites is 80. If your application is configured to run in a different port, you must add the correct port number to the URL when accessing the website.
30
+
## Problem: I can't access my website, but my deployment is started and all role instances are ready
31
+
The website URL link shown in the portal doesn't include the port. The default port for websites is 80. If your application is configured to run in a different port, you must add the correct port number to the URL when accessing the website.
32
32
33
-
1. In the Azure portal, click the deployment of your cloud service.
33
+
1. In the Azure portal, choose the deployment of your cloud service.
34
34
2. In the **Properties** pane of the Azure portal, check the ports for the role instances (under **Input Endpoints**).
35
-
3. If the port is not 80, add the correct port value to the URL when you access the application. To specify a non-default port, type the URL, followed by a colon (:), followed by the port number, with no spaces.
35
+
3. If the port isn't 80, add the correct port value to the URL when you access the application. To specify a nondefault port, type the URL, followed by a colon (:), followed by the port number, with no spaces.
36
36
37
37
## Problem: My role instances recycled without me doing anything
38
-
Service healing occurs automatically when Azure detects problem nodes and therefore moves role instances to new nodes. When this occurs, you might see your role instances recycling automatically. To find out if service healing occurred:
38
+
Service healing occurs automatically when Azure detects problem nodes and therefore moves role instances to new nodes. When these moves occur, you might see your role instances recycling automatically. To find out if service healing occurred:
39
39
40
-
1. In the Azure portal, click the deployment of your cloud service.
40
+
1. In the Azure portal, choose the deployment of your cloud service.
41
41
2. In the **Properties** pane of the Azure portal, review the information and determine whether service healing occurred during the time that you observed the roles recycling.
42
42
43
-
Roles will also recycle roughly once per month during host-OS and guest-OS updates.
43
+
Roles recycle roughly once per month during host-OS and guest-OS updates.
44
44
For more information, see the blog post [Role Instance Restarts Due to OS Upgrades](/archive/blogs/kwill/role-instance-restarts-due-to-os-upgrades)
45
45
46
-
## Problem: I cannot do a VIP swap and receive an error
47
-
A VIP swap is not allowed if a deployment update is in progress. Deployment updates can occur automatically when:
46
+
## Problem: I can't do a VIP swap and receive an error
47
+
A VIP swap isn't allowed if a deployment update is in progress. Deployment updates can occur automatically when:
48
48
49
-
* A new guest operating system is available and you are configured for automatic updates.
49
+
* A new guest operating system is available and you configured for automatic updates.
50
50
* Service healing occurs.
51
51
52
52
To find out if an automatic update is preventing you from doing a VIP swap:
53
53
54
-
1. In the Azure portal, click the deployment of your cloud service.
55
-
2. In the **Properties** pane of the Azure portal, look at the value of **Status**. If it is**Ready**, then check **Last operation** to see if one recently happened that might prevent the VIP swap.
54
+
1. In the Azure portal, choose the deployment of your cloud service.
55
+
2. In the **Properties** pane of the Azure portal, look at the value of **Status**. If it's**Ready**, then check **Last operation** to see if one recently happened that might prevent the VIP swap.
56
56
3. Repeat steps 1 and 2 for the production deployment.
57
57
4. If an automatic update is in process, wait for it to finish before trying to do the VIP swap.
58
58
59
59
## Problem: A role instance is looping between Started, Initializing, Busy, and Stopped
60
-
This condition could indicate a problem with your application code, package, or configuration file. In that case, you should be able to see the status changing every few minutes and the Azure portal may say something like **Recycling**, **Busy**, or **Initializing**. This indicates that there is something wrong with the application that is keeping the role instance from running.
60
+
This condition could indicate a problem with your application code, package, or configuration file. In that case, you should be able to see the status changing every few minutes and the Azure portal may say something like **Recycling**, **Busy**, or **Initializing**. This fluctuation of status indicates that there's something wrong with the application that is keeping the role instance from running.
61
61
62
62
For more information on how to troubleshoot for this problem, see the blog post [Azure PaaS Compute Diagnostics Data](/archive/blogs/kwill/windows-azure-paas-compute-diagnostics-data) and [Common issues that cause roles to recycle](cloud-services-troubleshoot-common-issues-which-cause-roles-recycle.md).
63
63
64
64
## Problem: My application stopped working
65
-
1. In the Azure portal, click the role instance.
65
+
1. In the Azure portal, choose the role instance.
66
66
2. In the **Properties** pane of the Azure portal, consider the following conditions to resolve your problem:
67
-
* If the role instance has recently stopped (you can check the value of **Abort count**), the deployment could be updating. Wait to see if the role instance resumes functioning on its own.
67
+
* If the role instance recently stopped (you can check the value of **Abort count**), the deployment could be updating. Wait to see if the role instance resumes functioning on its own.
68
68
* If the role instance is **Busy**, check your application code to see if the [StatusCheck](/previous-versions/azure/reference/ee758135(v=azure.100)) event is handled. You might need to add or fix some code that handles this event.
69
69
* Go through the diagnostic data and troubleshooting scenarios in the blog post [Azure PaaS Compute Diagnostics Data](/archive/blogs/kwill/windows-azure-paas-compute-diagnostics-data).
In this article, you'll troubleshoot allocation failures where the fabric controller cannot allocate when deploying an Azure Cloud service (classic).
17
+
In this article, you troubleshoot allocation failures where the fabric controller can't allocate when deploying an Azure Cloud service (classic).
18
18
19
19
When you deploy instances to a Cloud Service or add new web or worker role instances, Microsoft Azure allocates compute resources.
20
20
@@ -29,7 +29,7 @@ In Azure portal, navigate to your Cloud service (classic) and in the sidebar sel
29
29
30
30
31
31
32
-
When you're inspecting the logs of your Cloud service (classic), you'll see the following exception:
32
+
When you inspect the logs of your Cloud service (classic), you see the following exception:
33
33
34
34
|Exception |Error Message |
35
35
|---------|---------|
@@ -54,9 +54,9 @@ Follow the guidance for allocation failures in the following scenarios.
54
54
55
55
### Not pinned to a cluster
56
56
57
-
The first time you deploy a Cloud service (classic), the cluster hasn't been selected yet, so the cloud service isn't *pinned*. Azure may have a deployment failure because:
57
+
The first time you deploy a Cloud service (classic), the cluster is unselected, so the cloud service isn't *pinned*. Azure may have a deployment failure because:
58
58
59
-
- You've selected a particular size that isn't available in the region.
59
+
- You selected a particular size that isn't available in the region.
60
60
- The combination of sizes that are needed across different roles isn't available in the region.
61
61
62
62
When you experience an allocation error in this scenario, the recommended course of action is to check the available sizes in the region and change the size you previously specified.
@@ -70,7 +70,7 @@ When you experience an allocation error in this scenario, the recommended course
70
70
71
71
### Pinned to a cluster
72
72
73
-
Existing cloud services are *pinned* to a cluster. Any further deployments for the Cloud service (classic) will happen in the same cluster.
73
+
Existing cloud services are *pinned* to a cluster. Any further deployments for the Cloud service (classic) happen in the same cluster.
74
74
75
75
When you experience an allocation error in this scenario, the recommended course of action is to redeploy to a new Cloud service (classic) (and update the *CNAME*).
76
76
@@ -102,4 +102,4 @@ For more allocation failure solutions and background information:
102
102
> [!div class="nextstepaction"]
103
103
> [Allocation failures - Cloud service (classic)](cloud-services-allocation-failures.md)
104
104
105
-
If your Azure issue isn't addressed in this article, visit the Azure forums on [MSDN and Stack Overflow](https://azure.microsoft.com/support/forums/). You can post your issue in these forums, or post to [@AzureSupport on Twitter](https://twitter.com/AzureSupport). You also can submit an Azure support request. To submit a support request, on the [Azure support](https://azure.microsoft.com/support/options/) page, select *Get support*.
105
+
If your Azure issue isn't addressed in this article, visit the Azure forums on [the Microsoft Developer Network (MSDN) and Stack Overflow](https://azure.microsoft.com/support/forums/). You can post your issue in these forums, or post to [@AzureSupport on Twitter](https://twitter.com/AzureSupport). You also can submit an Azure support request. To submit a support request, on the [Azure support](https://azure.microsoft.com/support/options/) page, select *Get support*.
0 commit comments