Company deploys new do-everything enterprise software, and two weeks before it's scheduled to go live, this IT pilot fish gets a call from one of the analysts working on the project.
"The analyst requested that FTP service be enabled for a service account," says fish. "That happens to be the account they use to start and stop the Java server."
But fish doesn't like the idea of opening a service where the password will be sent unencrypted. He responds to the analyst's message: Does the vendor specify FTP? Can you use Secure FTP instead?
Analyst replies that he's sure the system doesn't support Secure FTP.
Fish escalates the issue, and IT management tries to fight it, but loses. Unencrypted FTP it is.
The system goes live. Two weeks later, fish realizes that both memory usage and file count have jumped. He checks the server to find that several Java processes are eating up all the memory and file handles.
He calls the analyst -- who's glad fish called, because he wants to ask fish to raise the system's limits for memory use and file handles.
But fish knows there's no more to give. How did you get the Java configuration? he asks the analyst. "Oh, I copied it from the vendor's site," analyst says.
Did you check the memory size of the vendor's reference machine? "Yes, it was 128GB," says analyst. And how much does our machine have? 64GB.
That's why it's running out of memory, fish says. Can you adjust the Java memory option?
Short answer: Nope. "We ended up restarting the Java server every week," grumbles fish. "We lost the fight as usual.
"But at least they didn't ask us to reboot the physical machine..."
Don't let Sharky run out of your memories. Send me your true tale of IT life at firstname.lastname@example.org. You'll get a stylish Shark shirt if I use it. Add your comments below, and read some great old tales in the Sharkives.
Get your daily dose of out-takes from the IT Theater of the Absurd delivered directly to your Inbox. Subscribe now to the Daily Shark Newsletter.