Random crash report in notices.inc and wg.inc

whinis

Proxmox

GPz1100

@stephenw10 If some part of the config (config.xml) was causing this issue. How would one even begin to troubleshoot that?

Restore portions of it to a new install until crash is triggered or is there a better way?

stephenw10

Nothing should ever result in the config file being inaccessible. It looks like some filesystem or drive issue though because in addition to not being able to open the config file the PHP error is being unable to open the notices file to post an alert for it.

whinis

Just to be proactive, the SSD its on is at 30% wearout, I moved it to another ssd in the VM and still same issue. I checked the logs on the VM host (proxmox) and the sys logs of pfsense and no obvious errors in either.

whinis

And here is the error that occasionally occurs that causes the config to be reloaded

May  5 21:12:00 pfsense php_wg[93764]: /usr/local/pkg/wireguard/includes/wg_service.inc: XML error: no pfsense or pfsense object found!
May  5 21:12:00 pfsense php_wg[93764]: 
May  5 21:12:00 pfsense php_wg[93764]: /usr/local/pkg/wireguard/includes/wg_service.inc: pfSense is restoring the configuration /cf/conf/backup/config-1746449192.xml
May  5 21:12:00 pfsense php_wg[93764]: /usr/local/pkg/wireguard/includes/wg_service.inc: New alert found: pfSense is restoring the configuration /cf/conf/backup/config-1746449192.xml
May  5 21:12:00 pfsense php_wg[93764]: /usr/local/pkg/wireguard/includes/wg_service.inc: PHP ERROR: Type: 1, File: /usr/local/pkg/wireguard/includes/wg_globals.inc, Line: 197, Message: Uncaught Error: Cannot use a scalar value as an array in /usr/local/pkg/wireguard/includes/wg_globals.inc:197
May  5 21:12:00 pfsense php_wg[93764]: Stack trace:
May  5 21:12:00 pfsense php_wg[93764]: #0 /usr/local/pkg/wireguard/includes/wg_globals.inc(238): wg_init_config_arr(-1, Array)
May  5 21:12:00 pfsense php_wg[93764]: #1 /usr/local/pkg/wireguard/includes/wg.inc(345): wg_globals()
May  5 21:12:00 pfsense php_wg[93764]: #2 /usr/local/pkg/wireguard/includes/wg_service.inc(360): wg_resolve_endpoints()
May  5 21:12:00 pfsense php_wg[93764]: #3 /usr/local/pkg/wireguard/includes/wg_service.inc(294): wg_service_daemon()
May  5 21:12:00 pfsense php_wg[93764]: #4 /usr/local/pkg/wireguard/includes/wg_service.inc(60): wg_service_cli_start(false)
May  5 21:12:00 pfsense php_wg[93764]: #5 {main}
May  5 21:12:00 pfsense php_wg[93764]:   thrown
May  5 21:12:00 pfsense php_wg[93764]: /usr/local/pkg/wireguard/includes/wg_service.inc: New alert found: PHP ERROR: Type: 1, File: /usr/local/pkg/wireguard/includes/wg_globals.inc, Line: 197, Message: Uncaught Error: Cannot use a scalar value as an array in /usr/local/pkg/wireguard/includes/wg_globals.inc:197
May  5 21:12:00 pfsense php_wg[93764]: Stack trace:
May  5 21:12:00 pfsense php_wg[93764]: #0 /usr/local/pkg/wireguard/includes/wg_globals.inc(238): wg_init_config_arr(-1, Array)
May  5 21:12:00 pfsense php_wg[93764]: #1 /usr/local/pkg/wireguard/includes/wg.inc(345): wg_globals()
May  5 21:12:00 pfsense php_wg[93764]: #2 /usr/local/pkg/wireguard/includes/wg_service.inc(360): wg_resolve_endpoints()
May  5 21:12:00 pfsense php_wg[93764]: #3 /usr/local/pkg/wireguard/includes/wg_service.inc(294): wg_service_daemon()
May  5 21:12:00 pfsense php_wg[93764]: #4 /usr/local/pkg/wireguard/includes/wg_service.inc(60): wg_service_cli_start(false)
May  5 21:12:00 pfsense php_wg[93764]: #5 {main}
May  5 21:12:00 pfsense php_wg[93764]:   thrown

stephenw10

Hmm, you've only seen this in 2.7.2?

whinis

As far as I know. This config I think used to be 23. Something and then I rebuilt it once I stopped using commercial for my home.

stephenw10

Are you able to test 2.8-Beta?

whinis

I can if I have a guide of how to update to it

stephenw10

You just have to select it in the repo branch in System > Update.

whinis

Cool, ill try this tonight after the work day ends. Joy of working from home.

whinis

So, we are now a few days into the 2.8-Beta version and no more crashes have happened. Hopefully this is somewhat helpful for you but unsure if it is.

stephenw10

Well if anything changed there it's probably something low level that the OS updates could have addressed.