Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, January 1, 2015 11:17 AM
Hi
I'm an MSDN subscriber using Azure for last 20 months or so. I have a VM (Win Server 2012) which is serving some web sites and went offline (unresponsive) at 13.30 on 31/12/2014 (around 22 hours ago).
First port of call is to try RDP - stuck on "Securing remote connection...".
Check IP address hasn't changed, in Azure Management Portal. It hasn't, so I'm definitely trying to connect to the right server.
Next step, try restart of virtual machine through Management Portal.
Restarting message keeps showing for more than 20 minutes.
Open new instance of Management Portal and click Restart and below message is shown.
"Another reboot or reimage operation is already in progress on role instance ......"
It looks like Azure cannot restart the server any more.
I have domain names pointed at the server so don't want to lose the IP address and endure another 24 hours of outage with DNS changes.
Because I'm an MSDN subscriber I have no access to Azure support.
Can anyone please suggest what I can do next?
I don't want the hassle of changing providers but the Azure Portal does seem pretty unreliable. This is not the first issue I've had with it and when you factor in the outage in November, I can't help but think that Amazon would be a better place to be.
Any thoughts on that appreciated also.
Thanks a lot
Andy
All replies (5)
Thursday, January 1, 2015 2:04 PM ✅Answered
I eventually got this sorted.
I ran the Stop-AzureVM command again after waiting for another 15 minutes. After 45 minutes I saw that in the Azure Management Portal the server was Stopped (but not deallocated). The command itself didn't complete and I had to cancel it in the end after 75 minutes (see below).
Looking at Event Viewer it seemed that Windows Update could've caused a problem as the server outage was some 10 hours after a Windows Update rollback, but there were a few messages I wouldn't have expected to see in the Event Viewer (also below).
PS C:\ Stop-AzureVM -ServiceName "andytlive" -Name "andytlive" -StayProvisioned -Force
VERBOSE: 11:54:49 - Completed Operation: Get Deployment
VERBOSE: 11:54:49 - Begin Operation: Stop-AzureVM
Stop-AzureVM : InternalError : The server encountered an internal error. Please retry the request.
At line:1 char:1
- Stop-AzureVM -ServiceName "andytlive" -Name "andytlive" -StayProvisioned -Force
-
+ CategoryInfo : CloseError: (:) [Stop-AzureVM], CloudException
+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.StopAzureVMCommand
VERBOSE: 13:10:53 - Completed Operation: Stop-AzureVM
The system time has changed to 2014-12-31T07:39:57.431000000Z from 2014-12-31T07:39:57.436782800Z.
Change Reason: An application or system component changed the time.
The IO operation at logical block address 0x22d6e3f for Disk 0 (PDO name: \Device\Ide\IdeDeviceP0T0L0-0) was retried.
The IO operation at logical block address 0x1e88140 for Disk 0 (PDO name: \Device\Ide\IdeDeviceP0T0L0-0) was retried.
Any thoughts or feedback appreciated. In my mind, the Azure Management Portal should be able to restart a server regardless of that servers state simply by power cycling it.
Andy
Thursday, January 1, 2015 11:29 AM
After the restarting operation from the Azure portal times out I receive this message.
"Failed to restart virtual machine andytlive."
Thursday, January 1, 2015 11:30 AM
I'm now going to try installing the Azure Powershell tools and then to stop the VM with the StayProvisioned flag.
Andy
Thursday, January 1, 2015 11:40 AM
It seems that the Stop command won't work, hopefully this is a temporary thing until Azure gives up on the reboot operation.
PS C:\ Stop-AzureVM -ServiceName "andytlive" -Name "andytlive" -StayProvisioned
VERBOSE: 11:38:08 - Completed Operation: Get Deployment
VERBOSE: 11:38:09 - Begin Operation: Stop-AzureVM
Stop-AzureVM : ConflictError: Another reboot or reimage operation is already in progress on role instance andytlive.
At line:1 char:1
- Stop-AzureVM -ServiceName "andytlive" -Name "andytlive" -StayProvisioned
-
+ CategoryInfo : CloseError: (:) [Stop-AzureVM], CloudException
+ FullyQualifiedErrorId : Microsoft.WindowsAzure.Commands.ServiceManagement.IaaS.StopAzureVMCommand
VERBOSE: 11:38:10 - Completed Operation: Stop-AzureVM
PS C:\
Friday, January 2, 2015 8:32 AM
Hi Andy,
Good to hear that.
Which region is that VM in? I cloud not shut down my VM in the Azure management portal just now and I can use Azure PowerShell commands to stop it.
In addition, if you stop a VM using the Stop-AzureVM cmdlet with the -StayProvisioned parameter, then the VM still has reserved resources and it will keep the IP address, and it will be in the stopped status.
Best regards,
Susie
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].