After almost half a century, I'm still doing it...
-
So I'm working on a server from home.
I do a
cat /sys/class/net/eth0/operstateand it saysunknowndespite the interface being obviously up, since I'm SSH'ing into the box.I try to explicitely set the interface up to force the status to say
upwithip link set eth0 up. No joy, stillunknown.Hmm... maybe I should bring it down and back up.
So I do
ip link set eth0 downand... I drive 15 miles to work to do the correspondingip link set eth0 up50 years using Unix and I'm still doing this...
-
L [email protected] shared this topic
-
Why don't you use chained commands, or better yet simply create an alias that chains down/up, then use the alias instead?
-
Or use some kind of molly guard. Or have an OOB management channel.
You'd think you'd learn from your mistakes after one or two of them, not fifty years' worth...
-
Remember what Bruce Lee said:
I fear not the man who has practiced 10,000 kicks once, but I fear the man who has practiced one kick 10,000 times.
-
Because I plain forgot I was remote. It's as simple and as stupid as that.
-
In my defense, I just installed the machine. I was configuring it from home after hours.
-
Fair enough. I've done worse in my time as a keyboard jockey.
-
I knew a guy who did this and had to fly to Germany to fix it because he didn’t want to admit what he’d done.
-
There, but for the grace of god....
-
This hits....
-
after hours
I've configured PAM to not let me login remotely after hours, because I just know that someday I'll want to fix "just this tiny thing" and I'll break production because I'm too tired. I clearly need protection from myself, and this is one slice in Dr.Reasons's Swiss cheese model.
Don't let the people drag you down, this happens to all of us.
-
Don't be shitty.
-
I have a failsafe service for one of my servers, it pings the router and if it hasn't reached it once for an entire hour then it will reboot the server.
This won't save me from all mistakes but it will prevent firewall, link state, routing and a few other issues when I'm not present.
-
time to setup a console server so that you don't do that again.
-
I hope you don't admin any mission critical servers. That's a first year mistake.
-
This is a server I was setting up. It's not doing anything useful at all at the moment, hence the lax work practice. The only reason I drove back to work is because it's needed tomorrow and I wanted to finish setting it up tonite.
-
Until they have to troubleshoot the console server ..
-
then setup a super console server. lol
-
Did this once on a router in a datacenter that was a flight away. Have remembered to set the reboot in future command since. As I typed the fatal command I remember part of my brain screaming not to hit enter as my finger approached the keyboard.
️ -
Have remembered to set the reboot in future command since
That's not a bad idea actually. I'll have to reuse that one.
Thanks!
