Sign in

reboots are the real enemy. how do you schedule them for a dozen on-prem servers? lol

maintenanceoperationspatching5 replies 路 100 views 路 started
Reply
  1. Tariq Jansen
    @tariq_polar-2ap

    Our patching is whenever someone remembers and entirely manual, which means some servers get skipped for months lol i want to fix this without breaking things. How do u structure rings, approvals and reboots??

    theres also the reboot question xD some of these servers havent been restarted in a very long time, and everyone is scared of what happens if we do. how do you introduce regular reboots without causing a panic the first time? im about to throw this thing out the window lol

    1
  2. Lea
    @ltorres_15

    ahh classic rings work: a small canary group patched first (including at least one server per role), then a wider group a few days later, then the rest. Problems surface on servers that matter less.

    2 1 helpful
  4. Chen Lindqvist
    @tensor_owl-2e5

    hmmm separate security updates from everything else. Unattended security-only updates are fairly low risk on Debian/Ubuntu (unattended-upgrades with only the security origin enabled), while feature updates go through the window. good luck man!

    0 1 helpful
  5. Chen Lindqvist
    @tensor_owl-2e5

    hmmmm ok told my boss it would take 10 minutes. its been a whole week. this. so much this

    facepalm

    1 6 helpful
  6. Chen Lindqvist
    @tensor_owl-2e5

    guys pls help ok this thread just saved my weekend seriously need help here 馃槶

    17 0 helpful
Read next 路 System Administration
MONDAY 8AM AND THE MONITORING BOX CAN'T EVEN WRITE A LOCK FILE
Solved 路 15 replies
Read

Reply to this topic

Sign in or create an account to reply.