Re: Upgrading 11.2 -> 12.0 on EC2
> On Dec 19, 2018, at 1:24 PM, Brian Neal wrote: > > 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. I’m assuming that error, ‘sockstat input size mismatch’, was encountered during the very first reboot to the new 12.0 kernel? In that case, perhaps there’s an EC2-specific issue at play, since at that point userland and package updates haven’t even come into the picture yet. I’ve performed several 11.2 -> 12.0 upgrades on Digital Ocean (KVM hypervisor) within the past week without any kernel problems, but in your case the safest choice could simply be new instances, one of the things thankfully made nicest by the various cloud providers. I’d also very much recommend looking into some kind of new system automation to make things easier for you – whether it’s a full-blown official thing like Ansible or Puppet, or even just maintaining a giant shell script which you can use on fresh instances, so you’re not having to re-edit config. files by hand each time. -- Matt Garber ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading 11.2 -> 12.0 on EC2
On 12/18/18 10:50 PM, Brian Neal wrote: Hello, 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? I've done it successfully in the past but IIRC it was pretty sketchy - i think i put script in /etc/rc.local to finish the upgrade. for dev purposes i've done upgrades via rebuilding from source without too much drama. i'd due to the build/mergemasters and installworld before a reboot. but again this was for dev/testing, so if things didn't work out loosing data was a non-issue. I've since decided that one of the advantages of AWS is that I can easily just allocate a new VM, but this is predicated that I've got all my configs in a config mgmt engine and my user volumes exist on an EBS volume. -pete -- Pete Wright p...@nomadlogic.org @nomadlogicLA ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Upgrading 11.2 -> 12.0 on EC2
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 wrote: > > >> On Dec 19, 2018, at 1:50 AM, Brian Neal 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 > smime.p7s Description: S/MIME cryptographic signature
Re: Upgrading 11.2 -> 12.0 on EC2
> On Dec 19, 2018, at 1:50 AM, Brian Neal 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 ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Upgrading 11.2 -> 12.0 on EC2
Hello, 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? Cheers, -Brian ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
