Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Advertise on
How to keep your boxes up to date?
New on LowEndTalk? Please read our 'Community Rules' by clicking on it in the right menu!

How to keep your boxes up to date?

How do you guys keep your servers up to date? I have nearly a dozen servers and I'm not sure how to ensure my servers are up to date on software without making it a dull and tiresome task.


  • unattended-upgrades for security updates (only, because they are non-breaking)

  • DavidxDavidx Member
    edited April 2014

    ssh user&host

    sudo su

    apt-get update && apt-get dist-upgrade

    Thanked by 1linuxthefish

    Found this on DO as a project. Looks interesting.

    Thanked by 2rmlhhd petris
  • GoodHostingGoodHosting Member
    edited April 2014

    Why not use:

    fucking shell scripts


    related hilarity:

    Acting Director of Albino Geek Services Ltd. My Keybase ID ( gh ) | Enterprise KVM Virtual Private Servers | Twitter / Status : @ GoodHostingCo

  • @daxterfellowes said:

    Found this on DO as a project. Looks interesting.

    At a max of 10 servers and no simple self-hosted option, I'll pass. But interesting offer.

  • I run apt-get update && apt-get -y upgrade via cron daily.

    http://BornIn.Asia - FREE shared hosting and subdomain service for LET members! Click here to see how to get one yourself!
    96Forum: Low End VPS Discussions. Selling domains with GApp with various user counts (10 year reg incl. for some)

  • tchentchen Member

    +1 @albertdb with unattended-upgrades, security only.

    I'd strongly advise against cron dist-upgrade or upgrade in general for any production environment.

    Thanked by 1sleddog
  • deptadaptdeptadapt Member
    edited April 2014

    I use Ansible to manage my servers, so I use a command like:

    ansible -s all -m apt -a "update_cache=yes upgrade=yes"

    Instead of applying to all you can use Ansible's inventory to organize your servers into groups. Before updating packages on my production servers, I test against my test servers. Ansible's playbook feature is also great for deployment and configuration management.

    Edit: link to docs if you want to get started:

    Be seeing you.

  • noennoen Member

    Debian / Ubuntu Linux: Send Automatic Email Notification When Security Upgrades Available

    Old guide, but should still work..

  • smansman Member
    edited April 2014

    +1 on the Ansible thing. Pretty easy to use for this sort of stuff. Playbooks are more involved. Probably better off using command line for this. You can create groups based on Linux version then run apt or yum depending on the group.

  • JakJak Member python's fabric allows you to connect to multiple servers via ssh and run commands i was using it to run yum update -y

  • I use Apticron to email myself when my servers requires updates. Updates have broken my system before, I need to make sure I'm the one applying the updates - and not a cron script.

    darknyan said: At a max of 10 servers and no simple self-hosted option, I'll pass. But interesting offer.

    I connected them about self-hosting... they never responded. :(

  • gracagraca Member

    on debian I use cron-apt (apt-get install cron-apt) I set it to check everyday and send email to me every updates available.

    Everyday all I need to do is checking my email, I can review the details from cron-apt email, if I decided to apply the update, I use ansible/chef/puppet etc, or you can use manual approach if your have small farm server

    Thanked by 1tchen

    I'm Fanatical Lowendbox enthusiast

  • cececece Member


  • smansman Member
    edited April 2014

    Fabric is not bad but I think Ansible is better for sysadmin types. You can do much much more sysadmin stuff with it. Fabric is ok if your are a software development type and know python imho.

    I've used both and although I do some python software development I tend to prefer Ansible for sysadmin things.

  • fucking shell scripts :3

  • I use puppet, so I just have an exec resource running a yum update. Runs every 30 minutes, and everything is good.

Sign In or Register to comment.