HAAALLLLLPP!! SYSTEM DOWN!!!! 14,000 CLIENTS NO ONE WORKING!!!!I don't have to look at the account field. I know this one's Mookman. I'm also pretty sure it's going to be all sorts of stupid, it being a Prio-1. I'm guessing they pulled the engine and prop off a Cessna and don't understand why it won't fly anymore.
And... I'm right.
We are hit by critical Issue, $YourBigApp is down. We are unable to startup application even after recycle services.Mmm-hmm... and what did you change between it all working last night and it not working this morning, Mookman? I know I shouldn't ask this because I know that the answer I'm going to get is exactly what I should expect from MildlyNaughtyPuppy in a few years hence when I notice my computer has been "fixed" while I was in the kitchen pouring out bowls of chow for the pack. I can handle getting this response from a toddler, not so much so from an "administrator". But I have to ask. It's part of The Method.
The Login page itself does not appear. We use Siteminder for systems Authentication.
Exactly which "nothing" was changed overnight?
We just did a release and infer this issue is occuring after this, but need to confirm. THe components for the release are only PrimeComponent and CentralCommunicationsSystemYou need to confirm that the system which was working perfectly last night only stopped working after you changed out the exact things that would stop it working now and that the problem hasn't perhaps been caused by fairies or my bad attitude? Put the system back the way it was and fer chrissakes start debugging your fucking changes before rolling out to production!
We dont want to return to older version and must confirm this is not a new defect on $YourBigAppConfirmed.
Resolution: Patch back to prior version.
Close: Root Cause: 17-Fuckwit.