Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/2013120
-
UI is not coming up.
So using the serial interface on this APU to see what is going on.
found in /conf the file upgrade_log.txt[2.4.0-RELEASE][admin@]/conf: cat upgrade_log.txt
Updating repositories metadata… done.
2.4.0 version of pfSense is available
Locking package pfSense-pkg-Service_Watchdog... done.
Locking package pfSense-pkg-nmap... done.
Locking package pfSense-pkg-squid... done.
Locking package pfSense-pkg-squidGuard... done.
Unlocking package pkg... done.
Reinstalling pkg due to ABI change...
pkg-static: Warning: Major OS version upgrade detected. Running "pkg-static ind
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):Installed packages to be REINSTALLED:
pkg-1.10.1_1 [pfSense] (ABI changed: 'freebsd:10:x86:64' -> 'freebsd:11)Number of packages to be reinstalled: 1
The process will require 1 MiB more space.
[1/1] Reinstalling pkg-1.10.1_1…
[1/1] Extracting pkg-1.10.1_1: …....... done
You may need to manually remove /usr/local/etc/pkg.conf if it is no longer need.Upgrading necessary core packages...
Checking for upgrades (2 candidates): .. done
Processing candidates (2 candidates): .. done
Checking integrity... done (0 conflicting)
The following 2 package(s) will be affected (of 0 checked):Installed packages to be UPGRADED:
pfSense-default-config: 2.3.4_1 -> 2.4.0 [pfSense-core]
pfSense-base: 2.3.4_1 -> 2.4.0 [pfSense-core]Number of packages to be upgraded: 2
The process will require 8 MiB more space.
[1/2] Upgrading pfSense-default-config from 2.3.4_1 to 2.4.0…
[1/2] Extracting pfSense-default-config-2.4.0: . done
[2/2] Upgrading pfSense-base from 2.3.4_1 to 2.4.0…
[2/2] Extracting pfSense-base-2.4.0: .. done
===> Keeping a copy of current version mtree
===> Removing schg flag from base files
===> Extracting new base tarballUnlocking package pfSense-pkg-Service_Watchdog… done.
Unlocking package pfSense-pkg-nmap... done.
Unlocking package pfSense-pkg-squid... done.
Unlocking package pfSense-pkg-squidGuard... done.Then I thought I run the upgrade
[2.4.0-RELEASE][admin@]/conf: pfSense-upgrade
Warning: PHP Startup: Unable to load dynamic library '/usr/local/lib/php/20131226/zmq.so' - /usr/local/lib/libsodium.so.180
Updating repositories metadata…
Updating pfSense-core repository catalogue...
pkg: Repository pfSense-core load error: access repo file(/var/db/pkg/repo-pfSense-core.sqlite) failed: No such file or diy
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-core/meta.txz: No address record
repository pfSense-core has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-core/packagesite.txz: No address record
Unable to update repository pfSense-core
Updating pfSense repository catalogue...
pkg: Repository pfSense load error: access repo file(/var/db/pkg/repo-pfSense.sqlite) failed: No such file or directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/meta.txz: No address record
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_0_amd64-pfSense_v2_4_0/packagesite.txz: No address record
Unable to update repository pfSense
Error updating repositories!What else can I try?
-
That must be an outdated copy of /usr/local/lib/php/20131226/zmq.so being referenced because it doesn't use that library any longer.
And the pkg errors indicate that it can't lookup and DNS requests.
The fastest method of recovery is a fresh installation if you can, then use the 'recover config.xml' option in the installer and it will read your current config in before wiping the drive and reinstalling, you'll boot back up good as new.