• Tenkard@lemmy.ml
    4·
    2 months ago

    Ubuntu server just asked me if I want to upgrade to V24, I don’t know when I’ll take time to do that :p

  • xmunk@sh.itjust.works
    46·
    2 months ago

    Initializing VPC…

    Configuring VPC…

    Constructing VPC…

    Planning VPC…

    VPC Configuration…

    Step (31/12)…

    Spooling up VPC…

    VPC Configuration Finished…

    Beginning Declaration of VPC…

    Declaring Configuration of VPC…

    Submitting Paperwork for VPC Registration with IANA…

    Redefining Port 22 for official use as our private VPC…

    Recompiling OpenSSH to use Port 125…

    Resetting all open SSH connections…

    Your VPC declaration has been configured!

    Initializing Declared VPC…

    • cypherix93@lemmy.worldEnglish
      88·
      2 months ago

      I can’t be bothered to walk down to the basement, so practically my server is also only accessible by SSH

      • yhvr@lemm.ee
        10·
        2 months ago

        I’m at college right now, which is a 3 hour drive away from my home, where a server of mine is. I just have to ask my parents to turn it back on when the power goes out or it gets borked. I access it solely through RustDesk and Cloudflare Tunnels SSH (it’s actually pretty cool, they have a web interface for it).

        I have no car, so there’s really no way to access it in case something catastrophic happens. I have to rely on hopes, prayers, and the power of a probably outdated Pop!_OS install. Totally doesn’t stress me out I’ll just say I like to live on the edge :^)

          • yhvr@lemm.ee
            2·
            2 months ago

            Hadn’t heard of pikvm before. Will keep that in mind, thanks!

        • Lucy :3@feddit.org
          6·
          2 months ago

          Currently the server(s) are in my room, which is so messy my dad probably wouldn’t even enter it voluntarily. And in the case grub/fstab/crypttab/etc. are messed up, which is probably the most common error, he probably couldn’t solve it by himself. Soon everything’s gonna live in its own little room in the basement, so it’s gonna be accessible easier actually.

        • msage@programming.dev
          4·
          2 months ago

          And no one ever tried to restore it.

          Happened to me as well, after a year I learned incremental DB backups were wrongly offset by GMT diff, so we were losing hours every time. Fun.

          Luckily we never needed them.

          And now we have Postgres with WAL archiving and I sleep so much better.

        • Buddahriffic@lemmy.world
          8·
          2 months ago

          Someone set up a script to automatically create daily backups to tape. Unfortunately, it’s still the first tape that was put in there 3.5 years ago, every backup since that one filled up failed. It might as well have failed silently because everyone who received the email with the error message filtered them to a folder they generally ignored.

    • naeap@sopuli.xyz
      14·
      2 months ago

      Never touch a running system
      Until you have a inviting hole in your system

      Nevertheless, I’m panicking every time I update my sever infrastructure…

  • WagnasT@lemmy.world
    17·
    2 months ago

    when it was the wrong server and you’re hoping it comes back up before 5 minutes and nagios starts sending alerts

  • umbrella@lemmy.ml
    35·
    2 months ago

    this week i sudo shutdown now our main service right at the end of the workday because i tought it was a local terminal.

    not a bright move.

    • mox@lemmy.sdf.org
      9·
      2 months ago

      Oops.

      Since you’re using sudo, I suggest setting different passwords on production, remote, and personal systems. That way, you’ll get a password error before a tired/distracted command executes in the wrong terminal.

      • umbrella@lemmy.ml
        17·
        2 months ago

        i have different passwords but i type them so naturally it didnt even register.

        “wrong password.”

        “oh, i’m on the server, here’s the right password:”

        “no wait”

    • SavvyWolf@pawb.socialEnglish
      39·
      2 months ago

      There’s a package called molly-guard which will check to see if you are connected via ssh when you try to shut it down. If you are, it will ask you for the hostname of the system to make sure you’re shutting down the right one.

      Very usefull program to just throw onto servers.

    • Trainguyrom@reddthat.comEnglish
      8·
      2 months ago

      I was making after hours config changes on a pair of mostly-but-not-entirely redundant Cisco L3 switches which basically controlled the entire network at that location. While updating the running configs I mixed up which ssh session was which switch and accidentally gave both switches the same IP address, and before I noticed the error I copied the running config to the startup config.

      Due to other limitations and the fact that these changes were to fix DNS issues (and therefore I couldn’t rely on DNS to save me) I ended up keeping sshing in by IP until I got the right switch and trying to make the change before my session died due to dropped packets from the mucked up network situation I had created. That easily added a couple of hours of cleanup to the maintainence I was doing

    • naeap@sopuli.xyz
      8·
      2 months ago

      Happens to everyone

      Just having a multitude of terminals open with a mix of test environment and (just for comparison) an open connection to the production servers…

      We were at a fair/exhibition once and on the first day people working on an actual customer project asked us, if they could compare with our code.
      Obviously they flashed the wrong PLC and we were stuck dead at the first hours of the exhibition.
      I still think that this place was cursed, as we also had to do multiple re-soldering of some connections of our robot and the sherry on top was the system flash dying - where I had fucked up, because I just finished everything late at night and didn’t made a complete backup of everything.
      But it seems, if luck runs out, you lose on all fronts.

      At least I was able to restore everything in 20mins. Which must be some kind of record.
      But I was shaking so much from the stress, that I couldn’t efficiently type anymore and was lucky to have a colleague to just calmly enter what I told him to and with that we’re able to get the show case up and running again.

      Well, at least the beer afterwards tasted like the liquid of the gods

    • LiveLM@lemmy.zipEnglish
      6·
      2 months ago

      Best thing I did was change my shell prompt so I can easily tell when it isn’t my machine

  • Ignotum@lemmy.world
    27·
    2 months ago

    I have more than once typed shutdown instead of reboot when working on a remote machine… always fun

    • umbrella@lemmy.ml
      6·
      2 months ago

      i have the horrible habit of using shutdown now because of my personal computers. a lot more fun.

    • chatokun@lemmy.dbzer0.com
      7·
      2 months ago

      Networking, we had a remote office in Europe (I’m in the US) and wanted to reset a phone. Phone was on port 10 of the Cisco switch, port 1 went to the firewall (not my design, already in place).

      Helping my coworker, I tell her to shut port 10.

      Shut port 1, enter.

      Ok… office is offline and on another continent…

    • sik0fewl@lemmy.ca
      2·
      2 months ago

      Not sure if this will help you, but I always do shutdown and then think about whether I want to do -r or -h. I’m sure it won’t help 🙂

  • Neuromancer@lemm.ee
    62·
    2 months ago

    In the old days some of the servers took at hour to reboot. That was stressful when you couldn’t ping it at an hour.

      • Neuromancer@lemm.ee
        36·
        2 months ago

        The more disk you had, the longer it took. It walked the scsi bus which took forever. So if you had more disk. It took even longer.

        Since everything was remote, you’d have to call hands and they weren’t technical. Also no cameras since it was the 90’s.

        Now when I restart a vm or container. I panic if it’s not back up in 10 minutes.

          • Neuromancer@lemm.ee
            9·
            2 months ago

            It isn’t a disk driver since the OS is not loaded yet. It is the hardware identifying each disk in the SCSI chain. Not sure what else it was doing walking the bus much I know finding all the disk was the longest part.

            • CanadaPlus@lemmy.sdf.org
              1·
              2 months ago

              Shoot, it did occur to me that might not technically be the right word.

              Still, even if you’re an engineer in the late 80’s, it seems like it would be obvious you need a way for disks to announce themselves in O(1) time. Was it just a limitation of interoperability between vendors or something?

              • Neuromancer@lemm.ee
                11·
                2 months ago

                I think it was just a limit of how quick everything ran back then. Also, this was an IBM system that was checked, double-checked, and triple-checked because it was a mission-critical system. IBM used to be known for quality hardware. Hard to imagine because they are such a crap company now but that was the equivalent of a google back then.

    • fuckwit_mcbumcrumble@lemmy.dbzer0.comEnglish
      20·
      2 months ago

      I like how posting got fairly fast. Then we started putting absurd amounts of ram into servers so now they’re back to slow.

      Like we have a high clock speed dual 32 core AMD server with 1TB of ram that takes at least 5 minutes to do it’s RAM check. So every time you need to reboot you’re just sitting there twiddling your thumbs waiting anxiously.

      • Neuromancer@lemm.ee
        9·
        2 months ago

        I will date myself. These machines had a lot of memory as well which added to the slow reboot. I think it was 16 gigs.

        The r series for IBM took forever. The p series was faster but was still slow

            • trolololol@lemmy.world
              1·
              2 months ago

              I had a friend with one of those while I had an Atari. The Atari game would come up within a minute, but the tape took like 15 min to start.

              • Neuromancer@lemm.ee
                12·
                2 months ago

                Using a tape drive is crazy when you think about it. It was slow…. This wasn’t the big tape cartridges. It was a standard Audio tape. Not sure why they could store but it was all sequential

  • NastyNative@mander.xyzEnglish
    231·
    2 months ago

    Tbh there is nothing more taxing on my mental health than doing maintenance on our production servers.

    • tooclose104@lemmy.ca
      4·
      2 months ago

      When someone previously told a vrtx vm not to auto boot after power up and none of the remote access is working either… Both undocumented as well, of course. And your tired AF tech is statically configuring the wrong IP range on their laptop to manu because it’s been a long shutdown day and are also unfamiliar with the system in general (me). Good times, I figured it out though, but lots of sweating and swearing.