Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Windows Azure Infrastructure Services (IaaS) has only been in General Availability (GA, or <em>production</em>) about 3 weeks, since April 16 (see announcement <a href="http://weblogs.asp.net/scottgu/archive/2013/04/16/windows-azure-general-availability-of-infrastructure-as-a-service-iaas.aspx" rel="nofollow">here</a>). Prior to GA, there was no SLA and you would have seen more frequent OS restarts as various patches were still being applied to the Host OS. Are you saying that this pattern has continued at the same velocity since April 16?</p> <p>Now that IaaS is GA, I wouldn't expect 4 restarts in a week. That said: there are several reasons you'd see a restart:</p> <ul> <li>Host hardware failure (this takes down all Guest OSs running on that host)</li> <li>Host software update (and only if requiring a restart of the Host os). <em>Host OS reboots shouldn't be happening at the frequency you're seeing.</em></li> <li>Guest OS issues. Here's where things depart from PaaS (web/worker role Cloud Services). In IaaS, there's no Guest OS maintenance done by Azure; this is all in your hands. It's possible to get reboots if installing Windows Updates automatically. Possibly you could be running into an application-level issue causing the box to become unresponsive for a long period of time, resulting in the Azure fabric controller rebooting your box as it thinks it's unhealthy. And... your app could be somehow crashing the box.</li> </ul> <p>If you've ruled out application error and are sure the VMs are in good health at the time they're rebooting, you may need to open a support ticket with Microsoft to help diagnose the issue further.</p>
 

Querying!

 
Guidance

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