• Possibly linux@lemmy.zip
    link
    fedilink
    English
    arrow-up
    39
    arrow-down
    4
    ·
    22 hours ago

    Having high uptime is not the flex you think it is

    You shouldn’t have uptime higher than 60 days

      • Possibly linux@lemmy.zip
        link
        fedilink
        English
        arrow-up
        3
        ·
        6 hours ago

        If a device hasn’t been rebooted in a long time there is a much higher chance of it not coming back after a reboot. This is made worse by the fact that sometimes power loss is unexpected which means that an outage can occur at a bad time.

        The other issue is that a high uptime device doesn’t usually have the latest updates installed. Delaying updates creates security issues and when you do get around to updating it means that more things get changed at once.

    • JohnAnthony@lemmy.dbzer0.com
      link
      fedilink
      arrow-up
      8
      ·
      10 hours ago

      I tried telling this to my manager for years. He saw it as a “X days since we last had a problem and needed to reboot the server” and took pride in it.

      We finally shut it down at over 5 years of uptime. Some docker containers had been running for 4 years straight.

      Yes, that means what you think it does concerning update policies. Yes, the server and some containers were exposed to the internet. No, the backups were never tested.

      • Redjard@reddthat.com
        link
        fedilink
        arrow-up
        6
        ·
        19 hours ago

        uptime should be handled by the kernel, so a kexec “soft-reboot” would still reset the uptime.