Hi all,
The upgrade of an OPNsense firewall from 19 -> 20 just failed. I am running OPNsense as VM on a Xen host, which has worked beautifully since 17.x or so. I initiated the upgrade in the evening and noticed the firewall was unresponsive in the morning after which I virtually powercycled the VM.
The boot process crashes with a Fatal Error:
Uncaught Error: Call to undefined function OPNsense\Core\ctype_digit() in /usr/local/opnsense/mvc/app/library/OPNsense/Core/Config.php:82. Line 82 contains:
return ctype_digit(implode('', array_keys($arrayData)));
See attached screenshot.
Any suggestions how I can pull OPNsense off the ground?
kind regards,
Jan
Try to get a connection to the internet, usually via DHCP through your physical WAN interface, e.g.:
# dhclient em0
Then bootstrap again...
# opnsense-bootstrap
It looks like your disk did not retain all files during the upgrade.
Cheers,
Franco
Hi Franco,
Thanks for the quick response :-)
After bringing OPNsense online, I did:
# opnsense-bootstrap
# reboot
and I end up with the same Fatal Error. In other words opnsense-bootstrap completed very quickly (didn't appear to download anything from the internet or did it with the speed of light).
What could be the reason for not retaining all files during the upgrade? The system surely has stable power.
Jan
I don't know. Can you run the following?
# pkg check -da
# pkg check -sa
Do you have any plugins installed or self-built ports?
Thanks,
Franco
Hi Franco,
pkg check -da
shows missing dependencies
hostapd is missing a required shared library: libssl.so.9
hostapd is missing a required shared library: libcrypto.so.9
pkg: No packages available to install matching 'openssl102' have been found in the repositories
pkg check -sa
shows heaps of checksum mismatches.
I have a few plugins from the OPNsense repositories. No self-built ports or customisation; everything is out of the standard box. After:
pkg update
pkg upgrade
I got OPNsense back up & running.
Then I ran the update from the webinterface once again and am now running 20.1.5. As far as I can tell the configuration of the system has been retained successfully.
Not sure what went on here though...!
Thanks for your help!
regards,
Jan
Hi Jan,
Okay, glad you could fix it.
Don't know either. Packages are signed and verified, which means during install the disk "forgot" to store the new files / dependencies.
I've seen such effects on virtual installs sometimes where the file system layer pretends to store things but after reboot the old files are back (Hyper-V in particular).
Cheers,
Franco