Project

General

Profile

Bug #8915

After updating to 2.4.4-rc an empty crash report is shown

Added by Steve Wheeler 3 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Upgrade
Target version:
Start date:
09/18/2018
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.4.4
Affected Architecture:
All

Description

In some cases a crash report is presented at first login after upgrading but the report contains no crash data and no PHP errors.

I have seen this twice on an SG-4860 coming from 2.4.3p1.

Also reports on an SG-3100:
https://forum.netgate.com/topic/135615/update-from-2-4-3-p1-on-sg-3100-to-rc-2-4-4-r-20180917-0837-crash-report-on-startup

Associated revisions

Revision 6e150fc0 (diff)
Added by Jim Pingle 2 months ago

Unify and improve crash report checking. Fixes #8915

Revision e4125720 (diff)
Added by Jim Pingle 2 months ago

Unify and improve crash report checking. Fixes #8915

(cherry picked from commit 6e150fc0d022d231c7dc243ba68f4784f58973d5)

History

#1 Updated by Marcel Beerli 3 months ago

Just did the upgrade from 2.4.3-1 to 2.4.4 on a PC Engines APU2 and had this issue as well. Not an empty crash report, it had about 4 pages.

#2 Updated by Jim Pingle 3 months ago

If it wasn't empty, then it was not this issue. This issue is specifically about an empty crash report.

#3 Updated by Steve Beaver 2 months ago

  • Target version changed from 2.4.4-GS to 2.4.4_1

#4 Updated by Jim Pingle 2 months ago

  • Status changed from New to In Progress
  • Affected Version set to 2.4.4

#5 Updated by Jim Pingle 2 months ago

I just pushed a change that should hopefully take care of this, under the assumption that some mismatch in how index.php checks for reports was different than how crash_reporter.php checks.

This should fix any case we can reasonably correct.

The only other way I could see this condition happening is if there was a report when the dashboard loaded, but by the time the user navigated to crash_reporter.php it was removed, for example by pfSense-upgrade finishing up.

#6 Updated by Jim Pingle 2 months ago

  • Status changed from In Progress to Feedback
  • % Done changed from 0 to 100

#7 Updated by Danilo Zrenjanin 2 months ago

Tried to replicate getting PHP crush report on SG-3100:

from version 2.4.3_p1 to 2.4.4 - RELEASE / no crush report at first login
from version 2.4.3_p1 to 2.4.5-DEVELOPMENT / no crush report at first login.

note
I noticed in both cases while booting after upgrade unusual logs:

 on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Warning: Invalid argument supplied for foreach() in Command.php on line 249
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstall in Role.php on line 173
Notice: Undefined index: honorsbaseinstal

ot open "/usr/local/lib/php/20131226/curl.so.so")) in Unknown on line 0
Warning: PHP Startup: Unable to load dynamic library 'dom.so' (tried: /usr/local/lib/php/20131226/dom.so (Cannot open "/usr/local/lib/php/20131226/dom.so"), /usr/local/lib/php/20131226/dom.so.so (Cannot open "/usr/local/lib/php/20131226/dom.so.so")) in Unknown on line 0
Warning: PHP Startup: Unable to load dynamic library 'hash.so' (tried: /usr/local/lib/php

These options need to match
 in Unknown on line 0
Warning: PHP Startup: Unable to load dynamic library 'pfSense.so' (tried: /usr/local/lib/php/20131226/pfSense.so (/usr/local/lib/php/20131226/pfSense.so: Undefined symbol "zval_used_for_init"), /usr/local/lib/php/20131226/pfSense.so.so (Cannot open "/usr/local/lib/php/20131226/pfSense.so.so")) in Unknown on line 0
Warning: PHP Startup: posix: 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
Warning: PHP Startup: readline: 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
Warning: PHP Startup: shmop: Unable to initialize module
Module compiled with module API=20131226
PHP    compiled with module API=201

After boot process all works as expected.

#8 Updated by Jim Pingle 2 months ago

  • Status changed from Feedback to Resolved

Those logs are expected, they are from PEAR and various other parts of PHP being upgraded. As long as the empty report isn't shown this is OK.

Also available in: Atom PDF