From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id E50F3138010 for ; Thu, 28 Mar 2013 16:30:41 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 01E21E097E; Thu, 28 Mar 2013 16:30:27 +0000 (UTC) Received: from mail-la0-f48.google.com (mail-la0-f48.google.com [209.85.215.48]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 66457E0952 for ; Thu, 28 Mar 2013 16:30:25 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id fq13so18139715lab.35 for ; Thu, 28 Mar 2013 09:30:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=SmCZDjIs21rH+pdX5YT8aO39nuSusnG33ovR0/ND5K8=; b=xm72yKVD7UVga4s7nHdqNBJJxYE0R/YFMeDhzMTfJvWbEngUfbn1goJETrrKHtucXB rqdcai9fbu3F3dETIdhs1mRbCjePAean0xMy1rnlNQIhZGuQr79HkJWQCzODhJM5nJA+ psWTZLjqLTFPAFE64kNculx+5CwAaV6xAG7FmlaudBwvFE79NFeR5nGBDaY9HEz8kS8O JCtYEfNpIHbl2Bw4E5tOw1DMzItKpRPcgYhxc1j0O8RRIb1Wdqf0p4wYiSryDeAcsDha B50Vrd58/zEJbP8+0oKZtsOXRpOkPLs0/GMCIOeJISKaX1KIZtZ5s770UlFWDs/Ap1Kw nQjA== Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 X-Received: by 10.112.87.132 with SMTP id ay4mr12403363lbb.87.1364488223428; Thu, 28 Mar 2013 09:30:23 -0700 (PDT) Received: by 10.114.58.43 with HTTP; Thu, 28 Mar 2013 09:30:23 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Mar 2013 12:30:23 -0400 Message-ID: Subject: Re: [gentoo-user] Updating our live servers. I'm scared! From: Nick Khamis To: gentoo-user@lists.gentoo.org Content-Type: text/plain; charset=ISO-8859-1 X-Archives-Salt: 6d265409-a63a-4785-83d0-bb987e9b1d6e X-Archives-Hash: 3c8c59c46e839490cb842b648b86a656 So basically rsync configs and databases first? When issuing updates to world and so no. What is the safest process/order to sync portage, and update world? I have seen a number of flags various example use, and was wondering if someone can give me the safest and equally effective commands with flags included. Thanks again, Nick. On 3/28/13, Joshua Murphy wrote: > On Thu, Mar 28, 2013 at 11:38 AM, Nick Khamis wrote: > >> Hello Everyone, >> >> Just got a ticket assigned to me where we need to update our production >> servers. >> >> uname -a >> Linux noun 3.4.9-gentoo #2 SMP Sat Oct 13 09:35:07 EDT 2012 x86_64 >> Intel(R) Xeon(TM) CPU 3.60GHz GenuineIntel GNU/Linux >> >> eselect >> [18] hardened/linux/amd64 * >> >> I don't think they have been updated since the initial install and >> wanted to get a little feedback on some safe practices and methods >> that should be performed before and while doing so. >> >> Thanks in Advance, >> >> Nick. >> >> > Personally, I would recommend pulling an rsync (databases and such might > cause a hiccup with that) of one of them to a nonessential system and > testing updating there, building packages (assuming matching use flags, > etc, across your systems), documenting the pitfalls you run into as you go. > After you're up to date there, run through and test it again from a base > copy, then test the actual services to ensure changes to them don't hose > your environment's configuration, and once that's good, it then depends > entirely on what failover, or downtime allowances you have available. If > you have no failover to rely on, and can't afford enough downtime to update > the system in place from the packages you've built, clone each off, update, > then migrate the changes that've occured in the time between... time > consuming, and requires a lot of care, but doable. > > -- > Poison [BLX] > Joshua M. Murphy >