CloudatCost Issues
-
@thecreativeone91 said:
I haven't noticed any issues with my BigDog Instance. Likely there are simply less of those competting for resources.
Presumably that means that there are dedicated servers for BigDogs and different ones for Dev1s. Completely possible, just saying.
-
Random.. But I wonder if I can get Zimbra to work on a BigDog 1 instance. It would just be me using it.
-
@thecreativeone91 said:
Random.. But I wonder if I can get Zimbra to work on a BigDog 1 instance. It would just be me using it.
It's our Zimbra server, running on a BigDog, that I am testing the performance on as we speak! That's a bizarre coincidence.
-
@thecreativeone91 said:
Random.. But I wonder if I can get Zimbra to work on a BigDog 1 instance. It would just be me using it.
http://mangolassi.it/topic/4029/building-zimbra-on-centos-7-on-cloudatcost
-
Anyone else having issues with changing the run mode. All my others worked fine. On this Dev 1 instance, when I click the Modify drop down all the other menu items are clickable however when over the run mode the cursor just changes to a normal pointer.
-
@thecreativeone91 have not seen that happen yet.
-
@thecreativeone91 said:
Anyone else having issues with changing the run mode. All my others worked fine. On this Dev 1 instance, when I click the Modify drop down all the other menu items are clickable however when over the run mode the cursor just changes to a normal pointer.
I have the same issue with the minecraft server! Guess it goes down in 7 days
-
@scottalanmiller said:
@thecreativeone91 have not seen that happen yet.
I ended up having to re-image it, hopefully that fixes it. I could SSH/VNC(Console) to it however the password given in the panel did not work so something was not right in the imaging. My BigDog 1 has been stuck re-imaging from Windows 2012 to CentOS 7 for the past hour though.
-
I think that the "mode" thing needs to be removed. It is confusing and who actually wants that? I think that it adds risk and complication but I'm not seeing the value.
-
@scottalanmiller said:
I think that the "mode" thing needs to be removed. It is confusing and who actually wants that? I think that it adds risk and complication but I'm not seeing the value.
I think it adds value to the C@C business though, but not the consumer, it allows C@C to plan for overages with the assumption that a certain percentage of servers are built to test one thing, with this added precaution it prevents those servers from running forever and using resources that could be allocated to something else.
That being said, as a consumer I really wish they didn't have it.
-
@scottalanmiller said:
I think that the "mode" thing needs to be removed. It is confusing and who actually wants that? I think that it adds risk and complication but I'm not seeing the value.
If people forget they have them it allows C@C to just have them turned of not using any resource aside from disk space. Otherwise there is no value.
-
My benchmark tool is still running. That's crazy.
-
@Aaron-Studer said:
@thecreativeone91 said:
Anyone else having issues with changing the run mode. All my others worked fine. On this Dev 1 instance, when I click the Modify drop down all the other menu items are clickable however when over the run mode the cursor just changes to a normal pointer.
I have the same issue with the minecraft server! Guess it goes down in 7 days
I was able to get it to work in Firefox. It seems there is an issue with there php. When I have three instances the last one on the page in every other browser has that issue.
-
Finally the report is done. Here is the BigDog running CentOS 7:
ServerBear Benchmark CloudatCost BigDog
UnixBench score: 1833.7
I/O rate: 10.0 MB/second
Bandwidth rate: 6.3 MB/second -
Still having issues getting them to image properly.
-
@thecreativeone91 said:
Still having issues getting them to image properly.
I had one that I had to do three times.
-
@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.
