PHP Warning: PHP Startup: Unable to load dynamic library 'intl.so' (tried: /usr/local/lib/php/20190902/intl.so (Shared object "libicuio.so.69" not found, required by "intl.so"), /usr/local/lib/php/20190902/intl.so.so (/usr/local/lib/php/20190902/intl.so.
-
I'm having the same issue. After clearing & reboot, the problem persists:
PHP Errors: [10-Jul-2021 05:49:10 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'intl.so' (tried: /usr/local/lib/php/20190902/intl.so (Shared object "libicuio.so.69" not found, required by "intl.so"), /usr/local/lib/php/20190902/intl.so.so (/usr/local/lib/php/20190902/intl.so.so: invalid file format)) in Unknown on line 0 [10-Jul-2021 05:49:10 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'intl.so' (tried: /usr/local/lib/php/20190902/intl.so (Shared object "libicuio.so.69" not found, required by "intl.so"), /usr/local/lib/php/20190902/intl.so.so (/usr/local/lib/php/20190902/intl.so.so: invalid file format)) in Unknown on line 0 [...]cat /cf/conf/upgrade_log.txt >>> Setting vital flag on php74... done. >>> Updating repositories metadata... done. Your system is up to dateEdit: I don't have icu69, and it doesn't seem to be available
pkg upgrade -f icu-69.1,1 [...] pkg: icu-69.1,1 is not installed, therefore upgrade is impossible`There seem to exist various files in /tmp based on these error messages:
"intl.so"), "libicuio.so.69" 'intl.so' (Shared (tried: [...] -
For now disabled intl in
/usr/local/etc/php/ext-20-intl.ini... -
You should look at /conf/upgrade_log.latest.txt which should show the actual upgrade.
You should just install that pkg if for some reason it's missing:
pkg install icuIf it failed to upgrade though you have specified the full pkg version so it may not see that. Try:
pkg upgrade -f icuSteve
-
cat /conf/upgrade_log.txt Your system is up to dateicu is definitely installed but the only available version is
68.2,1-- but php wants version 69.* -
Your "/conf/upgrade_log.latest.txt" contains just that line ?
My "/conf/upgrade_log.latest.txt" contains the entire "2.5.2" upgrade process, 1111 lines.
It shows :
.... icu: 68.2,1 -> 69.1,1 [pfSense] ....My icu has version 69.1.1 on my "2.5.2" :
pkg search icu icu-69.1,1 International Components for Unicode (from IBM) -
Yeah if you're not seeing that it's looking at the wrong package branch I would suggest.
Also upgrade_log.txt is not upgrade_log.latest.txt which should show the actual upgrade.
Steve
-
@stephenw10
I don't have upgrade_log.latest.txt, only upgrade_log.txt -- and that's all it has in it.Here's what I see
[2.5.2-RELEASE][root@pfSense.fry.lan]/root: pkg search icu icu-69.1,1 International Components for Unicode (from IBM) [2.5.2-RELEASE][root@pfSense.fry.lan]/root: pkg info icu icu-68.2,1 Name : icu Version : 68.2,1 Installed on : Wed Feb 17 20:41:55 2021 PST Origin : devel/icu Architecture : FreeBSD:12:amd64 Prefix : /usr/local Categories : devel Licenses : ICU Maintainer : office@FreeBSD.org WWW : http://site.icu-project.org/ Comment : International Components for Unicode (from IBM) Shared Libs provided: libicui18n.so.68 libicuuc.so.68 libicuio.so.68 libicutu.so.68 libicutest.so.68 libicudata.so.68 Annotations : FreeBSD_version: 1202504 repo_type : binary repository : pfSense Flat size : 48.7MiB Description : The International Components for Unicode (ICU) is a C and C++ library providing Unicode support (ex. character set conversions, locales, normalization, transliteration, etc.). More information on ICU can be found on the homepage WWW: http://site.icu-project.org/ [2.5.2-RELEASE][root@pfSense.fry.lan]/root: pkg install -f icu Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. Checking integrity... done (0 conflicting) The most recent versions of packages are already installed -
Hmm, looks like the upgrade never completed then maybe?
I would re-install clean and restore the config if you can. It's hard to say what state that system is in. 2.5.2 should have icu-69. Did you try force upgrading the package like I showed above?
Steve
-
If someone still has one in this state, show the output of the following commands:
pkg version -vL=pkg info -qpkg check -s |& egrep -v '(Checking all|local/man|share/doc|\.dtd$|\.sample2*$|\.m4$)'
That last command may still show some other expecting items depending on packages you have installed.
-
I ran into this on a machine that is running the Unifi wifi controller. Reinstalling the Unifi controller pulled in the newer version of ICU. The Unifi installer for pfSense, while fantastically useful, is a bit of a dirty hack, and it has caused me grief on upgrades before.
For reference: https://github.com/unofficial-unifi/unifi-pfsense/blob/master/README.md
-
@bfeitell said in PHP Warning: PHP Startup: Unable to load dynamic library 'intl.so' (tried: /usr/local/lib/php/20190902/intl.so (Shared object "libicuio.so.69" not found, required by "intl.so"), /usr/local/lib/php/20190902/intl.so.so (/usr/local/lib/php/20190902/intl.so.:
I ran into this on a machine that is running the Unifi wifi controller. Reinstalling the Unifi controller pulled in the newer version of ICU. The Unifi installer for pfSense, while fantastically useful, is a bit of a dirty hack, and it has caused me grief on upgrades before.
For reference: https://github.com/unofficial-unifi/unifi-pfsense/blob/master/README.md
It wouldn't surprise me if others in similar situations had similar causes (meaning packages from alternate repositories). If a package from some other source clobbered the "correct" version of icu/intl/whatever then it could be left in a broken state on upgrade.
Not much we can do about that, though, since that's all up to the end user to manage.
Still need more information from others before we can say for sure what might have led to that situation.
-
@jimp
I also have the unifi controller installed from that source. I don't think I upgraded it after the pfsense upgrade, I guess it got clobbered before the upgrade then?: pkg version -vL= Updating pfSense-core repository catalogue... pfSense-core repository is up to date. Updating pfSense repository catalogue... pfSense repository is up to date. All repositories are up to date. alsa-lib-1.1.2_2 ? orphaned: audio/alsa-lib boost-libs-1.72.0_3 < needs updating (remote has 1.72.0_5) dejavu-2.37_1 ? orphaned: x11-fonts/dejavu fontconfig-2.13.92_2,1 < needs updating (remote has 2.13.93,1) icu-68.2,1 < needs updating (remote has 69.1,1) java-zoneinfo-2021.a ? orphaned: java/java-zoneinfo javavmwrapper-2.7.6 ? orphaned: java/javavmwrapper libICE-1.0.10,1 ? orphaned: x11/libICE libSM-1.2.3,1 ? orphaned: x11/libSM libX11-1.6.12,1 ? orphaned: x11/libX11 libXau-1.0.9 ? orphaned: x11/libXau libXdmcp-1.1.3 ? orphaned: x11/libXdmcp libXext-1.3.4,1 ? orphaned: x11/libXext libXfixes-5.0.3_2 ? orphaned: x11/libXfixes libXi-1.7.10,1 ? orphaned: x11/libXi libXrender-0.9.10_2 ? orphaned: x11/libXrender libXt-1.2.0,1 ? orphaned: x11-toolkits/libXt libXtst-1.2.3_2 ? orphaned: x11/libXtst libpthread-stubs-0.4 ? orphaned: devel/libpthread-stubs libxcb-1.14_1 ? orphaned: x11/libxcb mongodb36-3.6.22 ? orphaned: databases/mongodb36 openjdk8-8.282.08.1 ? orphaned: java/openjdk8 python37-3.7.9_1 ? orphaned: lang/python37 snappy-1.1.8 ? orphaned: archivers/snappy snappyjava-1.1.7.5 ? orphaned: archivers/snappy-java unzip-6.0_8 ? orphaned: archivers/unzip xorgproto-2020.1 < needs updating (remote has 2021.4)ugh.. guess I'll have to reinstall after all :\
-
It at least sees those updates available. I would probably re-install to be sure you have a clean install but you could try a force re-install for all packages.
https://docs.netgate.com/pfsense/en/latest/troubleshooting/upgrades.html#forced-pkg-reinstallSteve
-
Had the issue when upgrading from 2.5.x to 2.6.0…
Came to success after enabling « admin » account to enable root privileges over ssh and be able to unlock « icu-68.2,1 » and update it to « icu-70.1_1,1 » :
pkg unlock icu pkg delete -f icu pkg install -yf icuTrying to « simply » update the « icu » package wasn't working…
-
@lange-ludo Thanks, I had the same issue upgrading to 2.6.0 and this fixed it for me.
