Whoops, wrong terminal again.

[-]

jlp_utah@reddit

We used to say "focus," indicating that your focus was assigned to the wrong window. Windows didn't really suffer from this unless you were using the Xmouse extension, and MacOS is also relatively immune.

[-]

Rare_Needleworker571@reddit

Whats the terminology for when you debug and the debug fails, after 100 more attempts the debug continues to fail; and the cherry on top you debug for an extra week but that debug still ends up failing?

[-]

flash44007@reddit

An oh SSHit moment indeed.

[-]

nighthawke75@reddit

Measure twice, cut once. The same rule applies to executing commands on servers.

[-]

Proof-Variation7005@reddit

technical term is a "whoopsy daisy"

[-]

timbotheny26@reddit

An "Ah shit." moment.

[-]

fizzlefist@reddit

Ah, see, around these parts we call that an "oopsey doodle"

[-]

Sarke1@reddit (OP)

I was thinking something like "terminal blindness", but that works too.

[-]

IdiosyncraticBond@reddit

Nobody says whoopsy daisy anymore 😉 , https://youtu.be/VC3thojIrFc

[-]

Oricol@reddit

I'm more of an "ooopsie poopsie" guy myself.

[-]

elpollodiablox@reddit

Technical term is actually "What the actual fuck do you mean '404'? I just pushed the change...oh...with...reloaded nginx on the wrong server. Whoopsy daisy." but shortened to "whoopsy daisy."

[-]

InevitableOk5017@reddit

oops wrong hole she said in the shawer

[-]

gigabyte898@reddit

The “onosecond”

[-]

Open_Somewhere_9063@reddit

LMAO

[-]

darthfiber@reddit

What helps for those that do this is getting out of the habit of making quick changes. Even if you aren’t using deployment systems prepare for and be prepared for your changes.

Stage all of your work in a TextEdit / Notepad in plaintext. Think through everything, the intended outcome, the order of commands, potential outcomes, and how to rollback. When you are prepared organize yourself and then proceed. Doing things too quick will only result in mistakes, stress, and burnout.

[-]

eg_ducks@reddit

I've been doing this bc I'm in a new environment that I don't totally know my way around yet, and it really takes the stress down a level or two.

[-]

Arillsan@reddit

Lets say Im trying to come up with the series of commands, in lets say a dev/test environment - would I do this still? (Or is that the scenario where I accidentally change into rhe wrong terminal...)

[-]

darthfiber@reddit

Going to be hard to replicate in staging or prod if you didn’t keep track of it in Dev. Depends on the environment, at least write down what you do as you go.

[-]

robvas@reddit

Or enter a command into Slack/Teams

[-]

fireandbass@reddit

Typing in your password in the wrong window and sending it to a Teams meeting chat of 50 people. 🤦🏻‍♂️

[-]

pointandclickit@reddit

I’ve done this once or twice. Enough to put a little more restraint on my password selection.

Being an adult really is just suck all the way down.

[-]

tech2but1@reddit

You guys aren't using password managers?

[-]

pointandclickit@reddit

Of course, but I don’t typically add stuff that’s set up for AD authentication otherwise it would be a constant game of whack a mole updating them.

[-]

kFURVqNY2BAxD2UtP2rq@reddit

In Bitwarden I add the app & URL and make the username “SSO”

[-]

promd@reddit

LOOOL!!!!

[-]

MorpH2k@reddit

Happened to me all the time but I had two computers with a KVM-switch for the keyboard to switch between them and it was probably at least once a month that I'd have it on the wrong computer and send my password over teams.

[-]

Appropriate_Let2486@reddit

It's worse in the DOD, they have alerting software for safety or base/gate closures and it makes you re-authenticate throughout the day and it's just a ActivClient popup to re-enter your PIN, countless times I have done it, usually talking or looking at someone while entering your pin.

[-]

kagato87@reddit

My lead dev once asked me if the cat walked across my keyboard after I sent him a message mid-conversation (I was pulling application logs for him).

I said "crap, guess I have to change my password now."

Later he realized I meant it, that long random string of text really was my password.

With a good password, you can do this, blame the cat, and people will commiserate the feline hijinks, buying you precious minutes to find that change password button.

[-]

sam7oon@reddit

withthe CSO in the group 😅

[-]

MisterVertigo7@reddit

I can't count high enough to tell you the number of times I've accidently overwritten documentation in one note because I think I'm typing a command in a terminal but my window focus was still in OneNote.

[-]

shizakapayou@reddit

About once a quarter someone will Teams me what’s obviously a Yubikey tap.

[-]

castillar@reddit

These happen a lot with the little ones that stay in your port all the time, usually due to the conductive element hitting someone’s leg when they have shorts on and a laptop on their lap. We refer to them as “Yubisneezes.” :)

[-]

whetu@reddit

Had it all the time at the last job simply because of the placement relative to the Macbook Pro keyboard, they were so easy to bumcccccbhcrtftlctnvurbuutghvcguvvdutvnfufekhnvp

[-]

picklednull@reddit

You can disable that with the management tool.

[-]

ibetno1tookthis@reddit

I do this all the time lol. Sometimes two or three times in a row

[-]

Ludwig234@reddit

You can easily turn off that feature using yubikey manager or yubico authenticator. Just delete the default config on the short tap slot.

[-]

dedjedi@reddit

the yubisneeze

[-]

madgoat@reddit

Cccccbtuhkjlcgejcuddifdvckvrdjnfgdtiblhnrffh

[-]

beren12@reddit

Password:

[-]

tailwheel307@reddit

Sudo rm -rf/ is the only command worthy of teams

[-]

DonL314@reddit

It looks almost like the command that removes the French language pack:

sudo rm -fr /

[-]

spin81@reddit

I didn't know my Ubuntu system had bloat! Thanks for this, I'm running the command right n

[-]

Sarke1@reddit (OP)

"For Real"

[-]

tailwheel307@reddit

The only acceptable use for teams is to cause chaos and confusion.

[-]

Ok-Pomegranate-7458@reddit

that is my password

[-]

sam7oon@reddit

you can write that on the teams chat where your manager sits and go bring pop corn , enjoy the show

[-]

belgarion90@reddit

Or admin password.

[-]

ImMrBunny@reddit

ls -a

[-]

joshghz@reddit

We have a running gag where a coworker will type "ssh" as a hushing sound, and I'll immediately respond with the usage guide from PowerShell

[-]

Cherveny2@reddit

done this many times, especially when super busy, and teams distracts me

[-]

_doki_@reddit

I tend to have this kind of problem with teams too... But I'm being stoooooopid because sometimes among the mess I'm not paying attention if the console got the focus back or if I'm somehow still with teams as the main windows..

[-]

le_suck@reddit

that's what cats are for.

[-]

ShadowCVL@reddit

I do this almost daily, be troubleshooting something, someone asks me something, I’m reading a doc and type out an elaborate command, hit enter and then try to figure out where I entered the command

[-]

HTDutchy_NL@reddit

Eh... as long as it didn't nuke a data source (or at least not all in the redundant set)... Everything else is IAC and can replicated in minutes.

[-]

Valheru78@reddit

This is one of the reasons all my servers have molly-guard installed, rebooted the wrong server a few times.

Also, lookup the reason why molly-guard was invented ;)

[-]

aenae@reddit

I was once connected to a KVM-switch with 16 servers connected to it. I was doing something on one server, and had to reboot it, so i pressed ctrl-alt-delete.

Nothing happened, so i pressed it again and the server rebooted.

While it was rebooting, i got a call 'the website is down', followed by several alerts that 16 servers stopped responding.

What actually happened is that the first time i tried to do a ctrl-alt-delete, i accidently pressed something like 'cltr-alt-insert', which was a keybind for the KVM switch to put it into broadcast mode; ie: every keypress would be send to every server. I did not know of that feature, but i do now know what happened with that second ctrl-alt-delete.

[-]

Sarke1@reddit (OP)

Lol, that's definitely a series of unfortunate events.

[-]

Spazbototto@reddit

Over the years fucked up so much shit trying to multi-task with rdp and ssh suffering from constant burnout.

It's doesn't even phase me anymore, I just close the session and write it down to fix later.

[-]

Tatermen@reddit

Way back when I started and we used Server and Workstation 2000, we used to set the desktop background of our servers to bright yellow so that when we were remote desktop'd into them, we didn't accidently mistake it for our local desktop and eg. shutdown or reboot them.

I work more on network gear now, but I still set my serial consoles to a different colour (usually blue) to differentiate them from SSH sessions.

[-]

Practical-Alarm1763@reddit

My favorite is accidentally right clicking an entire running config onto a putty session.

[-]

jjaAK3eG@reddit

Windows habits.. I keep trying to ctrl + v into putty sessions.

[-]

Practical-Alarm1763@reddit

I'm still doing that for 20+ years now.

[-]

FuriousFurryFisting@reddit

imo Windows Terminal with openssh is superior. Nothing to install, no stupid different key format, ctrl-c ctrl-v works.

[-]

BoltActionRifleman@reddit

Been there! I know nothing ever happens and the “commands” all fail but my instincts kick in and I always sift through the pile of failed command ashes to make sure.

[-]

Zenkin@reddit

and the “commands” all fail

Unless you've copied an entire running config, planning to do something like CTRL+F for port descriptions in notepad, and you accidentally right-click into that same session.

...Or so I've heard.

[-]

pdp10@reddit

puTTY made that all too easy, as I recall. :(

[-]

tech2but1@reddit

While also ignoring Ctrl-Shift-C/V annoyingly.

[-]

Cormacolinde@reddit

I sometimes wonder why selecting text in a browser didn’t put it in my clipboard automatically.

[-]

thomasbeagle@reddit

ls -a | less

[-]

SpeltWithOneT@reddit

Set a different background colour for each machine mate

[-]

LesbianDykeEtc@reddit

I have my prompt colors set as bright highlighted red for root/admin accounts, or on machines where I really need to be extra careful.

[-]

dasunt@reddit

I set the prompt differently for different environments.

Ain't going to stop all mistakes, but it'll help.

[-]

scubajay2001@reddit

This is exactly how I stopped wrong windowitis:

Green = sales/demo (like money making)

Yellow = lab (proceed with caution, testing is happening)

Red = prod (do not use outside of a maint. window)

[-]

MisterEd_ak@reddit

Testing in lab? Isn't that what prod is for?

[-]

FALSE_PROTAGONIST@reddit

gif

[-]

dedjedi@reddit

every company has a testing environment. some companies also have a production environment.

[-]

MisterEd_ak@reddit

[-]

scubajay2001@reddit

gif

[-]

scubajay2001@reddit

gif

[-]

OgdruJahad@reddit

How about difference databases?

In case you accidentally delete the production database

[-]

scubajay2001@reddit

Thankfully never had that happen, not sure why a dev would do that and usually the lab systems are isolated from prof entirely, including dbs.

Backups are the answer here though, both diff and full that ideally you're testing for the efficacy of your backup solutions 2x annually too

[-]

Dayzerty@reddit

I did this once! Imported a backup from 1-2 hours ago and no one was wiser

[-]

IdiosyncraticBond@reddit

We had that. Then a colleague used a dev terminal to login to production and didn't logout. Other colleague then proceeded to restart the environment in his ~dev~ production environment

[-]

justinDavidow@reddit

Set a different background colour for each machine mate

Yeah; there ain't enough colors for that. ;)

[-]

rml0000@reddit

This is why i set the text color for production servers to red. sadly it took a few oopsies before i thought of this.

[-]

Majik_Sheff@reddit

Color scheme indicates danger level. Local unprivileged user gets a pleasant amber text on black.

Root on the VM hypervisor gets black on a vivid red background.

[-]

AverageMuggle99@reddit

That old chestnut.

[-]

A_Nerdy_Dad@reddit

Or accident clear text your damn password lol

[-]

Over-Map6529@reddit

We call it a fuckup here.

[-]

Not_Freddie_Mercury@reddit

SNAFU

[-]

scubajay2001@reddit

That's highly technical terminology you're using there. Must be quite the seasoned sysadmin lol

[-]

Bent01@reddit

Me writing the config of a branch Cisco ASA onto the datacenter ASA (diff models) using ASDM years ago.

Went to the bathroom when it was writing, came back to a shitstorm of phone calls 😂

[-]

IFarmZombies@reddit

If you are a midwest sysadmin, its usually just an "ope"

[-]

JimmyG1359@reddit

Screwing up

[-]

Burgergold@reddit

Unplanned outage

[-]

Witte-666@reddit

Depending on the day and time, it could be called something like a "Monday problem"

[-]

ofnuts@reddit

Seen worse. In the late 80s, a Unix sysadmin colleague had the habit to mount his Windows (or was it OS/2?) PC in the Unix tree so that he could grab files he had downloaded from the internet.

Until that fateful day when he did a rm -r in some directory under which his PC was mounted. Between the command taking longer than expected and the hard disk flurry on the PC it took him a while to make things click and hit Ctrl-C. He was so miffed we thought he would resign on the spot and take in sheep farming.

[-]

Wendals87@reddit

More times than I'd care to admit I restarted our shared jump host, thinking I was in a remote powershell session on another device

As soon as I hit enter and realise what I've done, the teams chat lights up with people asking if the jump host is down

[-]

FarToe1@reddit

I wish I could say it happened less with experience...

[-]

dasdzoni@reddit

systemctl stop httpd

What do you mean the production website is down??

[-]

vogelke@reddit

I generally call it a facepalm or an awshit. So far, my best prevention for this is always having the hostname and userid in my shell prompt.

You might also want to turn the prompt red if you're running as root.

[-]

HearthCore@reddit

Terminal Escape ? As if it was malware

Boss, the hypervisor is down due to some unforeseen terminal escape.

[-]

Sarke1@reddit (OP)

That's a good one. I was thinking something like "terminal blindness".

[-]

rumforbreakfast@reddit

Reminds me of the commenter who accidentally ran sysprep on his own machine rather than the one he was remoted onto 😆

[-]

Cormacolinde@reddit

I remember launching a VERY aggressive partition recovery software on disk 1, because of course disks start counting at 0 right? Not in this software no it didn’t it counted from 1. At least it was my own work machine and I had a backup but I got a lab computer setup for this stuff afterwards.

[-]

Stokehall@reddit

Didn’t do list disk or list part first ? We call that partition roulette.

[-]

No_Winner2301@reddit

incompetence?

[-]

dorflGhoat@reddit

I have a burned-in muscle memory to >hostname >pwd before running anything.

But I used to support a nightmare Oracle stack and would frequently have 5 or 6 sessions open at once and haven’t recovered from that trauma.

[-]

Aboredprogrammr@reddit

And a follow up question: what do you call the physical form of this situation? For example, you have a laptop next to a keyboard/desktop, and starting at the laptop but typing on the desktop keyboard. (I do this more often than I would care to admit!)

[-]

tech2but1@reddit

I've been writing on paper and then turned to my computer to Ctrl-Z something.

[-]

littlelowcougar@reddit

I’ll alt tab back to Slack every now and then only to realize it was the app in focus four minutes ago when I was pummeling vi keystrokes at a seemingly unresponsive terminal.

Apparently my go to for “why the fuck isn’t this terminal responding” is ESC + jkjkjkjkjhhll

[-]

inode71@reddit

My boss in the 90s called them “oh shits” and we each got one per year guilt free.

[-]

joshghz@reddit

Depending on the command and the session, sometimes that term is called "unemployment"

[-]

sssRealm@reddit

docker rm $(docker ps -a -q)
(◞‸◟,)

[-]

blissed_off@reddit

I was connected to what I thought was one of my test server’s iDRAC interface. We’re having our team call, I’m half listening and half redoing this test server with a new OS. Halfway through the call, my boss interrupted the meeting and asked if anything was going on with the DAM server. I said I’d take a look.

It only took me a minute to realize what I had done. I went to his office and told him exactly what happened and that I will recover it. Thankfully the DAM was on hyper v, and all of the VM disk and config files are on a different raid than the boot disk. All told it was down less than two hours. Bonus I upgraded the windows OS and hyper V….

It happens. Own it, fix it. I wrote up a recovery plan afterwards for our DR run book.

[-]

imagei@reddit

That depends. If you’re connected to the wrong cluster, it’s a clusterfuck. If it’s an ssh session it’s a sshiit.

[-]

Pyrostasis@reddit

Tuesday

gif

[-]

MadeMeStopLurking@reddit

1st time is a lesson.

2nd time is a mistake

3rd time is an RPE

[-]

Silent_Title5109@reddit

Pasted passwords yes. Sent wrong command nope. Guess who now always change his bash prompt to time:hostname:pwd

Yeah I probably just jinxed my Monday right there.

[-]

rayholtz@reddit

It could be called a RGE. Resume Generating Event.

[-]

Redemptions@reddit

This is why my terminals backgrounds are color coded. Red Prod (is this critical?), greens are test (go nuts)

[-]

Far-Appointment-213@reddit

The term is....

Fubar

[-]

Leucippus1@reddit

I call that move the "this IS a kunernetes node, right?" followed by 'the system will be back up in a minute temporary error nothing to see here.' Then a bun of well deserved shit from my fellow engineer.

[-]

nahmean@reddit

Incompetence

[-]

BlackV@reddit

I like you.

[-]

GardenWeasel67@reddit

Tuesday

[-]

sam7oon@reddit

Mondays work too

[-]

Live-Juggernaut-221@reddit

Pulling a gitlab? https://youtu.be/tLdRBsuvVKc

[-]

Signal_Till_933@reddit

What a great video.

Obviously the engineer fucked up running rm -rf but how had nobody ever tested their backups in such a large company? Very broken system. It was bound to happen.

[-]

Logmill43@reddit

I learned something from this. Thanks for the share

[-]

SpecFroce@reddit

Desktop clutter/PEBKAC

[-]

SlightAnnoyance@reddit

I propose "terminoops"

[-]

Recent_Carpenter8644@reddit

Not SSH, but I've configured a window size in Powertoys slightly smaller than full screen, so I can easily set that size for RDP sessions so I can tell whether I'm doing commands on my own computer or the remote session.

Someone here accidentally ran an RDP session to a server inside an RDP session to another server, and got confused what they were installing something on. It took some convincing in the form of event log entries before they accepted that it was them that did it.

[-]

cbelt3@reddit

“Fuuui….”.

Got another monitor and color coded systems.

Prod is RED.

[-]