So I’m working on a server from home.

I do a cat /sys/class/net/eth0/operstate and it says unknown despite 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 up with ip link set eth0 up. No joy, still unknown.

Hmm… maybe I should bring it down and back up.

So I do ip link set eth0 down and… I drive 15 miles to work to do the corresponding ip link set eth0 up

50 years using Unix and I’m still doing this… 😥

  • thingsiplay@beehaw.org
    7·
    4 days ago

    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.

  • plumbercraic@lemmy.sdf.org
    13·
    4 days ago

    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. 🤦‍♂️

    • ExtremeDullard@lemmy.sdf.orgOP
      71·
      4 days ago

      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!

      • SayCyberOnceMore@feddit.ukEnglish
        3·
        3 days ago

        This.

        Do it. This saved my life on more than one occasion.

        You’ll think “nah, it’ll be fine” and then at 11pm when your brain’s fried on vending machine coffee you’ll be glad that you did it… 3 times over…

  • apt_install_coffee@lemmy.ml
    9·
    4 days ago

    A few months ago I accidentally dd’d ~3GiB to the beginning of one of the drives in a 4 drive array… That was fun to rebuild.

    • IngeniousRocks (They/She) @lemmy.dbzer0.com
      5·
      4 days ago

      Like 3 weeks ago on my (testing) server I accidentally DD’d a Linux ISO to the first drive in my storage array (I had some kind of jank manual “LVM” bullshit I set up with odd mountpoints to act as a NAS, do not recommend), no Timeshift, no Btrfs snapshot. It gave me the kick in the pants I needed to stop trying to use a macbook air with 6 external hard drives as a server though. Also gave me the kick in the pants I needed to stop using volatile naming conventions in my fstab.

      • apt_install_coffee@lemmy.ml
        1·
        3 days ago

        I wish.

        It was a bcachefs array with data replicas being a mix of 1,2 & 4 depending on what was most important, but thankfully I had the foresight to set metadata to be mirrored for all 4 drives.

        I didn’t get the good fortune of only having to do a resilver, but all I really had to do was fsck to remove references to non-existent nodes until the system would mount read-only, then back it up and rebuild it.

        NixOS did save my bacon re: being able to get back to work on the same system by morning.

  • mlg@lemmy.worldEnglish
    7·
    3 days ago

    Lol I’ve locked myself out of so many random cloud and remote instances like this that now I always make a sleep chain or a kill timer with tmux/screen.

    Usually like:

    ./risky_dumb_script.sh ; sleep 30 ; ./undo.sh

    Or

    ./risky_dumb.script.sh

    Which starts with a 30 second sleep, and:

    (tmux) sleep 300 ; kill PID

  • melroy@kbin.melroy.org
    5·
    4 days ago

    @ExtremeDullard@lemmy.sdf.org You’re doing it wrong. Just setup a KVM behind your server. So then you never need to leave home again.

  • Ephera@lemmy.mlEnglish
    11·
    4 days ago

    At $DAYJOB, we’re currently setting up basically a way to bridge an interface over the internet, so it transports everything that enters on an interface across the aether. Well, and you already guessed it, I accidentally configured it for eth0 and couldn’t SSH in anymore.

    Where it becomes fun, is that I actually was at work. I was setting it up on two raspis, which were connected to a router, everything placed right next to me. So, I figured, I’d just hook up another Ethernet cable, pick out the IP from the router’s management interface and SSH in that way.
    Except I couldn’t reach the management interface anymore. Nothing in that network would respond.

    Eventually, I saw that the router’s activity lights were blinking like Christmas decoration. I’m guessing, I had built a loop and therefore something akin to a broadcast storm was overloading the router. Thankfully, the solution was then relatively straightforward, in that I had to unplug one of the raspis, SSH in via the second port, nuke our configuration and then repeat for the other raspi.

  • twinnie@feddit.uk
    103·
    4 days ago

    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.

  • InnerScientist@lemmy.world
    41·
    4 days ago

    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.

  • Float@startrek.websiteEnglish
    24·
    4 days ago

    Every network engineer must lock themselves out of a node at some point, it is a rite of passage.