MSSQL1 is seeing some abuse right now and we are working on it.
I will need to reboot it here shortly there will be about 5 minutes out while I reboot.
it is coming up after the reboot now, sometimes on a reboot it does a shutdown instead of restarting, and it did in this case so I had a blank screen on KVM had to login to the power system and issue a power cycle to get it back up adding a minute or so to the reboot time.
DBs are up and going well now, we are watching for any return of abuses on it.
I have found the source of the abuse as well, a full DB making a loop of errors, fixing it promptly.