• Victor@lemmy.world
      0·
      8 days ago

      Was about to say, “or if you’re running Arch, the last time you updated the kernel or systemd version, so probably last week or summit.”

    • billwashere@lemmy.worldEnglish
      0·
      7 days ago

      Yeah that’s about the only time I have to do reboots at work which are 99% linux. Well the production ones anyway.

      Or the other reason is my lab having power issues due to malfunctioning UPSes, faulty NEMA L6-30 plugs, janky 240v circuit breakers or… I’m beginning to think my lab is electrically cursed.

    • Tavi@lemmy.blahaj.zoneEnglish
      0·
      9 days ago

      I was introduced to homelab by trying to figure out how my uncles setup. It ran for 4 years after he died, 11 years uptime. The estate probate prevented anyone from touching the equipment for the legal fights, and I get a kick out of thinking of how smug he would have been about it.

  • nomad@infosec.pub
    0·
    9 days ago

    Debian admin here. Even Debian gets regular kernel upgrades that like a reboot afterwards. Security updates are more important than uptime. Also regular testing for clean recovery after a reboot is a must so a power outrage doesn’t bring any new surprises with it. Also test your backup restores regularly.

    • Pika@sh.itjust.worksEnglish
      0·
      9 days ago

      I haven’t had a kernel update on Debian that triggered the “you should restart” message in quite some time. I was under the understanding that most newer systems now use splicing at the kernel level to not require periodic reboots.

      • CrazyLikeGollum@lemmy.worldEnglish
        0·
        9 days ago

        I haven’t seen it in a while either, but also, if there is a kernel update, uname -s always returns the old kernel until a reboot.

    • pHr34kY@lemmy.world
      0·
      9 days ago

      As someone running a UPS on my ubuntu server, “uptime” represents the time since the last kernel release, and not much else.

    • FlexibleToast@lemmy.worldEnglish
      0·
      9 days ago

      Yeah, people that brag about uptimes are just bragging about the fragility of their infrastructure. If designed correctly you should be able to patch and reboot infrastructure while application availability stays up.

      • Trainguyrom@reddthat.comEnglish
        0·
        8 days ago

        With an uptime of greater than 5 years I’m going to be concerned about the system potentially not coming back up after a reboot/power outage, especially for physical hardware

        At a bank I worked at, we had an old IBM Power server which was at that point purely used for historical data. It had multiple years of uptime and was of course a good 10+ years old. When we went to take it offline, we actually just disabled the nic on the switch so we could reduce the number of powercycles it would see in fear that it would not power on anymore. Theoretically the data on it is purely historical, backed up and not needed, but there was enough question marks on each of those fronts we just played it safe

    • Zeroc00l@sh.itjust.works
      0·
      9 days ago

      Novice homelaber here, is this just a case of apt update & upgrade or is there different commands for security and kernel updates? Also what’s your preferred backup/restore software? Thanks!

          • jcr@jlai.luFrançais
            0·
            8 days ago

            Incredible that it’s not written everywhere, I always wanted to use something like this without the " update && upgrade" which looks like is not working oftentimes

            • TerraRoot@sh.itjust.works
              0·
              8 days ago

              Is it really not written? I saw apt upgrade --update and knew the standard shortcut would be -u, but that didn’t work so I tried -U, bingo bongo off I went.

            • JargonWagon@lemmy.world
              0·
              8 days ago

              Your note is very interesting about the difference between the commands and how autoremove will automatically remove stuff before or after the upgrade is performed. Should it always be done after, or are there instances when running it before is more beneficial? Is there any need to do both like this:

              # sudo apt --update --autoremove upgrade -y && sudo apt autoremove -y
              • Arthur Besse@lemmy.mlEnglish
                0·
                8 days ago

                I can’t really imagine a benefit to --autoremove except for keeping old packages a bit longer before removing them.

                Eg, if you run apt --update --autoremove upgrade -y once a day you’ll keep your prior-to-currently-running-version kernel packages a day longer than if you ran autoremove immediately after each upgrade.

                To make things more confusing: the new-ish apt full-upgrade command seems to remove most of what apt autoremove wants to… but not quite everything. 🤷

      • nomad@infosec.pub
        0·
        9 days ago

        Kernel updates are usually held back and need to be selected manually. E.g. apt-get install linux-image-amd64.

        I prefer rsync for private backups and employ bareos in my company for all servers.

      • Ghoelian@piefed.socialEnglish
        0·
        9 days ago

        Nope it’s just apt update & upgrade. Iirc apt tells you when the kernel was updated and needs a reboot as well.

          • Samsy@lemmy.ml
            0·
            9 days ago

            I configured restic once, forget about it and saved my files because it was making backups since forever.

          • zr0@lemmy.dbzer0.comEnglish
            0·
            9 days ago

            Oh, never heard about it. A quick research showed me that restic is a very viable solution. Thanks for mentioning it, I added it to my comment.

            While researching, I also came across a fancy WebUI, which is mostly what non-CLI users want: backrest

      • cRazi_man@europe.pubEnglish
        0·
        9 days ago

        I’m not the person you asked the question of. I’m a fellow novice homelaber.

        I use Kopia to backup my data folders and Docker container data. Works really well. The project for this weekend is to set offsite backups to be uploaded to iDrive.

        When I update I use this:

        sudo apt update && \ sudo apt upgrade -y && \ sudo apt full-upgrade -y && \ flatpak update -y 2>/dev/null; \ sudo apt autoremove -y && \ sudo apt autoclean && \ sudo journalctl --vacuum-time=7d

  • katy ✨@piefed.blahaj.zoneEnglish
    0·
    7 days ago

    how long since the boss has been asleep so you can finally restart without them calling two seconds later cause they didn’t bother reading the scheduled downtime email

    • oppy1984@lemdro.idEnglish
      0·
      9 days ago

      Seriously, one black out and suddenly you see the need for a UPS. Now my desktop is on a USB, my work laptop and monitors are on a UPS, my homelab is on a UPS, even my modem and router are on a UPS. I just wish I could get a backup generator, but that’s not happening anytime soon.

      • jakobmn@feddit.dk
        0·
        9 days ago

        My experience with using an UPS is that they have caised an outage every few years, which is more often than we get power outages where I live, so I didn’t replace the batteries last time the UPS took down my server, and are just running straight from the wall. It might be better with a more expensive UPS, but it’s not worth it for me.

      • Magister@lemmy.world
        0·
        8 days ago

        I sometimes have power outage in winter (snow storm, ice, etc) and working from home I need a UPS ; modem cable, router, PC, monitors, are on it, it can stand ~5h

        • oppy1984@lemdro.idEnglish
          0·
          8 days ago

          I’ve had good luck with APC. Just be ready to pay a bit more upfront. But so far in the last 6 or 7 years, I’ve only had to replace one battery.

          • Magister@lemmy.world
            0·
            8 days ago

            I bought a used APC Back-UPS Pro BR1500G for $100 on market place, it was a good deal, I replaced the 2 battery inside and added 4 outside (it is supported), I’m ready!

      • Mike D@piefed.socialEnglish
        0·
        9 days ago

        I got tired of my network puking every time the power went out for 5 seconds.

        Edit- My NAS really dislikes having the power cut off.

        • oppy1984@lemdro.idEnglish
          0·
          9 days ago

          Yep, the black outs have stopped now but for a while it was a daily occurrence. My NAS took a beating and so did my desktop. I spent a ton on ups’s to make sure that stuff was protected and bonus, I wouldn’t loose connection while on phone calls with government officials while at work… they get pissy when you suddenly drop off.

  • chronicledmonocle@lemmy.world
    0·
    8 days ago

    Pretty sure everybody is missing the joke. The joke is that Debian packages are so stable and stale that you likely will need a reboot before an update.

    Also, it’s a joke…please patch your boxes, k?

  • JovialSodium@lemmy.sdf.org
    0·
    9 days ago

    I’ve got an OpenBSD based router with ~4 hours of battery backup. If I ever stopped futzing around with it, the uptime would be fairly close to when the last version update was. (They’ve got a release cadence of about 6 months).

  • Digit@lemmy.wtfEnglish
    0·
    8 days ago

    On my Gentoo server, uptime:

    • 21:47:56 up 2455 days, 15:09, 1 user, load average: 0.00, 0.01, 0.00

    Solid.

    Would have been double that by now if not for the fire.

    • Victor@lemmy.world
      0·
      8 days ago

      You forgot to say “this is fine”, I take it?

      Joking aside, I hope you didn’t lose anything. Was it a big fire?

      • Digit@lemmy.wtfEnglish
        0·
        8 days ago

        Those who manage the dedicated server racks service kept my stuff intact. Thankfully. Just disrupted my uptime.

        [User “error” since, has cost me a TB of data. “Error”, fearquoted, because it was intentional… probably unnecessary clearing of space, partly regretted since.]

        I don’t know how big the fire was, happened over 1000 miles away from here.

        So, it really was fine. :3

  • TerraRoot@sh.itjust.works
    0·
    9 days ago

    Heard of tuptime? I’ve been using it for a while now, I think I like it.

    System startups: 151 since 18:00:05 10/11/15 System shutdowns: 137 ok + 13 bad System life: 9yr 223d 1h 27m 47s

    Longest uptime: 106d 5h 34m 28s from 14:17:10 26/03/22 Average uptime: 23d 4h 32m 0s System uptime: 99.81% = 9yr 216d 12h 31m 51s

    Longest downtime: 4d 23h 30m 48s from 10:36:53 14/09/23 Average downtime: 1h 2m 46s System downtime: 0.19% = 6d 12h 55m 56s

    Current uptime: 25d 0h 34m 25s since 20:25:37 15/11/25