• Blackmist
    link
    fedilink
    English
    arrow-up
    39
    ·
    10 months ago

    Ah, if only it was a server room and not a customer 3 hours drive away. And he’d closed and gone home for the night.

    Fortunately it just needed a reboot, and I was able to talk him through that in the morning.

    • SpaceCowboy@lemmy.ca
      link
      fedilink
      arrow-up
      13
      ·
      10 months ago

      Oof… well you can just say “it must be some hardware problem or something… maybe a reboot will fix it.”

    • JasonDJ@lemmy.zip
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      10 months ago

      Oof I did a firmware upgrade on my main external firewall.

      The upgrade went fine but when we added an ISP a month or so prior, I forgot to redistribute the ISPs routes. While all my ISPs were technically working, and the firewall came back up, nothing below it could get to the internet, so it was good as down.

      Cue the 1.5 hour drive into the office…

      Had that drive to think about what went wrong. Got into the main lobby, sat down, joined the wifi, and fixed it in 3 minutes.

      Didn’t even get to my desk or the datacenter.