Upgrade to 23.01 - crash report

stephenw10

Have you rebooted since the upgrade?

Do those errors only appear after rebooting?

If not what triggers the errors?

Steve

madas

@stephenw10

No - not on a reboot. I have rebooted it 2-3 times since the upgrade and it doesn't occur on reboot.

This happened at 2am so I have no clue what triggered it

Brad Bishop

I'm getting similar errors:

PHP ERROR: Type: 1, File: /usr/local/www/xmlrpc.php(147) : eval()'d code, Line: 14, Message: Uncaught TypeError: Cannot access offset of type string on string in /usr/local/www/xmlrpc.php(147) : eval()'d code:14
Stack trace:
#0 /usr/local/www/xmlrpc.php(147): eval()
#1 /usr/local/share/pear/XML/RPC2/Server/CallHandler/Instance.php(141): pfsense_xmlrpc_server->exec_php('\nini_set('displ...')
#2 /usr/local/share/pear/XML/RPC2/Backend/Php/Server.php(135): XML_RPC2_Server_Callhandler_Instance->__call('pfsense.exec_ph...', Array)
#3 /usr/local/share/pear/XML/RPC2/Backend/Php/Server.php(99): XML_RPC2_Backend_Php_Server->getResponse()
#4 /usr/local/www/xmlrpc.php(988): XML_RPC2_Backend_Php_Server->handleCall()
#5 {main}
thrown @ 2023-02-28 15:23:50

I have rebooted. This seems to be happening throughout the day.

madas

@stephenw10

Not sure if its related but i have up/down notifications on my gateways and they are now getting stuck in a loop and i get the notifications over and over again.

Notifications in this message: 3

10:28:59 MONITOR: VPN_TOR_VPNV4 is available now, adding to routing group VPN_NORMAL
9.9.9.9|1x|VPN_TOR_VPNV4|98.764ms|3.098ms|10%|online|none
10:29:02 DynDNS updated IP Address on VPN_TOR (ovpnc9) to xx
10:34:40 MONITOR: VPN_TOR_VPNV4 has packet loss, omitting from routing group VPN_NORMAL
9.9.9.9|1x|VPN_TOR_VPNV4|99.52ms|3.805ms|57%|down|highloss

Its not really down. I received 1000 of these in the last 5 minutes.

stephenw10

@brad-bishop said in Upgrade to 23.01 - crash report:

I'm getting similar errors

That's a different error, you should open a new thread.

Though IIRC there is already a patch for it. See: https://redmine.pfsense.org/issues/14000

Try the patch shown here: https://redmine.pfsense.org/issues/13944

stephenw10

@madas said in Upgrade to 23.01 - crash report:

This happened at 2am so I have no clue what triggered it

Presumably something that triggered a notification. What's in the logs at that time?

Steve

madas

@stephenw10

Sorry - i think i'm confusing issues.

I see your last post about the home assistant integration - i think that was for brad only (i'm not using HA).

I don't see any fix for my PHP issue?

Separately - i'm getting this notification loop and I actually managed to catch pfsense stuck in a loop bringing the gateway on the VPN up and down over and over again. the VPN is an openvpn client and I actually shutdown openvpn completely and PFSense was still stuck in a loop bringing it up/down. Maybe I should open a new thread for this one?

stephenw10

Yes, that link to the fix was for Brad. He's seeing a different bug entirely.

Yes you should open a new thread for a looping VPN connection. That appears to be triggering the notifications but it's actually notifying correctly for the incorrect connection attempts.

Do you still see that error if you don't have email notifications enabled in nut?
I note OP here was seeing it without nut.

madas

@stephenw10

I just disabled NUT as I did see that losing connection to the UPS over time. So maybe thats it?

I can monitor to see if it still occurs now NUT is disabled

NUT worked fine with the UPS prior to 23.01

stephenw10

Yes, it should still work. There may be a bug you've hit. Let's see what that changes.

madas

@stephenw10 do you want me to shutdown NUT completely or just disable the email notification?

stephenw10

Just disable the notification.

Brad Bishop

@stephenw10

Sorry I didn't start a new thread. This worked. My fault / my side.

I appreciate the help.

Have a great day!

madas

@stephenw10

No crash notification on the firewall but i noticed that NUT is complaining that it lost connectivity to the UPS again.

stephenw10

Like intermittent? Is it USB connected? Probably better to start a new thread about that. Unless it;s something already being discussed in packages.

madas

@stephenw10 it is connected to USB (the same as it has always been). No issues on previous versions

stephenw10

Ok, start a new thread for that then it seems unrelated to the notifications issue.