Skip site navigation (1)Skip section navigation (2) 
Date:      Wed, 19 Dec 2018 10:24:39 -0800
From:      Brian Neal <brian@aceshardware.com>
To:        Matt Garber <matt.garber@gmail.com>
Cc:        "freebsd-stable@freebsd.org" <freebsd-stable@freebsd.org>
Subject:   Re: Upgrading 11.2 -> 12.0 on EC2
Message-ID:  <68E503D2-A227-4662-9A72-F74D66BF32E9@aceshardware.com>
In-Reply-To: <8FE35DD1-6D07-4430-9706-A873E0D8ECCE@gmail.com>
References:  <5c19ea68.1c69fb81.1febf.ddb2SMTPIN_ADDED_MISSING@mx.google.com> <8FE35DD1-6D07-4430-9706-A873E0D8ECCE@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help 

[-- Attachment #1 --]
Thanks, Matt. I did try the update procedure from the handbook and found the instance hanging on boot with a repeated socket error. If I have to rebuild from scratch, I’d prefer to find some jail/deployment-automation so I don’t have to manually rebuild everything on each release. FWIW, I did have to recreate the instance when moving from 10 to 11.

Cheers,

-Brian

> On Dec 19, 2018, at 7:33 AM, Matt Garber <matt.garber@gmail.com> wrote:
> 
> 
>> On Dec 19, 2018, at 1:50 AM, Brian Neal <brian@aceshardware.com> wrote:
>> 
>> I’m 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’s 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 – and of course potentially using `pkg-static` or ports to rebuild/reinstall your packages/ports against the new ABI.
> 
> If you’re 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 “safe” 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’re 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
> 

[-- Attachment #2 --]
0	*H
010
	`He0	*H
00נ@b%^"10
	*H
0:10	UUS10U
	IdenTrust10UTrustID CA A120
180314183331Z
190314183331Z01/0-U&Verified Email: brian@aceshardware.com1%0#	*H
	brian@aceshardware.com1/0-
	&,dA01427D0000016225C9E54C000172F10"0
	*H
0
r_=`{:Y0
O1%8bx4ypw@?Y`a{C>%&^Ί\S␞E[V	ɍ<SJYY蒑~^`MQ	 ɥmM_eϱ*}'V)chLalٳpݱI
E^m`5xu̝a|,$e})쓛d?}΃T{Iꮅj5_(lx)00U0+x0v00+0$http://commercial.ocsp.identrust.com0B+06http://validation.identrust.com/certs/trustidcaa12.p7c0U#0si5u̠{2kB0	U00,U #00`H/0
0J+>https://secure.identrust.com/certificates/policy/ts/index.html0+0This TrustID Certificate has been issued in accordance with 
IdenTrust's TrustID Certificate Policy found at https://secure.identrust.com/certificates/policy/ts/index.html0EU>0<0:864http://validation.identrust.com/crl/trustidcaa12.crl0!U0brian@aceshardware.com0U
3')$ֹUJp|0U%0++0
	*H
lMXySVdXy0`윋r65]89?V0bz3N7Jq<2!L`{(+NR25	edk`6cr_)j%ǂ50rCڤR}ShYJ9V\AܲUmhi)^|ĩAK`c$;p@ײ,7{		%V
Bт[?S(#CC2szø؎2F.xt100N0:10	UUS10U
	IdenTrust10UTrustID CA A12@b%^"10
	`He)0	*H
	1	*H
0	*H
	1
181219182440Z0/	*H
	1" 8@X6?9ruEzz0]	+71P0N0:10	UUS10U
	IdenTrust10UTrustID CA A12@b%^"10_*H
	1PN0:10	UUS10U
	IdenTrust10UTrustID CA A12@b%^"10
	*H
e"t`ZAC	xJE&uKqξ0/D%PVعQ\ABJ6/#JQ(gvҏh^Pr{&ͺpG($@t^+s/x`MJ\	UNaD#"U_
GߡX=:g8I5w&,,S,Tiΰ>	)؛-O^D߂D42KáUt8v88=hf
Wu2G1GI)#/

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?68E503D2-A227-4662-9A72-F74D66BF32E9>