Project

General

Profile

Actions
Copy link

Bug #2214

closed

PHP core dumps on RRD upgrade

Added by Seth Mos almost 13 years ago. Updated almost 13 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Configuration Upgrade
Target version:
2.1
Start date:
02/20/2012
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:

Description

With the arrival of PHP 5.3.10 on FreeBSD 8.3 the upgrade code core dumps PHP leaving the box dead in the water.

Files

Download all files
php core dump 5.3.10 freebsd 8.3.png (29.4 KB) php core dump 5.3.10 freebsd 8.3.png Seth Mos, 02/20/2012 05:34 AM
php-core.zip (4.6 MB) php-core.zip Seth Mos, 03/13/2012 09:15 AM
php-truss.zip (8.04 KB) php-truss.zip Seth Mos, 03/13/2012 09:15 AM
testscript.txt (5.1 KB) testscript.txt Seth Mos, 03/13/2012 09:21 AM
wan-traffic.rrd.old.zip (73.7 KB) wan-traffic.rrd.old.zip Seth Mos, 03/13/2012 09:21 AM
php-gdb-full.txt (12.6 KB) php-gdb-full.txt Warren Baker, 03/15/2012 08:54 AM
Actions
Copy link
 #1

Updated by Seth Mos almost 13 years ago

  • Category set to Configuration Upgrade
  • Target version set to 8
  • Affected Version set to 2.1-IPv6
Actions
Copy link
 #2

Updated by Chris Buechler almost 13 years ago

  • Target version changed from 8 to 2.1
  • Affected Version changed from 2.1-IPv6 to 2.1

not IPv6-related. 2.1-IPv6 is a tag used for one of the reports on here to list all IPv6-related items, any general 2.1 things please just put as 2.1.

Actions
Copy link
 #3

Updated by Seth Mos almost 13 years ago

Actions
Copy link
 #4

Updated by Seth Mos almost 13 years ago

Appears to be related to either suhosin or our builds, they want a backtrace.

Tried to make a image with a debug php but it failed and now I can't make normal ones either.

Actions
Copy link
 #5

Updated by Rob Logan almost 13 years ago

I saw this as well, but only after the reboot from transferring a config.xml (with red info) and no vlan tagged interfaces were made, so it might be related to rrd import from devices that don't exist. the workaround is to not use an old config.xml. I have a core, but no gdb (currently) so no bt.

Actions
Copy link
 #6

Updated by Rob Logan almost 13 years ago

(with `sed s/red/rrd//` info)

Actions
Copy link
 #7

Updated by Seth Mos almost 13 years ago

  • Status changed from New to Needs Patch

Disabled the Suhosin extension which resolves the crash on RRD upgrade, needs a newer patch, disabled the existing extension in rc.php_ini_setup

Actions
Copy link
 #8

Updated by Seth Mos almost 13 years ago

  • Status changed from Needs Patch to New
Actions
Copy link
 #9

Updated by Seth Mos almost 13 years ago

Suhosin author can not replicate issue, it's ours again, we need a backtrace for him

Actions
Copy link
 #10

Updated by Seth Mos almost 13 years ago

Made a core file and I have the truss output

Actions
Copy link
 #11

Updated by Seth Mos almost 13 years ago

Adding the test script and data file

Actions
Copy link
 #12

Updated by Seth Mos almost 13 years ago

This is the backtrace without debugging symbols. Probably not useful.

#0 0x081ee4f5 in zend_hash_exists ()
[New Thread 288dd140 (LWP 100414/initial thread)]
(gdb) bt
#0 0x081ee4f5 in zend_hash_exists ()
#1 0x291b1be8 in zif_suhosin_extract () from /usr/local/lib/php/20090626/suhosin.so
#2 0x08204582 in execute_internal ()
#3 0x291aeb77 in suhosin_execute_internal () from /usr/local/lib/php/20090626/suhosin.so
#4 0x08208e31 in execute ()
#5 0x08208649 in execute ()
#6 0x291af033 in suhosin_execute_ex () from /usr/local/lib/php/20090626/suhosin.so
#7 0x08208b24 in execute ()
#8 0x08208649 in execute ()
#9 0x291af033 in suhosin_execute_ex () from /usr/local/lib/php/20090626/suhosin.so
#10 0x081e18e4 in zend_execute_scripts ()
#11 0x0818e7b9 in php_execute_script ()
#12 0x08265066 in zend_get_zval_ptr ()
#13 0x0805d567 in _start ()
#14 0x00000000 in ?? ()
#15 0x00000000 in ?? ()
#16 0xbfbfec48 in ?? ()
#17 0x0805d567 in _start ()
#18 0x00000003 in ?? ()
#19 0xbfbfec74 in ?? ()
#20 0xbfbfec84 in ?? ()
#21 0xbfbfec60 in ?? ()
#22 0xbfbfec70 in ?? ()
#23 0x00000000 in ?? ()
#24 0xbfbfec6c in ?? ()
#25 0x0805d4d8 in _start ()
Previous frame inner to this frame (corrupt stack?)

Actions
Copy link
 #13

Updated by Warren Baker almost 13 years ago

  • File php-gdb-full.rtf added

Attached is a bt full of php-5.3.10 and modules compiled with debugging.

Actions
Copy link
 #14

Updated by Warren Baker almost 13 years ago

  • File deleted (php-gdb-full.rtf)
Actions
Copy link
 #15

Updated by Warren Baker almost 13 years ago

Warren Baker wrote:

Attached is a bt full of php-5.3.10 and modules compiled with debugging.

Lets try that again.

Actions
Copy link
 #16

Updated by Seth Mos almost 13 years ago

  • Status changed from New to Resolved

Warren committed a new php5-suhosin port which fixes the core dump by downgrading to a older patch.

Actions
Copy link
 #17

Updated by Warren Baker almost 13 years ago

  • % Done changed from 0 to 100

Just to clarify this problem a little more, Suhosin has a patch for building of PHP5 and then there is the extension (php-suhosin). In buildports.RELENG_2_0 it makes use of 0.9.27 of the extension and this version was causing the seg faults with the newer PHP version. I updated buildports.RELENG_2_1 to include an updated version of the suhosin extension (v0.9.33), which thus resolved the seg fault issue.

Actions
Copy link

Also available in: Atom PDF