Update from 2.4.3-p1 on SHUTTLE (Core(TM)2 Quad CPU Q8400) to RC-2.4.4.r.20180917.0758 crash report on startup. A lot of PHP errors.

mrzaz

Update from 2.4.3-p1 on SHUTTLE (Core(TM)2 Quad CPU Q8400) to RC-2.4.4.r.20180917.0758 crash report on startup.
Logged into the GUI i got the following crash:
(RC downloaded via pfsense Update function by enabling RC in settings. "Next Release Candidate (2.4.4-RC))

Crash report begins.  Anonymous machine information:

amd64
11.2-RELEASE-p3
FreeBSD 11.2-RELEASE-p3 #15 e6b497fa0a3(RELENG_2_4_4): Mon Sep 17 08:00:47 EDT 2018     root@buildbot3:/crossbuild/ce-244/obj/amd64/WvDslnYb/crossbuild/ce-244/pfSense/tmp/FreeBSD-src/sys/pfSense

Crash report details:

PHP Errors:
[07-Sep-2018 00:53:48 UTC] PHP Warning:  Failed loading Zend extension 'opcache.so' (tried: /usr/local/lib/php/20131226/opcache.so (/usr/local/lib/php/20131226/opcache.so: Undefined symbol "zend_opcode_handlers"), /usr/local/lib/php/20131226/opcache.so.so (Cannot open "/usr/local/lib/php/20131226/opcache.so.so")) in Unknown on line 0
[07-Sep-2018 00:53:48 UTC] PHP Warning:  PHP Startup: Unable to load dynamic library 'session.so' (tried: /usr/local/lib/php/20131226/session.so (/usr/local/lib/php/20131226/session.so: Undefined symbol "zval_used_for_init"), /usr/local/lib/php/20131226/session.so.so (Cannot open "/usr/local/lib/php/20131226/session.so.so")) in Unknown on line 0
[07-Sep-2018 00:53:48 UTC] PHP Warning:  PHP Startup: bcmath: Unable to initialize module
Module compiled with module API=20131226
PHP    compiled with module API=20170718
These options need to match
 in Unknown on line 0
[07-Sep-2018 00:53:48 UTC] PHP Warning:  PHP Startup: bz2: Unable to initialize module
Module compiled with module API=20131226
PHP    compiled with module API=20170718
These options need to match
 in Unknown on line 0
[07-Sep-2018 00:53:48 UTC] PHP Warning:  PHP Startup: ctype: Unable to initialize module
Module compiled with module API=20131226
PHP    compiled with module API=20170718
These options need to match
 in Unknown on line 0
.
.
.
See attached logfile for ALL...

0_1537224813029_Crash-pfsense_RC244_20180918.txt
0_1537224904078_Crash-pfsense_RC244_20180918.zip
Best regards
Dan Lundqvist
Stockholm, Sweden

gsiemon

I have pretty much the same list of errors here on a VM running on vSphere 6.5 when upgrading from 2.4.3-p1 to 2.4.4RC. Fortunately, I had a snapshot and rolled back. If it matters, I upgraded using option 13 on the console.

0_1537225272046_PHP_errors.txt

stephenw10

What packages did you have installed during the upgrade?

Steve

gsiemon

@stephenw10 I had the following installed:

Acme
AutoConfigBackup
Avahai
freeradius3
LADVD
nmap
Open-VM-Tools
openvpn-client-export
phBlockerNG-devel
Service_Watchdog
Shellcmd
snort

All versions current on 2.4.3-p1.

stephenw10

I just spent a while struggling with what looks like very similar logs.
I found Auto config backup to be the issue. After removing that it upgraded OK.
That package should be removed by the update process anyway as it is replaced by the code in the base in 2.4.4. It's not yet clear why that didn't happen in my case. I have ACB installed on just about every box I have and only one hit this.
If you can test that I'd be very interested.

Steve

gsiemon

@stephenw10 I removed the ACB module and tried again but I still get a long list of errors

0_1537234405398_PHP_errors2.txt

I also had no connectivity to the internet but couldn't figure out why and didn't have time to do a lot of troubleshooting. I've rolled back again in the meantime.

gzorn

@stephenw10

I encountered a similar crash report (though the system seems to be working otherwise). I didn't have ACB installed.

stephenw10

In my case I think I was actually hitting this: https://redmine.pfsense.org/issues/8911
That should be fixed in the next RC image.

Steve

gsiemon

@stephenw10 Thanks. I didn't start with a fresh install and import the config, it was an upgrade of an existing installation. Perhaps there is another way to generate the same crash report?

I did notice that the console display from the VM showed a bunch of errors when running the upgrade. I'll try to get a video of it and figure out what was going on.