Synopsis:
I have 3 web servers running FreeBSD 11.4 and I want to upgrade them to 12.2. I upgraded one last night and ran into some issues I've never seen before in past FreeBSD updates. I'm always trying to learn new things and I figured maybe I haven't been doing things properly in the past, even though they seemed to work. What's the best way?
Details:
I updated the server to FreeBSD 12.2 using the normal procedure described in the docs. No issues.
Maybe I did something wrong (it was 3am of course) but my usual method of updating all of my third party apps is to:
This has worked fine on all 3 servers, for the past few years. Sometimes I have to make some adjustments noted in
But when portupgrade was trying to update Apache, it stopped. So, I went to do the update manually and got this...
Next, I tried Googling and found a few people experiencing the same thing, but from 1 or 2 years ago, and no clear solutions. I did notice one person said he used
WOAH!! Why are all of those FreeBSD 11 packages still on my system??? Did I not use the right options with
Did I do something else wrong??
After I completed the above
So, I must have done something wrong that caused a bunch of FreeBSD 11 stuff to remain on my system and cause issues. But what? And how can I be sure there still aren't packages from 11 lingering around? I'm trying to figure out the best approach to take when I upgrade the other 2 servers. This one is a backup server but the other 2 have live, client web sites on them.
Thanks!! P.S. I love this forum <3
I have 3 web servers running FreeBSD 11.4 and I want to upgrade them to 12.2. I upgraded one last night and ran into some issues I've never seen before in past FreeBSD updates. I'm always trying to learn new things and I figured maybe I haven't been doing things properly in the past, even though they seemed to work. What's the best way?
Details:
I updated the server to FreeBSD 12.2 using the normal procedure described in the docs. No issues.
Maybe I did something wrong (it was 3am of course) but my usual method of updating all of my third party apps is to:
Code:
# portsnap fetch && portsnap update
# portupgrade -urRa
This has worked fine on all 3 servers, for the past few years. Sometimes I have to make some adjustments noted in
/usr/ports/UPDATING
but everything usually works well. But when portupgrade was trying to update Apache, it stopped. So, I went to do the update manually and got this...
Code:
# cd /usr/ports/www/apache24
# make install clean
...
unixd.c:245:25: error: variable has incomplete type 'union semun'
union semun ick;
^
unixd.c:245:19: note: forward declaration of 'union semun'
union semun ick;
^
1 error generated.
*** [unixd.lo] Error code 1
make[5]: stopped in /usr/ports/www/apache24/work/httpd-2.4.48/os/unix
1 error
make[5]: stopped in /usr/ports/www/apache24/work/httpd-2.4.48/os/unix
*** [all-recursive] Error code 1
make[4]: stopped in /usr/ports/www/apache24/work/httpd-2.4.48/os/unix
1 error
make[4]: stopped in /usr/ports/www/apache24/work/httpd-2.4.48/os/unix
*** [all-recursive] Error code 1
make[3]: stopped in /usr/ports/www/apache24/work/httpd-2.4.48/os
1 error
make[3]: stopped in /usr/ports/www/apache24/work/httpd-2.4.48/os
*** [all-recursive] Error code 1
make[2]: stopped in /usr/ports/www/apache24/work/httpd-2.4.48
1 error
make[2]: stopped in /usr/ports/www/apache24/work/httpd-2.4.48
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop.
Next, I tried Googling and found a few people experiencing the same thing, but from 1 or 2 years ago, and no clear solutions. I did notice one person said he used
pkg
to install apache24 and it worked, so I tried that and found some interesting (to me, lol) output:
Code:
# pkg install apache24
Updating FreeBSD repository catalogue...
Fetching meta.conf: 100% 163 B 0.2kB/s 00:01
pkg: http://pkgmir.geo.freebsd.org/FreeBSD:12:amd64/quarterly/packagesite.pkg: Not Found
Fetching packagesite.txz: 100% 6 MiB 6.6MB/s 00:01
Processing entries: 100%
FreeBSD repository update completed. 30844 packages processed.
All repositories are up to date.
Updating database digests format: 100%
The following 19 package(s) will be affected (of 0 checked):
New packages to be INSTALLED:
apache24: 2.4.48
mozjpeg: 4.0.3
Installed packages to be REINSTALLED:
apr-1.7.0.1.6.1_1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
db5-5.3.28_7
freetype2-2.10.4
giflib-5.2.1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
jansson-2.13.1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
jbigkit-2.1_1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
json-c-0.15_1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
libedit-3.1.20210216,1
libgd-2.3.1,1 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
libunistring-0.9.10_1
libunwind-20201110 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
libyaml-0.2.5 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
pcre-8.44
png-1.6.37_1
tiff-4.3.0 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
webp-1.2.0 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
wget-1.21 (ABI changed: 'freebsd:11:x86:64' -> 'freebsd:12:x86:64')
Number of packages to be installed: 2
Number of packages to be reinstalled: 17
WOAH!! Why are all of those FreeBSD 11 packages still on my system??? Did I not use the right options with
portupgrade
??Did I do something else wrong??
After I completed the above
pkg
command, I did an experiment to see if I could reinstall apache24 from ports... AND IT WORKED!! No errors.So, I must have done something wrong that caused a bunch of FreeBSD 11 stuff to remain on my system and cause issues. But what? And how can I be sure there still aren't packages from 11 lingering around? I'm trying to figure out the best approach to take when I upgrade the other 2 servers. This one is a backup server but the other 2 have live, client web sites on them.
Thanks!! P.S. I love this forum <3