The firewall encountered an error after upgrading to 23.01

JonathanLee

@yaw I have removed and reinstalled as soon as you save the configuration it fails

JonathanLee

I have the same issue with I save Squid config changes. Thanks for opening the redmine ticket. Everything works until I save the proxy config

PHP_errors.txt

JonathanLee

@yaw should I open a pfSense ticket and reinstall from a USB or will this result in the same issue?

(Image: error when you try to save the Squid config changes)

yaw

@jonathanlee I don't think reinstalling from USB will help. I think the developers are going to need to fix this and update the squid and squidguard packages. You can try opening a ticket if you have a support agreement.

JonathanLee

@yaw I opened a TAC ticket with Netgate. I cannot do a reinstall right now, my family will be mad at me.

https://forum.netgate.com/topic/178036/23-01-squid-issue/3?_=1676773067228

I have a thread open also same issue.

TAC had me perform a BareMetal install via USB drive and reinstall the configuration after, and it cleared up a lot of my issues. The in-place upgrade did not fully install from what their team said last night, it never fully completed.

With the fresh install it is working fine for now.

hugoeyng

@jonathanlee When I open the webGUI a warning message, about the crash error, is showed to me.

And if I try to reinstall the Squid Proxy Filter the crash error message is showed in the "installation progress box"

JonathanLee

@hugoeyng do you have the error? I had to resave reverse proxy because it was blank before the update and save the config as that was missing for me, after update it.

Dobby_

Upgrade from 22.05 (zfs) to 23.01 (zfs)
-- reboot
-- go in console (8) and type pfSense-upgrade
-- reboot again
-- go in console type in pkg update and pkg upgrade
-- reboot again

All failures went away (my settings) only higher cpu, ram and swap usage was there for a while. Perhaps, it could help you out of your situation. I must restart the ClamD, snort and unbound once, but after reboot they were working automatically again.

matyi.szabolcs

@dobby_

It is unnecessary because PHP8.1 is not compatible with the current code.

hugoeyng

@jonathanlee I read about this above and I did it. No success.

hugoeyng

@dobby_ thank you, but did not work for me.

Dobby_

@matyi-szabolcs
There for it is an 23.01 RC release candidate I think

At my upgrade it went one times wrong with two pkg´s
and after rebooting and upgrading over the console with
pfSense-upgrade and a reboot I must even type in the
admin and password by hand, but after pkg upgrade the
two packets were upgraded and rebooting again brought
me no errors again and it was like before showing the console without typing in something by hand.

The only one I got is now this one, but not related to this topic

Crash report begins.  Anonymous machine information:

amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n2xxxxx-6xxx487xxxx: Fri Feb 10 20:30:29 UTC 2023     root@freebsd:/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/obj/amd64/VDZvZksF/var/jenkins/workspace/pfSense-Plus-snapshots-23_01-main/sources/FreeBS

Crash report details:

PHP Errors:
[16-Feb-2023 21:45:51 Europe/Berlin] PHP Fatal error:  Uncaught TypeError: Unsupported operand types: string / float in /usr/local/www/widgets/widgets/ntp_status.widget.php:90
Stack trace:
#0 {main}
  thrown in /usr/local/www/widgets/widgets/ntp_status.widget.php on line 90



No FreeBSD crash data found.

matyi.szabolcs

@dobby_

I wrote earlier that the code is not compatible with PHP 8.1.

This is causing all the errors at the moment.
Tt's not just SquidGuard that has a problem.

A major code update is needed here.

hugoeyng

@matyi-szabolcs Did you read something about if /when that "major code update" will be avaliable ?

matyi.szabolcs

@hugoeyng

I don't know, I'm not a developer.

hugoeyng

@dobby_ I ran pfSense-upgrade -y and the error has gone

matyi.szabolcs

@hugoeyng said in The firewall encountered an error after upgrading to 23.01:

pfSense-upgrade -y

For me, "pfSense-upgrade -y" did not solve anything.
The error persists.

hugoeyng

@matyi-szabolcs I was wrong: "pfSense-upgrade -y" did not fix the problem.

hugoeyng

@jonathanlee said in The firewall encountered an error after upgrading to 23.01:

@hugoeyng do you have the error? I had to resave reverse proxy because it was blank before the update and save the config as that was missing for me, after update it.

I did it more than one time and did not work.

Memory usage is high

JonathanLee

@hugoeyng Did this ever calm down once ZFS syncs?