Unable to load dynamic Library

[Druplex]

[19-May-2020 09:24:23 UTC] PHP Warning: PHP Startup: Unable to load dynamic library 'readline.so' (tried: /usr/local/lib/php/20170718/readline.so (Shared object "libreadline.so.7" not found, required by "readline.so"), /usr/local/lib/php/20170718/readline.so.so (/usr/local/lib/php/20170718/readline.so.so: invalid file format)) in Unknown on line 0

[Gertjan]

Hi,

What pfSense version ?
Did you install something lately ?

See also the many other "so.so" forum messages.

[Druplex]

@Gertjan am on 2.4.4-p3, i had upgraded to 2.4.5 but gave me the same same error so i just reverted back and the error is still on.
And nop, i have not installed anything off late. the pfsense box only has one active open vpn service.

[Gertjan]

@Druplex said in Unable to load dynamic Library:

@Gertjan am on 2.4.4-p3, i had upgraded to 2.4.5 but gave me the same same error so i just reverted back and the error is still on.

Ok.
Packages were updated / upgraded to support 2.4.5 and PHP dependencies.
You can't upgrade packages using and 'old' version of pfSense like 2.4.4-p3 if a 2.4.5 exists, as the package could actually need (example) PHP 7.2.b) while pfSense 2.4.4-p3 is using 7.2.a.
There will be a PHP library version mismatch. That what you are seeing.

Normally, when you upgrade pfSense, you don't stop there.
The list with installed packages will also get updated, and show you if any packages should be upgraded. At that moment, these upgrade might not be optional, as they could use old (PHP) libraries, and pfSense just replaced them with more recent ones. This explains the error you saw.
Just finish upgrading, and all will be fine.

Downgrading pfSense will not help here.

Golden rule : Do not install/upgrade (use ?) packages any more as soon as a new version of pfSense comes out and you decide to stay on the old version.
That is : closely observe what sub packages, like PHP, get installed with it them. Some will work on neraly any version of pfSense, some use a lot of shared resources with the OS or other pfSense core files, and need to get upgraded - at least re installed.

See Netgate release notes. Netgate's upgrade video and the huge quantity of forum posts about the subject.

Keep in mind : most packages are created by people like you and me. Package maintainers should only have to support their package using the latest pfSense version. No one want to make a package installable on all kind of recent and ancient pfSense version (like Microsoft doesn't support his older versions neither, it's just to much of o job).