23.01 notices.inc PHP error

daplumber

I am getting the following crash report on an irregular occasional basis:

===
Crash report begins. Anonymous machine information:

amd64
14.0-CURRENT
FreeBSD 14.0-CURRENT #0 plus-RELENG_23_01-n256037-6e914874a5e: 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:
[02-Mar-2023 22:00:00 CST6CDT] PHP Fatal error: Uncaught TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given in /etc/inc/config.lib.inc:172
Stack trace:
#0 /etc/inc/config.lib.inc(172): fwrite(false, 'a:44:{s:7:"vers...')
#1 /etc/inc/config.lib.inc(147): generate_config_cache(Array)
#2 /etc/inc/config.inc(141): parse_config()
#3 /etc/inc/gwlb.inc(25): require_once('/etc/inc/config...')
#4 /etc/inc/functions.inc(35): require_once('/etc/inc/gwlb.i...')
#5 /etc/inc/notices.inc(26): require_once('/etc/inc/functi...')
#6 /usr/local/arpwatch/sendmail_proxy.php(5): require_once('/etc/inc/notice...')
#7 {main}
thrown in /etc/inc/config.lib.inc on line 172
[02-Mar-2023 22:00:00 CST6CDT] PHP Fatal error: Uncaught ValueError: Path cannot be empty in /etc/inc/notices.inc:101
Stack trace:
#0 /etc/inc/notices.inc(101): fopen('', 'w')
#1 /etc/inc/config.lib.inc(1162): file_notice('phperror', 'PHP ERROR: Type...', 'PHP errors')
#2 [internal function]: pfSense_clear_globals()
#3 {main}
thrown in /etc/inc/notices.inc on line 101

No FreeBSD crash data found.

===

PHP error log attached, but it doesn't contain anything else useful.

Any idea what's going on here, and what I can do to fix it?
My hardware is a Dell Desktop with Intel i5-6500 @ 3.2GHz, 8GB of RAM, a 1TB SSD, GELI ZFS boot/root, Intel X520 and Intel 1GB NICs, two WAN connections to two different ISPs.

I recently had to turn off the watchdog on the pfBlockerNG DNSbl as it kept crashing too.

230306_PHP_errors.log.txt

jimp

Unfortunately errors in that spot are likely from a problem writing to the disk. It could be a filesystem issue, the disk may be failing, the controller might have stopped responding, etc. It's really impossible to know for sure -- all that can be told from that is that the attempts to write to the disk failed in those specific locations.

daplumber

@jimp OK, so should I manually fsck the disk (SSD) or what?

dem

@daplumber You might want to look at the S.M.A.R.T. and ZFS dashboard widgets:

Disk Screenshot.png

daplumber

@dem I use both widgets and there was nothing in either.

So after a bunch of zpool scrub zroot, and having to burn a CURRENT-14 memstick because I forgot to update the boot code after doing a zpool upgrade, and some more scrubs, sigh...

All seems copacetic once more. ¯\_(ツ)_/¯

stephenw10

We did re-open the bug for this anyway since a number of people are hitting it:
https://redmine.pfsense.org/issues/14061

Steve