FreeBSD 15.0-RELEASE: Trouble after upgrade
Date: Tue, 02 Dec 2025 12:21:51 UTC
I have upgraded my FreeBSD 14.3-RELEASE to 15.0-RELEASE using freebsd update. There is trouble in paradise: 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" Dec 2 15:13:00 gw /usr/sbin/cron[89387]: in openpam_load_module(): no pam_nologin.so found Dec 2 15:13:00 gw /usr/sbin/cron[88206]: in openpam_load_module(): no pam_nologin.so found Dec 2 15:14:00 gw /usr/sbin/cron[46876]: in try_dlopen(): /usr/lib/pam_nologin.so.6: /lib/libutil.so.10: Undefined symbol "initgroups@FBSD_1.8" Dec 2 15:14:00 gw /usr/sbin/cron[46846]: in try_dlopen(): /usr/lib/pam_nologin.so.6: /lib/libutil.so.10: Undefined symbol "initgroups@FBSD_1.8" Dec 2 15:14:00 gw /usr/sbin/cron[46876]: in openpam_load_module(): no pam_nologin.so found Dec 2 15:14:00 gw /usr/sbin/cron[46846]: in openpam_load_module(): no pam_nologin.so found Dec 2 15:15:00 gw /usr/sbin/cron[53989]: in try_dlopen(): /usr/lib/pam_nologin.so.6: /lib/libutil.so.10: Undefined symbol "initgroups@FBSD_1.8" Dec 2 15:15:00 gw /usr/sbin/cron[53989]: in openpam_load_module(): no pam_nologin.so found Dec 2 15:15:00 gw /usr/sbin/cron[54892]: in try_dlopen(): /usr/lib/pam_nologin.so.6: /lib/libutil.so.10: Undefined symbol "initgroups@FBSD_1.8" Dec 2 15:15:00 gw /usr/sbin/cron[54892]: in openpam_load_module(): no pam_nologin.so found Dec 2 15:15:00 gw /usr/sbin/cron[55782]: in try_dlopen(): /usr/lib/pam_nologin.so.6: /lib/libutil.so.10: Undefined symbol "initgroups@FBSD_1.8" Dec 2 15:15:00 gw /usr/sbin/cron[55782]: in openpam_load_module(): no pam_nologin.so found But: root@gw:/ # ls -al /usr/lib/pam_nologin* lrwxr-xr-x 1 root wheel 16 Dec 7 2018 /usr/lib/pam_nologin.so -> pam_nologin.so.6 -r--r--r-- 1 root wheel 6640 Dec 2 14:04 /usr/lib/pam_nologin.so.6 root@gw:/ # And now I cannot SSH to the server. It's a VM in Proxmox so I can still access it via the console. However, my terminal is full of the above errors. -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254 7 3200 0004/+254 7 2274 3223 In an Internet failure case, the #1 suspect is a constant: DNS. "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-) [How to ask smart questions: http://www.catb.org/~esr/faqs/smart-questions.html]