RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1312028 - php-5.3.3-46.el6_7.1.x86_64 crashes existing setup
Summary: php-5.3.3-46.el6_7.1.x86_64 crashes existing setup
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: php
Version: 6.7
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Remi Collet
QA Contact: BaseOS QE - Apps
URL:
Whiteboard:
Depends On:
Blocks: 1269194
TreeView+ depends on / blocked
 
Reported: 2016-02-25 14:54 UTC by Patrick
Modified: 2021-01-14 09:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-28 11:09:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
sosreport (9.69 MB, application/x-xz)
2016-02-25 14:58 UTC, Patrick
no flags Details
strace (28.29 KB, text/plain)
2016-02-26 14:17 UTC, Patrick
no flags Details

Description Patrick 2016-02-25 14:54:58 UTC
Description of problem:

Customer reports that his setup started to crash after updating to php-5.3.3-46.el6_7.1.x86_64.

the sosreport shows that also httpd was updated the same time.

php-5.3.3-46.el6_7.1.x86_64                                 Fri Feb 19 20:54:55 2016
httpd-2.2.15-47.el6_7.3.x86_64                              Fri Feb 19 20:54:49 2016



Version-Release number of selected component (if applicable):


How reproducible:
N/A

Steps to Reproduce:
1.
2.
3.

Actual results:

(gdb) bt
#0  0x00007fefe6d14c2a in gc_zobj_possible_root () from /etc/httpd/modules/libphp5.so
#1  0x00007fefe6d0399b in zend_hash_destroy () from /etc/httpd/modules/libphp5.so
#2  0x00007fefe6cf680f in _zval_dtor_func () from /etc/httpd/modules/libphp5.so
#3  0x00007fefe6ceae3a in _zval_ptr_dtor () from /etc/httpd/modules/libphp5.so
#4  0x00007fefe6d0399b in zend_hash_destroy () from /etc/httpd/modules/libphp5.so
#5  0x00007fefe6cf680f in _zval_dtor_func () from /etc/httpd/modules/libphp5.so
#6  0x00007fefe6ceae3a in _zval_ptr_dtor () from /etc/httpd/modules/libphp5.so
#7  0x00007fefe6d0399b in zend_hash_destroy () from /etc/httpd/modules/libphp5.so
#8  0x00007fefe6cef348 in destroy_zend_class () from /etc/httpd/modules/libphp5.so
#9  0x00007fefe6d0399b in zend_hash_destroy () from /etc/httpd/modules/libphp5.so
#10 0x00007fefe6cf7d54 in ?? () from /etc/httpd/modules/libphp5.so
#11 0x00007fefe6ca4d9a in php_module_shutdown () from /etc/httpd/modules/libphp5.so
#12 0x00007fefe6ca4e49 in php_module_shutdown_wrapper () from /etc/httpd/modules/libphp5.so
#13 0x00007fefe6d7efa1 in ?? () from /etc/httpd/modules/libphp5.so
#14 0x00007fefeb0ee92e in apr_pool_destroy () from /usr/lib64/libapr-1.so.0
#15 0x00007fefec62a81e in ?? ()
#16 0x00007fefec62af0b in ?? ()
#17 <signal handler called>
#18 0x00007fefeac00500 in __read_nocancel () from /lib64/libc.so.6
#19 0x00007fefded8e259 in ?? ()
#20 0x00007fff98448570 in ?? ()
#21 0x0000000000000004 in ?? ()
#22 0x00007fefeda1c5d0 in ?? ()
#23 0x00007fefed189880 in ?? ()
#24 0x0000000000000000 in ?? ()



Expected results:


Additional info:

attaching:
-core file
-sosreport

Comment 1 Patrick 2016-02-25 14:58:28 UTC
Created attachment 1130578 [details]
sosreport

Comment 3 Patrick 2016-02-26 14:17:09 UTC
Created attachment 1130835 [details]
strace

Hello,


I requested the customer to fully rollback the last yum update, and confirm if the issue came with the updates. (in progress)

While setting up a test environment, with the same  packages, the issue hasn't showed up.

Attaching the strace from the crashing apache.


Cheers,
Patrick.

Comment 4 Joe Orton 2016-02-26 18:47:50 UTC
Thanks, please confirm the version used for the rollback as well.

Comment 5 Patrick 2016-04-20 06:10:26 UTC
Hello,

Customer never confirmed the version, and now abandoned the case.


Note You need to log in before you can comment on or make changes to this bug.