Getting crash reports after updating to 2.4.4

[jimp]

Those look like the typical errors you see during an upgrade. If you delete that report, do the same error messages come back?

[nesense]

@jimp they come back if I reboot or if WAN goes down and up again.

[jimp]

The exact same set of errors?

If so, it looks like maybe the upgrade did not complete. It's complaining about PHP module versions not matching, which I've only ever seen happen in the middle of an upgrade, not before or after repeatedly.

[nesense]

Yes, same errors everytime, everything seems to be functioning normally though, but should I reinstall freshly from 2.4.4 to be safe?

[jimp]

Before doing that, try running pfSense-upgrade -d from an ssh or console shell prompt to see if it attempts to correct the issues.

[nesense]

Here's the output of pfSense-upgrade -d:

>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
Fetching meta.txz: . done
Fetching packagesite.txz: .......... done
Processing entries: .......... done
pfSense repository update completed. 499 packages processed.
All repositories are up to date.
>>> Upgrading pfSense-upgrade...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be UPGRADED:
        pfSense-upgrade: 0.52 -> 0.53 [pfSense]

Number of packages to be upgraded: 1

13 KiB to be downloaded.
[1/1] Fetching pfSense-upgrade-0.53.txz: .. done
Checking integrity... done (0 conflicting)
[1/1] Upgrading pfSense-upgrade from 0.52 to 0.53...
[1/1] Extracting pfSense-upgrade-0.53: ..... done
>>> Setting vital flag on lang/php72...
>>> Updating repositories metadata...
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Your packages are up to date

I rebooted after and got the another exact crash report.

[jimp]

Nothing showing there. What is the output of pkg info?

[jwt]

What does php -v output?

% php -v
PHP 7.2.10 (cli) (built: Sep 14 2018 11:38:12) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.2.10, Copyright (c) 1999-2018, by Zend Technologies]

[nesense]

I already reinstalled.

[wdup]

Experiencing the same issue - had pfBlockerNG-devel installed prior to upgrade from 2.4.3-p1 to 2.4.4. Didn't appear to have any problems during upgrade. Have since uninstalled pfBlockerNG-devel, issue remains.

[TheNarc]

Same issue here, exact same set of error messages. Output from php -v:

PHP 7.2.10 (cli) (built: Sep 14 2018 11:32:18) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.10, Copyright (c) 1999-2018, by Zend Technologies

I too had pfBlockerNG-devel installed prior to the upgrade. I haven't tried uninstalling it, but I have noticed that the pfb_filter service isn't running, and if I attempt to start it manually, I can provoke the crash report.

[nesense]

I had pfblockerng-devel installed before but I uninstalled it and reinstalled the stable package before updating.

[REM]

I have same issue0_1537985459724_pfsence.txt

[jimp]

@rem said in Getting crash reports after updating to 2.4.4:

I have same issue0_1537985459724_pfsence.txt

Your upgrade did not complete. It's still referencing old PHP 5.6 items. If you have WAN connectivity, go to an ssh or console shell and run pfSense-upgrade again.

[REM]

Thank you, this message after first reboot, if in console i have:
Updating pfSense-core repository catalogue...
pfSense-core repository is up to date.
Updating pfSense repository catalogue...
pfSense repository is up to date.
All repositories are up to date.
Your packages are up to date

all ok, safety use?

[jimp]

If you still receive those errors after a reboot, then something must not be OK. If they went away, then it's fine.

If you still have problems, go through some of the suggestions here: https://www.netgate.com/docs/pfsense/install/upgrade-troubleshooting.html

[Ramosel]

@wdupreez said in Getting crash reports after updating to 2.4.4:

Experiencing the same issue - had pfBlockerNG-devel installed prior to upgrade from 2.4.3-p1 to 2.4.4. Didn't appear to have any problems during upgrade. Have since uninstalled pfBlockerNG-devel, issue remains.

Seeing the EXACT same thing as you. Working with Anthony but it seems to go deeper than pfBNG.

[Ramosel]

@thenarc said in Getting crash reports after updating to 2.4.4:

Same issue here, exact same set of error messages. Output from php -v:

PHP 7.2.10 (cli) (built: Sep 14 2018 11:32:18) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.2.0, Copyright (c) 1998-2018 Zend Technologies
    with Zend OPcache v7.2.10, Copyright (c) 1999-2018, by Zend Technologies

I too had pfBlockerNG-devel installed prior to the upgrade. I haven't tried uninstalling it, but I have noticed that the pfb_filter service isn't running, and if I attempt to start it manually, I can provoke the crash report.

Same issue here.

[Ramosel]

@jimp said in Getting crash reports after updating to 2.4.4:

@rem said in Getting crash reports after updating to 2.4.4:

I have same issue0_1537985459724_pfsence.txt

Your upgrade did not complete. It's still referencing old PHP 5.6 items. If you have WAN connectivity, go to an ssh or console shell and run pfSense-upgrade again.

Jim,
I too am seeing the same errors. I uninstalled all packages rebooted, then did the "pkg-static clean -ay; pkg-static install -fy pkg pfSense-repo pfSense-upgrade" from the link you sent. System came up clean reinstalled packages as well as the pfBlockerNG devel from Anthony and as soon as I try to start pfb_filter service it provokes a crash report full of PHP errors.

[jimp]

Does it work as long as you don't install pfBlockerNG? There were a couple changes just merged for it, but I'm not sure it would help what you are seeing. If it works OK until you install pfBlocker, that's probably a topic for a different thread.