Re: FreeBSD 15.0-RELEASE: Trouble after upgrade

From: Dave Cottlehuber <dch_at_skunkwerks.at>
Date: Tue, 02 Dec 2025 15:47:32 UTC 
On Tue, 2 Dec 2025, at 15:40, Odhiambo Washington wrote:
> On Tue, Dec 2, 2025 at 6:33 PM Dave Cottlehuber <dch@skunkwerks.at> wrote:
>> On Tue, 2 Dec 2025, at 12:21, Odhiambo Washington wrote:
>> > I have upgraded my FreeBSD 14.3-RELEASE to 15.0-RELEASE using freebsd update.
>> >
>> > There is trouble in paradise:
>> 
>> Hi Odhiambo,
>> 
>> Oh dear :-(
>> 
>> > Dec  2 15:13:00 gw /usr/sbin/cron[88206]: in try_dlopen(): 
>> > /usr/lib/pam_nologin.so.6: /lib/libutil.so.10: Undefined symbol 
>> > "initgroups@FBSD_1.8"
>> > Dec  2 15:13:00 gw /usr/sbin/cron[89387]: in try_dlopen(): 
>> > /usr/lib/pam_nologin.so.6: /lib/libutil.so.10: Undefined symbol 
>> > "initgroups@FBSD_1.8"
>> 
>> I'm guessing userland & kernel are out of sync, did you run
>> freebsd-update both before & after reboot?
>
> Yes, I did.
> I thought I had all this in my head.
> freebsd-update upgrade -r 15.0-RELEASE; freebsd-update install; reboot; 
> freebsd-update install; reboot

It's important to first ensure you're on the latest patches from your
currently supported release, *before upgrading*.

This is the first step in Upgrading using "freebsd update":

https://www.freebsd.org/releases/15.0R/installation/#upgrade-binary

This ensures you have amongst other patches, https://www.freebsd.org/security/advisories/FreeBSD-EN-25:18.freebsd-update.asc which may explain the symptoms.

> I must have forgotten about the last reboot, because after it, some 
> issues resolved themselves.
> 
>> Try running `freebsd-update install` again, and see if that
>> sorts it.

>> What does `freebsd-version -kru` show you?
>> 
>> ditto for `uname -a`?
>
> root@gw:/usr/ports/emulators/qemu # freebsd-version -kru
> 15.0-RELEASE
> 15.0-RELEASE
> 15.0-RELEASE
> root@gw:/usr/ports/emulators/qemu # uname -a
> FreeBSD gw.wash.lan 15.0-RELEASE FreeBSD 15.0-RELEASE 

These look fine, modulo the previous issues.

A+
Dave