7 ms·

I, too, have a server running 16.04 that I'm afraid to update. It currently has an uptime of 1281 days... at this point I'd feel bad rebooting it

by kylec 4mo ago

hdgvhicv 4mo ago
My oldest server is on 8.04.
nijave 4mo ago
dd filesystem to another machine then boot it up with an emulator like qemu and do a trial run Be careful if you have anything that autostarts that reaches out
- ThePowerOfFuet 4mo ago
  Genius.
prmoustache 4mo ago
What is there to be afraid of? Don't you have backups? Also, debian/ubuntu systems can easily be setup to auto update and reboot on a regular basis, leaving you manual maintenance only for the larger version upgrades.
- account42 4mo ago
  Backups are not going to help if a reboot breaks something.
  - prmoustache 4mo ago
    Yes because you can always do a dusaster recovery by reinstalling and restoring data. A reboot doesn't break anything. Bugs do. Any time I had a regression after a kernel update on a linux distro I could boot it on a prior version from the grub menu. Any time I had a regression with a software package I could rollback to a prior version. Rolling back updates is a problem that has been solved for decades, at least on linux systems. The key with unattended upgrade is you want to have decent monitoring to make sure you never run out of disc space and do not figure it out weeks later if you have had an issue.
- mx7zysuj4xew 4mo ago
  You do not reboot systems for regular updates. Only in case of critical kernel updates do you consider it
  - prmoustache 4mo ago
    You might want to restart services after they or libraries dependencies get updated. On debian based distros, updated packages automatically take care of restarting the service but it might not happen when only a dependency has been updated. In the end it is easier to schedule a weekly reboot window if packages have been updated. You aren't running a single server if you are interested in 99.99999990% of uptime anyway. Imho a regular reboot is good practice: you are more likely to remember what you did a week earlier if an app/service fail to restart after you tweaked a config file than if it happens months later. There is no reason to be afraid of reboot when they happen on a regular basis.

I, too, have a server running 16.04 that I'm afraid to update. It currently has an uptime of 1281 days... at this point I'd feel bad rebooting it

by kylec 4mo ago

I, too, have a server running 16.04 that I'm afraid to update. It currently has an uptime of 1281 days... at this point I'd feel bad rebooting it

hdgvhicv 4mo ago

My oldest server is on 8.04.

nijave 4mo ago

dd filesystem to another machine then boot it up with an emulator like qemu and do a trial run Be careful if you have anything that autostarts that reaches out

ThePowerOfFuet 4mo ago
Genius.

prmoustache 4mo ago

What is there to be afraid of? Don't you have backups? Also, debian/ubuntu systems can easily be setup to auto update and reboot on a regular basis, leaving you manual maintenance only for the larger version upgrades.

account42 4mo ago
Backups are not going to help if a reboot breaks something.
- prmoustache 4mo ago
  Yes because you can always do a dusaster recovery by reinstalling and restoring data. A reboot doesn't break anything. Bugs do. Any time I had a regression after a kernel update on a linux distro I could boot it on a prior version from the grub menu. Any time I had a regression with a software package I could rollback to a prior version. Rolling back updates is a problem that has been solved for decades, at least on linux systems. The key with unattended upgrade is you want to have decent monitoring to make sure you never run out of disc space and do not figure it out weeks later if you have had an issue.
mx7zysuj4xew 4mo ago
You do not reboot systems for regular updates. Only in case of critical kernel updates do you consider it
- prmoustache 4mo ago
  You might want to restart services after they or libraries dependencies get updated. On debian based distros, updated packages automatically take care of restarting the service but it might not happen when only a dependency has been updated. In the end it is easier to schedule a weekly reboot window if packages have been updated. You aren't running a single server if you are interested in 99.99999990% of uptime anyway. Imho a regular reboot is good practice: you are more likely to remember what you did a week earlier if an app/service fail to restart after you tweaked a config file than if it happens months later. There is no reason to be afraid of reboot when they happen on a regular basis.