Crash report after upgrade to 23.05
-
About 90 minutes after upgrading to 23.05 GUI showed there had been a crash.
PHP error log[30-May-2023 13:04:35 Europe/London] 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:43:{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/pkg/nut/nut_email.php(24): require_once('/etc/inc/notice...')
#7 {main}
thrown in /etc/inc/config.lib.inc on line 172
[30-May-2023 13:04:35 Europe/London] 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 101I believe I may just have restarted NUT which had lost contact with UPS, from General system log:
May 30 13:04:35 php-cgi 37927 nut_email.php: PHP ERROR: Type: 1, File: /etc/inc/config.lib.inc, Line: 172, Message: Uncaught TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given in /etc/inc/config.lib.inc:172
Can I provide any additional information?
-
Does the error return if you just remove the warning? After reboot perhaps?
-
After downloading PHP_errors.log I removed the warning and have not had any further problems.
Yesterday without problems I:
-
Restarted nut twice
-
Downloaded and configured udpbroadcastrelay
-
Removed Avahi
Today without problems I:
-
Rebooted
-
Restarted nut
Is there anything else I can try or provide?
-
-
If it does not return it was likely something that happened during the upgrade. Though you said it only alerted 90mins after that which is unexpected.
It might have been a package install that became stuck and was hence still on the old php code. Rebooting allowed it to complete.
If you see it again we can certainly dig into it.Steve
-
@stephenw10 Today I upgraded snort to latest version immediately got same crash. I have cleared the warning and the system is running ok.
/////////
[29-Jun-2023 09:09:22 Europe/London] 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/pkg/nut/nut_email.php(24): require_once('/etc/inc/notice...')
#7 {main}
thrown in /etc/inc/config.lib.inc on line 172
[29-Jun-2023 09:09:22 Europe/London] 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 -
It's this: https://redmine.pfsense.org/issues/14061
But that should be fixed in 23.05.
Are you able to replicate this, by reinstalling Snort for example?
Steve
-
@stephenw10 Just did snort reinstall via package manager without problem. Anything else I can try?
-
I added your data point here: https://redmine.pfsense.org/issues/14432
Since it's in NUT you might try reinstalling that.
This doesn't appear to be an error affecting functionality beyond the notice itself.
-
@stephenw10 Just did nut reinstall via package manager without problem. Anything else I can try?
-
Not sure at this point. We'll update that ticket as we know more.