I recently came across an error during a deployment to one of our Content Delivery App Service instances - stopping the deployment process dead in its tracks.
The error occurred when deploying to the CD Slot:
This occurred each time we attempted to deploy this step.
The error in full does indicate troubleshooting codes and links (oddly enough, the Microsoft link did not have any trace of the error code):
I found it especially strange given that we saw no indication that we've hit any limit on storage space in Azure Portal. Initially, I thought it may have something to do with storage on the build server, but was able to quickly rule out this theory by verifying that there was plenty of disk space remaining on that machine.
The error was also evident when I attempted to upload any file directly via FTP:
I began a look for some giant file(s) that may be preventing any additional files from being uploaded (since that's what made the most sense given the context of the error message itself).
By logging into the App Service via FTP, I was able to identify two IIS memory dumps located in the /LogFiles directory. These both appear to have been taken the month prior - and simply never removed.
After deleting both memory dump directories, I was able to restart the deployment step - which completed without errors. Direct FTP uploads were also restored.
By leaving the remnants of these IIS memory dumps on the App Service's storage, we must have surpassed that storage limit.
This brings up some interesting questions:
First, based on the configured pricing tier, is there a limit on how much Sitecore can store in App_Data/MediaCache or /temp folders before hitting that cap?
I assume the answer to that is yes - if your application is not setup to periodically clean stale files (which it should by default), it's possible to reach that storage limit and cause this error to surface. In that case, the quick fix to get your deployment out would be to remove some or all temp files in the application.
Second, how can we monitor this storage limit of App Services in Azure Portal?
I'll have to circle back on this one as I don't quite have the answer to it. It may even already exist, and I just haven't spotted it yet. I'll update this post if I do figure that one out, but please let me know if you have the answer in the comments!
The error occurred when deploying to the CD Slot:
This occurred each time we attempted to deploy this step.
The error in full does indicate troubleshooting codes and links (oddly enough, the Microsoft link did not have any trace of the error code):
I found it especially strange given that we saw no indication that we've hit any limit on storage space in Azure Portal. Initially, I thought it may have something to do with storage on the build server, but was able to quickly rule out this theory by verifying that there was plenty of disk space remaining on that machine.
The error was also evident when I attempted to upload any file directly via FTP:
I began a look for some giant file(s) that may be preventing any additional files from being uploaded (since that's what made the most sense given the context of the error message itself).
By logging into the App Service via FTP, I was able to identify two IIS memory dumps located in the /LogFiles directory. These both appear to have been taken the month prior - and simply never removed.
After deleting both memory dump directories, I was able to restart the deployment step - which completed without errors. Direct FTP uploads were also restored.
What's up with that?
Well, your Azure App Services is tied to a particular pricing tier that dictates storage, memory, ACU, etc. In our case, this particular App Services is configured to use the Standard standard tier - which has a 50GB limit.By leaving the remnants of these IIS memory dumps on the App Service's storage, we must have surpassed that storage limit.
This brings up some interesting questions:
First, based on the configured pricing tier, is there a limit on how much Sitecore can store in App_Data/MediaCache or /temp folders before hitting that cap?
I assume the answer to that is yes - if your application is not setup to periodically clean stale files (which it should by default), it's possible to reach that storage limit and cause this error to surface. In that case, the quick fix to get your deployment out would be to remove some or all temp files in the application.
Second, how can we monitor this storage limit of App Services in Azure Portal?
I'll have to circle back on this one as I don't quite have the answer to it. It may even already exist, and I just haven't spotted it yet. I'll update this post if I do figure that one out, but please let me know if you have the answer in the comments!
