I have a vm on Windows Azure running centos6 as dev node, and have recently experiencing a huge increase in outgoing traffic.
VM was stopped and after started by 1 day it shows 236.63 GB on outgoing traffic, server not running any applications, only 1 landing page.
need help how to detect what causing the traffic and how to prevent it, since it's reflecting badly on my bill.
Related
I am using ASP .NET SignalR to create a realtime game in the browser. It seems to run fine, other than occasional stutters on the display output.
I first noticed this when I deployed my application to a virtual PC in the cloud. To rule out bandwidth issues, I then deployed it to another virtual PC running locally.
Even when running the application from a virtual PC locally, I still get the stutters.
This issue does not happen when I run the application on local host using IIS express.
This makes me think that the issue has something to do with IIS, since both the cloud virtual PC and local virtual have this in common and local host does not.
After Googling I found lots of people advising to check certain settings in IIS.
These websocket settings were listed as possible culprits:
I don’t see any issues there though.
Another suggestion was to check the queue length in the advanced settings of the App Pool. Currently it is 1000. I believe that this is enough, as according to Perfmon, the number of requests received peeks at about 100 per second and sent at 80.
Has anyone else got any ideas?
I am using SignalR for ASP .NET 2.4.1 and IIS 10
Thanks
Looks like I blamed IIS wrongly, after further investigation I found the issue is most likely due to high CPU usage.
I ran Perfmon, and looked at the '%Processor Time' counters, and noticed that the application is frequently at 100%.
We newly setup Microsoft Azure 1core VM (Region SouthEastAsia) running a website. When we try to access home page from India, it loads after a considerable delay of 3sec to 7sec when there was no load on the server. The delay is consistent, and observed for other pages also.
firebug screen shows waiting time around 1600 ms
Q1: Is this a known network latency issue with Azure ?, if no How can we reduce the latency?
Q2: What is the Microsoft KPI for network latency ?
Environment:
Azure VM: Basic_A1 (1 core, 1.75 GB memory)
Application: LAMP stack (Apache1,php,Mysql)
OS: Ubuntu 14.04 LTS
Region: SouthEastAsia
Accessed from: India
The response size of the home page: 1.4 MB.
Observations:
1. Not a processing delay: We did a wget http://localhost/ on the server, and the page download was done within 700ms
Previously we had same setup with other vendor, the page load took less than 1sec
azure 2 core machine also has the same latency.
I suggest you to first log into an Azure VM and see if you do notice a time latency to the Website. Also you could check from a different ISP and see if the issue persists.
You should try two things:
Check Your site with http://tools.pingdom.com/fpt/ and give us an output (may be as image).
Check performance both with azure host name and Your own host name and compare results.
We have a Microsoft DC R2 server running only an Interbase database application, all works fine and we can access this application via both Point to Site and Site to Site VPN.
Our transfer speeds for files is coming in at about 5Mbps which is fantastic.
When we access our software (locally) which pulls data from the server (Azure) we're seeing it clock speeds of about 125KBps.
This results in a 3-6 second wait before the dataset appears on screen within our application.
In a local environment this is done within 0.5 seconds.
I'm trying to get to the bottom of the issue as the Internet connection we are on is a 100Mbps feed.
I look at the Draytek router and assumed that this was the problem, however we have tested from multiple sites and ISPs and can't seem to get any improvement on application DB access speeds. SMB speeds remain impressive.
We're not too experienced in the Azure area but we can't work out any way of improving those speeds, if anybody has any suggestions that would be fantastic.
FYI We're using an A2 Windows deployment (approx 4Gb).
Regards,
Pottre11
I have 2 VM machines on Azure.
One suddenly stopped responding.
It was down for around 30 minutes, until I just browsed into the Azure portal, and then I saw it was in the Starting state, and then it was up & running again.
How can I tell why my VM was shutdown?
EDIT: I'm assuming you're talking about Virtual Machines (IaaS), and not Cloud Services (PaaS).
Virtual Machines can, and will, restart, for several reasons. For example:
Hardware failure, where your Virtual Machine will then be restarted on another server.
Host OS refresh. This is the operating system running the physical server.
Some type of OS crash
Also keep in mind: Virtual Machines are in Preview with no SLA today. So there wouldn't be any information readily available to you for determining why your Virtual Machine became unavailable.
If it was unavailable for 30 minutes, then this hints at something akin to a host OS update or your virtual machine being moved. If it was down for, say, 5 minutes, then I'd guess it was an OS crash.
UPDATE I just looked at the Azure Dashboard which is showing degraded Compute with Virtual Machines (see RSS feed with problem description). Perhaps this is the root cause of your particular outage...
there are several things that might cause this to happen, your VM may have been crashed due to bad coding or bad development, the second reason I think is that the number of VM you created is not enough to the incoming traffic. this could cause your VM to restart if the number of incoming traffic is more than the number of VMs can handle.
Very suddenly without any changes or recent access my Azure virtual server is no longer available for RDP or web...I have logged into the azure control panel and everything appears to running without issue but it is not working.
I have checked the end points and they are present for both RDP and Web, totally weird.
I have 2 virtual servers and the other one is working fine and responding.
Anyone ever experience this? Just when my client wants to view his website as well...
http://cn-web-02.cloudapp.net is the URL
TIA
As I just answered for this question, Virtual Machines are in Preview and not in Production yet. There are several reasons why your Virtual Machines became unavailable (see other answer). Given that this is the second reported incident here today, it's a good guess it's related to the underlying Host OS being updated, which would take your Virtual Machine offline for a short period of time.
I tried your URL and it's available again. Just remember about this being in Preview, especially since you mention having a client that wants to view his website. If you put a production website in Virtual Machines, then you'll have to absorb the risk of not having an SLA.
Having said that: You can mitigate downtime risk by running two Virtual Machines, listening on a load-balanced input endpoint. Be sure to have both Virtual Machines in the same Availability Set. Doing that ensures that the Windows Azure fabric controller will not take both Virtual Machines offline at the same time when doing things like Host OS updates. If this were in Production, you'd then have a very high availability scenario. Even in Preview, you'll improve availability by taking advantage of Availability Sets. Note: You'll need to use some type of shared session cache, since visitors will now be sent to either one of your Virtual Machines.
I had same experience on it! We had 2 instances and all of its were re-imaged without any notified. I known it since we made some local change via RDP.
Reboot or Reimage may help! You may try!
Turns out it was an outage from Microsoft...for over 22 hours but everything is back up and running. This is the 2nd time in 6 months this has happened for long stretches...makes me a little nervous to say the least.
Thanks for the input everyone and for anyone that's interested MS have a good site that tracks the service levels on Azure. Windows Azure Service Dashboard
S