If you're migrating from mysql57-* to mysql80-*, watch out for other ports which may be linked to the shared MySQL 5.7 library:
If this gives you any results, those ports will probably need to be rebuilt after you upgrade MySQL. I got snagged by this with dns/bind916, which I have configured with the DLZ_MYSQL option enabled. When I rebooted that machine this afternoon, the named service didn't start, and upon investigating, it was still looking for the old MySQL 5.7 library:
This was fixed by doing a
I compile ports from source instead of using pkg-add(8), YMMV.
Code:
[root@host ~]# pkg shlib -qR libmysqlclient.so.20
If this gives you any results, those ports will probably need to be rebuilt after you upgrade MySQL. I got snagged by this with dns/bind916, which I have configured with the DLZ_MYSQL option enabled. When I rebooted that machine this afternoon, the named service didn't start, and upon investigating, it was still looking for the old MySQL 5.7 library:
Code:
[root@host /var/log/named]# service named start
Starting named.
ld-elf.so.1: Shared object "libmysqlclient.so.20" not found, required by "named"
/usr/local/etc/rc.d/named: WARNING: failed to start named
This was fixed by doing a
make clean deinstall reinstall
on dns/bind916, which linked it against the new library.I compile ports from source instead of using pkg-add(8), YMMV.
Last edited by a moderator: