Date: Wed, 19 Dec 2018 10:33:29 -0500 From: Matt Garber <matt.garber@gmail.com> To: Brian Neal <brian@aceshardware.com> Cc: "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org> Subject: Re: Upgrading 11.2 -> 12.0 on EC2 Message-ID: <8FE35DD1-6D07-4430-9706-A873E0D8ECCE@gmail.com> In-Reply-To: <5c19ea68.1c69fb81.1febf.ddb2SMTPIN_ADDED_MISSING@mx.google.com> References: <5c19ea68.1c69fb81.1febf.ddb2SMTPIN_ADDED_MISSING@mx.google.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> On Dec 19, 2018, at 1:50 AM, Brian Neal <brian@aceshardware.com> = wrote: >=20 > I=E2=80=99m looking for advice on doing a release upgrade of a running = instance. It looks like the normal procedure using freebsd-update = requires a reboot between invocations of the install command, but after = the first reboot, most of the userland is non-functional, including most = importantly sshd. Is it safe to run the install commands back to back = without rebooting? Or is the only safe procedure to build a new = instance from scratch for each release? Brian, It=E2=80=99s not true that after the first reboot the userland is = non-functional; sshd and friends should still be working fine. The first = reboot switches you to the 12.0 kernel, which is necessary as the first = step before upgrading the userland to 12.0 =E2=80=93 and of course = potentially using `pkg-static` or ports to rebuild/reinstall your = packages/ports against the new ABI. If you=E2=80=99re running any kind of public-facing service, the safest = method in my opinion *with as little downtime as possible* is to deploy = a new instance and then point to it once everything is successfully = reinstalled (e.g., DNS change, elastic IP change, elastic load balancer, = etc.). Otherwise, the =E2=80=9Csafe=E2=80=9D method to upgrade in place = is to follow what the handbook says, including when to reboot between = invocations of `freebsd-update`. As long as you follow exactly when it = instructs a reboot, and when to upgrade/reinstall userland and = packages/ports, you should be fine. If you=E2=80=99re still nervous, = just snapshot your boot EBS volume first as an extra precautionary = measure, and destroy it once you verify everything post-upgrade. -- Matt Garber
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8FE35DD1-6D07-4430-9706-A873E0D8ECCE>