PHP Startup: Unable to load dynamic library 'intl.so'

[json]

@stephenw10 I would say that this topic reocurred now after upgrade to 2.6.0 so the issue is still not solved - suggestion above to reinstall icu component fixed the problem ;)

Currently I'm happy to be on pfSense Plus 22.01-RELEASE :) from Community upgrade

[json]

@jnz07 said in PHP Startup: Unable to load dynamic library 'intl.so':

@stephenw10 I would say that this topic reocurred now after upgrade to 2.6.0 so the issue is still not solved - suggestion above to reinstall icu component fixed the problem ;)

Currently I'm happy to be on pfSense Plus :) from Community upgrade

Ofc prior to it Backup, then Factory Reset then Restore from Backup, then icu reinstall then Reboot helped.

[stephenw10]

Hmm, so you saw it whilst upgrading from 2.5.2 to 2.6.0 first?

[json]

@stephenw10 Yes exactly from 2.5.2 to 2.6.0 and then after upgrade to 22.01

[stephenw10]

And you saw this error at both steps?

As before seeing that error during the upgrade but not afterwards is expected. Like:

[106/174] Reinstalling php74-pear-XML_RPC2-1.1.4...
[106/174] Extracting php74-pear-XML_RPC2-1.1.4: .......... done

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 (Cannot open "/usr/local/lib/php/20190902/intl.so.so")) in Unknown on line 0
uninstall ok: channel://pear.php.net/XML_RPC2-1.1.4

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 (Cannot open "/usr/local/lib/php/20190902/intl.so.so")) in Unknown on line 0
install ok: channel://pear.php.net/XML_RPC2-1.1.4
[107/174] Reinstalling php74-pear-Net_IPv6-1.3.0.b2_2...
[107/174] Extracting php74-pear-Net_IPv6-1.3.0.b2_2: ...... done

Seeing that is not a problem.

Steve

[crogerson]

I ran into the same issue on a SG-3100 going from 21.05.2 to 22.01 in my lab.

I had to unlock delete and install icu followed by a reboot as well.

[22.01-RELEASE][admin@pfSense.localdomain]/root: pkg delete -f icu
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0 packages in the universe):

Installed packages to be REMOVED:
icu: 62.1_2,1

Number of packages to be removed: 1

The operation will free 43 MiB.

Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling icu-62.1_2,1...
[1/1] Deleting files for icu-62.1_2,1: 88%
icu-62.1_2,1: missing file /usr/local/man/man1/derb.1.gz
[1/1] Deleting files for icu-62.1_2,1: 89%
icu-62.1_2,1: missing file /usr/local/man/man1/genbrk.1.gz
[1/1] Deleting files for icu-62.1_2,1: 89%
icu-62.1_2,1: missing file /usr/local/man/man1/gencfu.1.gz
[1/1] Deleting files for icu-62.1_2,1: 90%
icu-62.1_2,1: missing file /usr/local/man/man1/gencnval.1.gz
[1/1] Deleting files for icu-62.1_2,1: 90%
icu-62.1_2,1: missing file /usr/local/man/man1/gendict.1.gz
[1/1] Deleting files for icu-62.1_2,1: 90%
icu-62.1_2,1: missing file /usr/local/man/man1/genrb.1.gz
[1/1] Deleting files for icu-62.1_2,1: 91%
icu-62.1_2,1: missing file /usr/local/man/man1/icu-config.1.gz
[1/1] Deleting files for icu-62.1_2,1: 91%
icu-62.1_2,1: missing file /usr/local/man/man1/makeconv.1.gz
[1/1] Deleting files for icu-62.1_2,1: 92%
icu-62.1_2,1: missing file /usr/local/man/man1/pkgdata.1.gz
[1/1] Deleting files for icu-62.1_2,1: 92%
icu-62.1_2,1: missing file /usr/local/man/man1/uconv.1.gz
[1/1] Deleting files for icu-62.1_2,1: 92%
icu-62.1_2,1: missing file /usr/local/man/man8/genccode.8.gz
[1/1] Deleting files for icu-62.1_2,1: 93%
icu-62.1_2,1: missing file /usr/local/man/man8/gencmn.8.gz
[1/1] Deleting files for icu-62.1_2,1: 93%
icu-62.1_2,1: missing file /usr/local/man/man8/gensprep.8.gz
[1/1] Deleting files for icu-62.1_2,1: 94%
icu-62.1_2,1: missing file /usr/local/man/man8/icupkg.8.gz
[1/1] Deleting files for icu-62.1_2,1: 100%
[22.01-RELEASE][admin@pfSense.localdomain]/root: pkg install -yf 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.
The following 1 package(s) will be affected (of 0 checked):

New packages to be INSTALLED:
icu: 70.1_1,1 [pfSense]

Number of packages to be installed: 1

The process will require 47 MiB more space.
10 MiB to be downloaded.
[1/1] Fetching icu-70.1_1,1.pkg: 100% 10 MiB 3.6MB/s 00:03
Checking integrity... done (0 conflicting)
[1/1] Installing icu-70.1_1,1...
[1/1] Extracting icu-70.1_1,1: 100%
[22.01-RELEASE][admin@pfSense.localdomain]/root: exit
exit

[json]

@crogerson @stephenw10 so I guess it's still a problem so don't ignore it. Repro on my side and our colleague @crogerson as well.

[stephenw10]

If you're seeing it after the upgrade is complete or if you remove the error report and it returns at reboot then that's problem, yes.

[cbm44]

Sorry for replying to an older topic, but I just updated my Netgate 1100 from 21.05.2 to 22.05 in an effort to address some memory leak, and now I have the same problem as the OP. However a reboot does not make the errors go away, and I cannot access the firewall aliases nor rules without getting a fatal exception: Uncaught Error: Call to undefined function idn_to_utf8() in /etc/inc/util.inc:3744

I've followed hints above to reinstall icu to no avail, and finally resorted to upgrading to the 22.09-DEVEL release as it won't let me downgrade. I'm sure I could do a factory reset and restore my config, but I was hoping for a better option. The previous reply from February suggests this problem may still exist, so that's why I'm posting. Personally I feel like the 22.05 upgrade was not entirely successful, because it was still reporting there was a 22.05 update available, but I'm not entirely sure.

Chris

[stephenw10]

Yes, it almist certainly didn't upgrade fully for some reason.

If you're on 22.09 now though the only way go back is to reinstall. Unless you were already running ZFS and can use Boot Envs.

Steve