with 25 Grids its very annoying, second issue is when i unbox a server and restart ASM the Servers are checked again and inactive server start automatically again which causes the processor to be overloaded.Is that REALLY important? Are they not sorted, or are they sorted different than you want them to be. And really so what?
I have the same problem. The manager will crash/timeout and when restarting the app it thinks A1 is offline and keeps trying to boot it.Heres one... sometimes the manager crashes... and the server stay online.. the thing is that when i restart the manager it thinks that the servers are offline and try to boot them instantly. Is there no way that the manager detects that the servers are online?
Actually I am running on a Dell R820 with quad socket 8-core xeon processors with 256GB of ram. Your response is irrelevant. My question stands.You aren't running 30 grids on one instance or the server manager. So how many you have is irrelevant. And they all load faster if they are all started together. Yes, individually they do load faster, but sequentially it takes longer overall.
You can't have them running already when you start the tool. Simple solution... wait for an update to drop. Shut the entire map down to update, update, launch the server manager, and let it do its thing.
Unfortunately, with the current version, I personally have a constant restart issue. Its detecting a new update that doesnt exist. I wouldnt even try to use it until its updated again!
[03:58] [Atlas] Checking for updates, can take up to 30 seconds... [03:58] [Atlas] BuildID 3484235 Released! [03:58] [Atlas] Current BuildID: 3487616, Updating To BuildID: 3484235 [03:58] [Atlas] Updated, Launching Servers if offline!
You are truly insufferable.Literally, NO ONE cares what your running! The point is that it's assinine to run it the way you are and then complain that it's doing what it's doing! Rolling out a huge chunk of restarts at once is not only not smart, but not good for the overall server's appearance. Rolling restarts across several instances of some form of management prog leads to less stress, ZERO downtime, and less issue when PART of the grid goes down for a crash. But hey... you do you and complain about issues. I'll sit back and enjoy the lack there-of.