Project

General

Profile

Actions

Bug #14518

closed

pfSense CrashLog on 2.7.0RC Upgrade

Added by Matthew Drury over 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.0
Affected Architecture:

Description

I received this crash log upon upgrade to 2.7.0RC from 2.6.0. Everything seems to be running fine so far despite this log appearing. The only other oddity was that the packages were not upgraded during the main install.

But I wanted to give the report to the devs.


Files

PHP_errors.log (87.9 KB) PHP_errors.log Crash Log Matthew Drury, 06/28/2023 12:50 PM
Actions #1

Updated by Jim Pingle over 1 year ago

  • Status changed from New to Feedback

The module errors are known/expected during any upgrade where the PHP version changes. We're working on trying to improve that for the future already.

The other PHP error is less clear but may be related.

Do any errors come back if you reboot?

Which packages did you have installed?

Actions #2

Updated by Matthew Drury over 1 year ago

There is no new crash report given upon a reboot.

Packages Installed:
Acme
llpd
nut
Openvpn-client-export
pfBlockerNG
RRD_Summary
Status_Traffic_Totals
suricata
System_Patches
WireGuard

Actions #3

Updated by Jim Pingle over 1 year ago

OK, and did you have to manually upgrade those packages after?

It's possible a problem with one of the old packages (e.g. the 2.6.0 version of a package) didn't uninstall properly which prevented the new version from installing, but without more info and being able to reproduce it, it's hard to say for certain.

If you still have the complete upgrade log (or a console output buffer if it was a serial console) that might help shed some light on things but if the system is working OK and the errors do not come back after a reboot there may not be anything actionable here.

Actions #4

Updated by Matthew Drury over 1 year ago

I did have to update almost all of the packages after the upgrade. I think the acme package and system patches were the only packages that I didn't need to update manually.

I don't have a complete log from this system. But I do have another 2.6 system that I plan to upgrade to the RC soon. If I encounter a similar experience I will report a more complete log if I can.

Actions #5

Updated by Kris Phillips over 1 year ago

Hello Matthew,

Please test with the release of 2.7 and let us know if you're able to reproduce this issue.

Actions #6

Updated by Matthew Drury over 1 year ago

Hello Kris,

I have not been able to recreate the issue since the 1 time it occurred. The 1st machine I upgraded to RC had not uninstalled any packages prior to updating. All other machines upgraded without pkgs installed, and no errors occurred.

It could have been the result of pkgs remaining installed during update or just a one off error caused by some config of the 1st machine.

Actions #7

Updated by Kris Phillips about 1 year ago

This can be closed as the RC is now RELEASE and there doesn't appear to be any more issues.

Actions #8

Updated by Jim Pingle about 1 year ago

  • Status changed from Feedback to Closed
Actions

Also available in: Atom PDF