Well, that's two of my three #FreeBSD servers upgraded to 14.4. The process went smoothly as always.

The third one is already on 15.0, but I need to understand some of its hiccups before I'll consider upgrading the two more important servers to it also.

@tgeusch You rebooted after the first round of FreeBSD-Update, and then...

ld-elf.so.1: Shared object "libsys.so.7" not found, required by "libc.so.7"

Solution adapted from https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=289769#c16

cd /tmp
/rescue/fetch https://download.freebsd.org/releases/amd64/15.0-RELEASE/base.txz
/rescue/tar zxf base.txz lib/libsys.so.7
/rescue/cp -v lib/libsys.so.7 /lib

/usr/sbin/freebsd-update

Probably should've done a pkg upgrade first - although that doesn't seemed to have helped on another 14->15 upgrade attempt.

289769 – libsys.so.7 not found when upgrading userland with legacy freebsd-update

@mWare I didn't hit that problem when upgrading to 15.0. I am running into some subtle issues that look like they're caused by a newer compiler handling some symbols differently, but I haven't had much time to investigate yet as I managed to find a quick workaround.

For example, lua-cqueues complains about a missing symbol that is actually a function in its own source code, which then breaks my kresd configuration. And I want to produce a somewhat better bug report than "it seems to be broken on 15.0".

@tgeusch I've done a couple dozen 14->15 uprades, and hit that problem now 3 times. Really not sure what makes the start point different, but I figured I'd copy my (edited) wiki notes here just in case someone else hits it :)

pkgbase is not on these systems.

@mWare I didn't pkgbaseify my one upgrade either, figured that one major change at a time is enough. While these servers are all part of my homelab or my self-hosted email, I'm not worried about them being on the latest major release as long as they're on a supported release and Just Work.

Thanks for sharing your wiki notes, they are helpful.

@tgeusch You're welcome, high tides lift all ships!

Also hosting email, that's #hardmode ;)

@mWare #email #selfHosting has definitely become #hardmode. I've done it for so long that I'm sticking with it for now simply because moving all of the domains to a hosted email like Tuta or Proton would be a bit of an expensive endeavour.
@tgeusch I'm hosting a couple hundred mailboxes on ArchiveOpteryx now, and am looking to deploy a (licensed) Stalwart cluster within a year. I'm always curious what the market is charging, and how much interest there is in >DEFINITELY< in Canada hosting.

@mWare oddly enough as someone who lives in your neighbourhood to the South, I'm thinking about diversifying my hosting strategy a little more internationally because ... reasons.

I'm only hosting a handful of mailboxes for friends & family and myself, but a few decades of collecting domains means there are more domains than people who I need to host somewhere.

@tgeusch I started off doing it for the novelty and offered to help everyone do it; later when operating as a business, I discovered the perils of doing something for free: people don't cancel.