CloudatCost Issues
-
@scottalanmiller said:
@thecreativeone91 said:
Still having issues getting them to image properly.
I had one that I had to do three times.
I think I'm on the 4th time with both my Dev 1 and Big Dog 1. They are taking over an hour each time.
-
Well the Big Dog 1 finished imaging. It is taking quite a long time to even boot it though. So I'm guessing there's major issues with Disk IO again.
-
If they take more than five minutes, restart. They are not going to work (I am pretty sure) if they take very long.
-
@thecreativeone91 said:
Well the Big Dog 1 finished imaging. It is taking quite a long time to even boot it though. So I'm guessing there's major issues with Disk IO again.
From the benchmark that Scott posted they have very little IO to begin with - I'd be patient and let it run for a bit.
-
@scottalanmiller said:
If they take more than five minutes, restart. They are not going to work (I am pretty sure) if they take very long.
It finally came up.
-
@thecreativeone91 and it is working?
-
Ubuntu login problems solved. This is undocumented and needs to be fixed. CloudatCost is using the user user rather than root. This is confusing. The password shown on the console is for user, not root. It says this nowhere. You have to figure it out by getting onto the system and poking around, guessing and testing. If you use user instead of root, it just works.
-
@scottalanmiller said:
Ubuntu login problems solved. This is undocumented and needs to be fixed. CloudatCost is using the user user rather than root. This is confusing. The password shown on the console is for user, not root. It says this nowhere. You have to figure it out by getting onto the system and poking around, guessing and testing. If you use user instead of root, it just works.
That makes since since root login is disabled by default on Ubuntu. Not sure why they don't give you the username.
-
Odd. It would not take much to show that on the panel .
-
One of my Instances disappeared from the panel today. Not sure what's up with it. Can't get to it either.
-
That's a new one. Very odd.
-
It looks like it's back now, but it was up and running Zimbra. Now it says imaging failed and I have to image it again. odd. Oh well.
-
I can't open the console (connection time outs) and I appear to have had very large memory utilisation 97% for I don't know how long (no monitoring software yet).
Memory is back down to 39%. I'm not sure if my forced reboot helped at all.Edit: upon reflection, I believe that the console access might be because of a firewall between my network and the greater Internet.
-
@nadnerB Can you access it via either console or SSH at all?
-
@nadnerB said:
I can't open the console (connection time outs) and I appear to have had very large memory utilisation 97% for I don't know how long (no monitoring software yet).
The panel doesn't show anything useful for memory utilization. It literally means nothing. There is no reason to believe you were using much memory.
-
@thecreativeone91 said:
It looks like it's back now, but it was up and running Zimbra. Now it says imaging failed and I have to image it again. odd. Oh well.
Have you tried clicking the Events button in the panel to see if anything odd shows there?
Servers that mysteriously reimage themselves is alarming. Anyone from there care to comment? @AmanBhogal? @charlie?
-
@Danp it didn't reimage itself just failed. I'm guessing due to the io issues, and needed to be reimaged. They likely can re-connect the virtual disk if you contact them instead of re-imaging it but I didn't care since its just testing.
-
@thecreativeone91 said:
@nadnerB Can you access it via either console or SSH at all?
I can now that I'm at home. At work, the ports seem to be blocked and because of our network setup, unblocking isn't going to happen
-
Install pending for 3 hours now.....
-
@Aaron-Studer install of what?
