[SOLVED] PHP.ini points to wrong extensions directory.
I had been playing with IPv6 settings and couldn't get an IP from the provider anymore so I assumed a reboot would fix that.
The device didn't come back online after the reboot so I hooked it up to my mac and saw a lot of php extension errors.
It looks like the php.ini still points to an older release (20131226) instead of the current 20170718 directory.
I've tried editing the php.ini file but it seems that doesn't survive a reboot so I've now sym-linked 20131226 > 20170718.
Can anyone tell me how this happened and what I can do to fix it permanently?
Sounds more like you installed a current package into an old and unsupported base system, do a fresh install with a current pfSense version.
It's a brand new, shiny, sparkling install. Just received the hardware last week & the system says all it up to date. I've been installing and uninstalling a few packages (Snort, ACME, ntopng, ...) but nothing outside of the regular package manager.
It's a brand new, shiny, sparkling install. Just received the hardware last week & the system says all it up to date.
Official hardware? If not, never trust a preinstalled pfSense, there have been occasion where they were compromised before.
Show a screenshot from the version information on the dashboard.
It's a blank PCEngines. Started from scratch with the official image on a USB stick.
I found where it get the dir from:
in /etc/rc.php_ini_setup it says
if pkg info -e php72; then PHP_VER=7 EXTENSIONSDIR="/usr/local/lib/php/20170718/" else PHP_VER=5 EXTENSIONSDIR="/usr/local/lib/php/20131226/" fi
and when running :
[2.4.4-RELEASE][admin@pfSense.mylocal]/root: pkg info -e php72 Shared object "libssl.so.111" not found, required by "pkg"
So I'll probably need to solve that one.
Yes. So I succeeded in breaking the thing :)
Fixed it by downgrading PKG & running it again.
Now the /usr/local/etc/php.ini says :
I ran these commands :
pkg-static install -f pkg pkg upgrade -f
FYI- Looks like you set it to pull updates from the 2.5.0 development snapshots but didn't upgrade to 2.5.0.