Databases
StackOverflow2013
Postsdbo
POAzure service dies after a few days
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POAzure service dies after a few days
    text
    copied!<p>I have Small size (x2) cloud service running and operating just fine for 4-6 days but then it becomes unresponsive and requires manual restart through Azure portal to get it back online.</p> <p>Windows event logs show that virtual memory is running low. After 2-3 days I start getting:</p> <blockquote> <p>Windows successfully diagnosed a low virtual memory condition. The following programs consumed the most virtual memory: WaIISHost.exe (3836) consumed 3810709504 bytes, CacheService.exe (1528) consumed 823902208 bytes, and w3wp.exe (1728) consumed 145485824 bytes.</p> </blockquote> <p>After a while services start failing (due to memory problem??):</p> <blockquote> <p>Application: CacheService.exe Framework Version: v4.0.30319<br> Description: The process was terminated due to an unhandled exception. Exception Info: Microsoft.ApplicationServer.Caching.ConfigStoreException<br> Stack: at Microsoft.ApplicationServer.Caching.CustomProviderProxy+&lt;>c_<em>DisplayClass5.b</em>_3(System.Object)<br> at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()<br> at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading.<em>ThreadPoolWaitCallback.PerformWaitCallback()<br> |http://schemas.microsoft.com/win/2004/08/events/event'>1026200x800000000000001138ApplicationRD00155D45A2ADApplication: CacheService.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception.<br> Exception Info: Microsoft.ApplicationServer.Caching.ConfigStoreException<br> Stack: at Microsoft.ApplicationServer.Caching.CustomProviderProxy+&lt;&gt;c</em>_DisplayClass5.&lt;PerformOperation&gt;b__3(System.Object)<br> at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()<br> at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()</p> </blockquote> <p>and eventually Http requests start failing:</p> <blockquote> <p>Process information:<br> Process ID: 3344<br> Process name: w3wp.exe<br> Account name: NT AUTHORITY\NETWORK SERVICE<br> Exception information:<br> Exception type: HttpException<br> Exception message: The paging file is too small for this operation to complete. (Exception from HRESULT: 0x800705AF) at System.Web.Compilation.BuildManager.ReportTopLevelCompilationException()<br> at System.Web.Compilation.BuildManager.EnsureTopLevelFilesCompiled()<br> at System.Web.Hosting.HostingEnvironment.Initialize(ApplicationManager appManager, IApplicationHost appHost, IConfigMapPathFactory configMapPathFactory, HostingEnvironmentParameters hostingParameters, PolicyLevel policyLevel, Exception appDomainCreationException)<br> The paging file is too small for this operation to complete. (Exception from HRESULT: 0x800705AF)</p> </blockquote> <p>I'm not sure if the problem is that virtual memory is configured too low, or is the use of the memory too high. WaIISHost.exe virtual memory use definitely looks quite high, but it seems to stabilize at around 4.1 GB.</p> <p>I do not know why WaIISHost.exe would need so much, since the Run() method is doing just very light housekeeping activities, such as pinging the site every few minutes to keep the Application running during daytime.</p> <p>Available Memory monitoring in Azure Portal shows the service to have 300-800MB of free memory during the whole period before the crash.</p> <p>Any ideas what is the problem? How can I configure virtual memory higher?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload