The firewall encountered an error after upgrading to 23.01

[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?

[hugoeyng]

@jonathanlee ZFS?

[JonathanLee]

@hugoeyng the release information states that the ZFS file system takes alot of memory on start up and will normalize after some time once the software is installed.

[hugoeyng]

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

@hugoeyng the release information states that the ZFS file system takes alot of memory on start up and will normalize after some time once the software is installed.

Yes. It is true. After a few minutes the use of memorry is normalized.

[Dobby_]

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

@hugoeyng the release information states that the ZFS file system takes alot of memory on start up and will normalize after some time once the software is installed.

This is what my APU do after a fresh (re)boot!
After while all is fine again, but I was applying a patch!

Did this ever calm down once ZFS syncs?

Can not really be based on that point in my eyes, I was starting with;

• pfSenseCE 2.6 (zfs)
  No problems at all
• upgrading to pfS+ 22.01 (zfs)
  No problems at all
• upgrading to pfS+ 22.05 (zfs)
  High cpu usage, after pfBlocker-ng patch applied
  all was fine again
• and once more upgrade to pfS+ 23.01 (zfs)
  High CPU and RAM usage and on top the Swap was running out of space too!!! After applying a patch all is fine

@hugoeyng
Actual picture to show again: CPU low, Swap low and
RAM low! I was also not seeing this message again.
Swap pager: running out of space

[JonathanLee]

@hugoeyng Mine will be at upper 90& for a while and after just drop down to 20-40%

[hugoeyng]

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

@hugoeyng Mine will be at upper 90& for a while and after just drop down to 20-40%

It is similar here. 22%
In the past I faced some question about swap. When rebooted, swap started up using 3% and after growing until crash.

[hugoeyng]

@jonathanlee I changed squidguard.inc as you can see in the following pic. The error message has gone, but SquidGuard does not start. Of course, I only test for the error and skip it, and I don´t know excatly what the consequences. :)

[JonathanLee]

@hugoeyng it could be that it won't start because the array holding the urls can not be iterated due to that line being removed. Can you find where that specific array is instantiated at? Also does this array have the correct elements in it? I see it they have it instantiated sgxml as an array in that function at the top. Come to think of it, what is that array pfxml used for is that the full config of pfsense? You have to convert it too or reseralize it? Keep in mind I am still a computer science student. PfSense farsantes me. It's amazing. I really want to learn how to debug the software like the ide jGRASP's debug. I can do programming in Java and Python. Again when you are coding for specific firewall hardware how can you debug it without the hardware? Do you use a virtual machine. I really need to learn that. We learned how to code but not with specific environments.

[JonathanLee]

@hugoeyng can you do a try catch instead?

[hugoeyng]

@jonathanlee please write how would you do it

[JonathanLee]

@hugoeyng

I know in Java It would be something like this photo. Again it needs the C programming version of it so you can read the specific error. This photo I have a array that is out of bounds when it prints that element, notice the error is caught. You can do more than print the error you can redirect it to other code also, so if something was missing in that config it could flag it if needed would need more code.