CloudatCost Issues
-
@Dashrender said:
lol I know that, I was mainly asking the second part of my question, in the assumption that our VM is doing what it should.. why does it show a higher than expected IO load?
Is it aware of the other loads around it on the host?Oh, I see. It doesn't show IO load. It shows IOWait state - the amount of time in which the CPU is stuck just waiting for IO to respond. So we have no idea what the load is, we only know that it can't respond to us.
-
@scottalanmiller said:
@Dashrender said:
lol I know that, I was mainly asking the second part of my question, in the assumption that our VM is doing what it should.. why does it show a higher than expected IO load?
Is it aware of the other loads around it on the host?Oh, I see. It doesn't show IO load. It shows IOWait state - the amount of time in which the CPU is stuck just waiting for IO to respond. So we have no idea what the load is, we only know that it can't respond to us.
Aww.. ok great, nice lightbulb moment for me.. Thanks!
-
If the storage was super slow, like it had a carrier pigeon interface, it would show up as having high IOWait but low load. But with SSDs, we assume they are over loaded.
-
This post is deleted! -
What is a SAR report? How do I get one?
-
@Aaron-Studer said:
What is a SAR report? How do I get one?
In Linux the command to get it is simply sar.
Ta da!
-
If you are missing the sar utility, it means that you forgot to install the sysstat utilities.
Either...
yum -y install sysstat
Or...
apt-get install sysstat
If you are on Ubuntu 14.04.2 LTS they do this ridiculous thing that it doesn't turn on my default. Run sar and it will tell you what to change to enable it. It's just editing one file to change a false to a true.
-
@scottalanmiller I always run CentOS7, per your recommendation
-
@Aaron-Studer said:
@scottalanmiller I always run CentOS7, per your recommendation
Good man. Just the yum and then it takes care itself. Nothing more to do. Report is blank for the first ten minutes after installing. It gets more useful over time. After an hour or so you'll have really useful data.
-
So what would be a reasonable time frame to fix such a issue?
-
Great, I just reset my Dev3 box and tried to connect to the console and it told my my attempt was logged for attempted hacking.. nice!
-
@Dashrender said:
Great, I just reset my Dev3 box and tried to connect to the console and it told my my attempt was logged for attempted hacking.. nice!
What gave you that message? Do you have a screenshot?
-
@scottalanmiller said:
@Dashrender said:
Great, I just reset my Dev3 box and tried to connect to the console and it told my my attempt was logged for attempted hacking.. nice!
What gave you that message? Do you have a screenshot?
I didn't grab one.. but I tried again and I see that it's still rebuilding my re-image...
-
Rebuilding a VM now seems to take about 30 minutes.
-
-
Should take under five minutes. I've reported the rebuild fail issues and they are looking into it. Just rebuild again if it doesn't work promptly. Doesn't hurt anything.
-
@scottalanmiller said:
Should take under five minutes. I've reported the rebuild fail issues and they are looking into it. Just rebuild again if it doesn't work promptly. Doesn't hurt anything.
I've seen some long rebuild times too, but I'm in no real rush so it didn't bother me...
-
After the re-image completed I still can't access the VM. Has been over a hour now.
-
Is that the correct IP address? They do change every time you reimage the VM...
-
@Aaron-Studer said:
After the re-image completed I still can't access the VM. Has been over a hour now.
What does the console say? We've seen the rebuilds fail, sometimes you have to re-image more than once before it is ready. Getting this verified before it reports that it is done is one of the things that we've talked about with them and that they are looking into.