Error after upgrade to 2.4.3-p1: “PHP ERROR: Type: 64 (…)”

[eric35]

After upgrade to 2.4.3-p1 I see on the console the following new error message (my hardware is RCC-VE 4860):

PHP ERROR: Type: 64, File: /usr/local/captiveportal/radius_authentication.inc, Line: 43, Message: require_once(): Failed opening required 'Crypt/CHAP.php' (include_path='.:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg:/usr/local/www/classes:/usr/local/www/classes/Form:/usr/local/share/pear')Netgate SG-4860”.

What is the issue and the best way to resolve?

[jimp]

pkg install -yf security/pear-Crypt_CHAP

Though if that is missing, it's hard to tell what else might be. You could reinstall everything with pkg clean -ay; pkg upgrade -f

[eric35]

Thank you, Jimp. My reinstall attempt per your suggestion failed (console log below). I hope you'll have a follow up...

2.4.3-RELEASE][admin@]/var/db/pkg: ls
local.sqlite pfSense-core.meta pfSense.meta
[2.4.3-RELEASE][admin@]/var/db/pkg: pkg clean -ay; pkg upgrade -f
pkg: Repository pfSense-core missing. 'pkg update' required
pkg: No package database installed. Nothing to do!
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 directory
pkg: https://pkg.pfsense.org/pfSense_v2_4_3_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_3_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_3_amd64-pfSense_v2_4_3/meta.txz: No address record
repository pfSense has no meta file, using default settings
pkg: https://pkg.pfsense.org/pfSense_v2_4_3_amd64-pfSense_v2_4_3/packagesite.txz: No address record
Unable to update repository pfSense

[jimp]

Fix your DNS and/or WAN connectivity on pfSense. Something is preventing it from resolving the hostname of the update server, which could be broken DNS or could be broken connectivity (missing default gateway, etc)

[eric35]

Thx again. I do not have any WAN connectivity on pfsense. I lost it after my upgrade attempt to 2.4.3. The only access I have is through the console. At this point should I flash the new 2.4.3 firmware and reconfigure all?

[jimp]

A reinstall is probably easiest.

If your WAN is DHCP you might be able to get away with running dhclient em0 where em0 is the actual WAN interface. If it's static or something else it could be done but it would be more difficult.

When you reinstall, choose the option to recover config.xml and it will pull your current settings back in.