I created a Standard B1s Windows VM instance where I'm running OpenSSH service and using it as a SFTP server.
All works perfectly fine for about 2 hours, I can RDP to the VM nicely and SSH connection works fine.
After about 2 hours the connection to VM becomes very slow in a way that RDP takes around a minute and SSH connection times out every time.
What fixes a problem for a short time is restarting the VM or resizing it to any other tier. Then again everything works fine for about 2 hours, then problem appears again.
I'm aware that B1s is a Burst type VM but we are using it as simple SFTP server where 2-3 times a day one document will be uploaded. So no high CPU or Memory occupancy is needed. I also tried resizing it to non B-class VM, but the problem is the same. We are located in East USA and server is also located in that Azure region.
Any help is appreciated! Thanks
Try accessing the VM from somewhere else. Maybe its a network related problem? Create a VM in Europe West and execute the same operations. If this is causing no issues then I would try to dig deeper in network related topics.
Related
For context, we have an Azure Virtual Machine that we use to test our app before pushing the changes to production. This VM automatically shutdown every evening to save some energy. Is there a way to make it start when trying to access its DNS name (******.cloudapp.azure.com)? It would be better than starting it at a fixed time every morning but if it is impossible or too complicated, is there a way to make it start at a specified time?
Starting the vm using events requires some changes in your architecture.
You can start a vm at fixed time using automation accounts. Look at this tutorial on Microsoft learn to accomplish your goal
https://learn.microsoft.com/en-us/azure/automation/automation-solution-vm-management-config
If you had a firewall in front off your VM you could log the HTTP 404 events, then trigger a function that started your VM.
But it is not trivial and the firewall would add extra cost (it may be more expensive than your VM)
So the best way is probably just to start the VM at a fixed time.
If you need the VM permanently you could look into Reserved instances to save costs. It could save you upto 80% https://azure.microsoft.com/en-us/pricing/reserved-vm-instances/
We've got a classic VM on azure. All it's doing is running SQL server on it with a lot of DB's (we've got another VM which is a web server which is the web facing side which accesses the sql classic VM for data).
The problem we have that since yesterday morning we are now experiencing outages every 2-3 hours. There doesnt seem to be any reason for it. We've been working with Azure support but they seem to be still struggling to work out what the issue is. There doesnt seem to be anything in the event logs that give's us any information.
All that happens is that we receive a pingdom alert saying the box is out, we then can't remote into it as it times out and all database calls to it fail. 5 minutes later it will come back up. It doesnt seem to fully reboot or anything it just haults.
Any ideas on what this could be caused by? Or any places that we could look for better info? Or ways to patch this from happening?
The only thing that seems to be in the event logs that occurs around the same time is a DNS Client Event "Name resolution for the name [DNSName] timed out after none of the configured DNS servers responded."
Smartest or Quick Recovery:
Did you check SQL Server by connecting inside VM(internal) using localhost or 127.0.0.1/Instance name. If you can able connect SQL Server without any Issue internally and then Capture or Snapshot SQL Server VM and Create new VM using Capture VM(i.e without lose any data).
This issue may be occurred by following criteria:
Azure Network Firewall
Windows Server Update
This ended up being a fault with the node/sector that our VM was on. I fixed this by enlarging the size of our VM instance (4 core to 8 core), this forced azure to move it to another node/sector and this rectified the issue.
One of my 10 Azure VMs running windows has suddenly became inaccessible! Azure Management Console shows the state of this VM as "running" the Dashboard shows no server activity since my last RDP logout 16 hours ago. I tried restarting the instance with no success, still inaccessible ( No RDP access, hosted application down, unsuccessful ping...).
I have changed the instance size from A5 to A6 using the management portal and everything went back to normal. Windows event viewer showed no errors except the unexpected shutdown today after my Instance size change. Nothing was logged between my RDP logout yesterday and the system startup today after changing the size.
I can't afford having the server down for 16 hours! Luckily this server was the development server.
How can I know what went wrong? Anyone faced a similar issue with Azure?
Thanks
there is no easy way to troubleshoot this without capturing it in a stuck state.
Sounds like you followed the recommended steps, i.e.:
- Check VM is running (portal/PowerShell/CLI).
- Check endpoints are valid.
- Restart VM
- Force a redeployment by changing the instance size.
To understand why it happened it would be necessary to leave it in a stuck state and open a support case to investigate.
There is work underway to make both self-service diagnosis and redeployment easier for situations like this.
Apparently nothing is wrong! After the reboot the machine was installing updates to complete the reboot. When I panicked, I have rebooted it again, stopped it, started it again and I have even changed its configuration thinking that it is dead. While in fact it was only installing updates.
Too bad that we cannot disable the automatic reboot or estimate the time it takes to complete.
We have set up a small AZURE VM (plain windows 2012 R2 image as provided by Microsoft) with a lightweight DEMO application that happily runs with SQLExpress and 1GB RAM. This VM did run quite fine for a month. A few days ago we shut down the VM and the cloud service to save some credits until we need the demo again.
Today the VM refuses to start and cycles continuously between "stopped", "starting" and "stopped (could not start)".
No useful error detals are listed but the operation logs of the management service notes
<OperationStatus>
<ID>98502f34-08bd-70a3-b0c3-f7e08976dd38</ID>
<Status>Failed</Status>
<HttpStatusCode>500</HttpStatusCode>
<Error>
<Code>InternalError</Code>
<Message>The server encountered an internal error. Please retry the request.</Message>
</Error>
</OperationStatus>
Can i expect that this situation will eventually resolve by itself or is there any other measure I could try to get my VM up and running again? It is no option to download the 20GB virtual disk to examine it locally and upload it again. This would take forever and a day.
Are the AZURE services just crap?
If you haven't already tried it, a typical workaround step is to delete the failing VM (keeping the disk/stateful information intact!) and then recreate it using the same disk.
We are having a VPC setup for our staging environment. In this we have attached an elastic ip to one instance & rest of the instances are connected through this.
Now today when we restarted our machines we are facing trouble running commands like top, vi, ps etc.
Also we have noticed that if we connect to secondary machines via their public ip then everything is working fine. However if we connect via primary machine then the screen hangs after the command is issued.
Having a hard time debugging the root cause. Any suggestions will be quite helpful.
Sorry for inconvenience. The problem was with our office network. It started automatically after sometime.