Love a good ol scream test. Only problem is you have to make sure to keep the disconnected thing or the data within for a solid year in case it's only used once annually by "very important process that makes sure the doors stay open" and no one realizes that thing you disconnected is where it's pulled from. Learned that one the hard way
post
With scream tests I unusually unplug the nic or whatever the equivalent is in a VM because a server can always have weird startup requirements that no one knows anymore while an unplugged nic doesn't change the running state if you need to bring it back online.
We left that shit running and blocked it with ACLs on the switch.
The guests are kinda black-box stuff to us. Don't want to mess with em.
What would you do if the power went out? Or you needed to upgrade the kernel?
Everything was on a ups with enough run time to turn the genny on.
As for updates, that wasn't my problem.
That's an unplanned power outage. A scream test would be a planed test. You also should do the email to all departments to see who knows what they are for and what you are doing. Usually gets the managers in a panic and those emails runs up and down the chains faster than "can you tell me what srv-15935 does"
Is the official name for this "the scream test"?
I do this in lots of jobs; I tend to come in on cleanup jobs after gross incompetence, sometimes for many years. In addition to fixing problems, I have to help companies learn what should be happening and realign them to normal operating practices. Stopping pointless, worthless, outdated and redundant practices are something I do, and sometimes I apply the method above, though with many fewer degrees of separation than you have to those who may be affected. I find cutting pointless stuff to be one of the best ways to focus energy on things that do matter, get people to a better place and sometimes even save money doing it.
Ya man. Google it. I'm not that creative. Did not make it up.
In Dutch its called the beep system. If something is shut down, we wait for the beeping to start, be it a different system or a person.
5 points for approachable naming!
My self-hosted YouTube channel with flames on the intro and intense guitar riffs will go with the Murican "scream test" with a Scream-O-Meter.com site link; my NYT best seller for pragmatic business strategy will be dubbed "the beep test" and have soft cream and pastel coloring with a demure typeface and wine pairing list on the inside back cover.
The difficulty in this structure is that someone, somewhere along the chain is laid off, fired made redundant and that person may have been in charge of the invoice.
That type of disconnect can be exploited: billing for services not rendered intermittently, etc.... We used to receive thermal printing paper at random times from a random company because they knew the invoice was sent to a different address and...who really commits fraud for printer paper? It could have just been a mistake because we received that paper....Right? Such a low key crime thats hard to spot and prove mal intentions.
That's what it's called. The mystery server that know one knows who set it up and don't know what it dose won't know what's hit them when I'm back in on Monday.

all 20 comments