Bug 751569
Summary: | php-eaccelerator-0.9.6.1-1.el6.x86_64 is broken | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | Harald Reindl <h.reindl> |
Component: | php-eaccelerator | Assignee: | Matthias Saou <matthias> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | el6 | CC: | matthias, n.beernink, sistemas |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-11-30 15:03:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Harald Reindl
2011-11-05 18:07:51 UTC
PHP processes crashes with php-accelerator enabled. With a Wordpress 3.2 installation the wp-admin/edit.php crashes. This is the process strace: write(4, "\227\0\0\0\3SELECT t.*, tt.* FROM wp_terms AS t INNER JOIN wp_term_taxonomy AS tt ON t.term_id = tt.term_id WHERE tt.taxonomy IN ('category') ORDER BY t.name ASC ", 155) = 155 read(4, "\1\0\0\1\n6\0\0\2\3def\twordpress\1t\10wp_terms\............................) --- SIGSEGV (Segmentation fault) @ 0 (0) --- rt_sigaction(SIGSEGV, {SIG_DFL, [SEGV], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, {0x7f9333a8faa0, [SEGV], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, 8) = 0 rt_sigaction(SIGFPE, {SIG_DFL, [FPE], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, {0x7f9333a8faa0, [FPE], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, 8) = 0 rt_sigaction(SIGBUS, {SIG_DFL, [BUS], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, {0x7f9333a8faa0, [BUS], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, 8) = 0 rt_sigaction(SIGILL, {SIG_DFL, [ILL], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, {0x7f9333a8faa0, [ILL], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, 8) = 0 rt_sigaction(SIGABRT, {SIG_DFL, [ABRT], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, {0x7f9333a8faa0, [ABRT], SA_RESTORER|SA_RESTART, 0x7f933cda8980}, 8) = 0 stat("/etc/localtime", {st_mode=S_IFREG|0644, st_size=2593, ...}) = 0 write(2, "[Tue Nov 15 12:38:22 2011\n] [notice] EACCELERATOR(31062): PHP crashed on opline 33 of view_switcher() at /var/www/DOMAIN/wp-admin/includes/class-wp-list-table.php:412\n\n", 176) = 176 kill(31062, SIGSEGV) = 0 rt_sigreturn(0x7956) = 0 --- SIGSEGV (Segmentation fault) @ 0 (0) --- Process 31062 detached After upgrading the following packages, I can confirm PHP processes crash when php-eaccelerator is left enabled. Updated php-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated php-cli-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated php-common-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated php-gd-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated php-imap-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated php-ldap-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated php-mbstring-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated php-mysql-5.3.2-6.el6_0.1.x86_64? Update5.3.3-3.el6_1.3.x86_64@base Updated php-pdo-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated php-pear-1:1.9.0-2.el6.noarch ? Update 1:1.9.4-4.el6.noarch @base Updated php-xml-5.3.2-6.el6_0.1.x86_64 ? Update 5.3.3-3.el6_1.3.x86_64 @base Updated phpMyAdmin-3.4.7.1-1.el6.noarch ? Update 3.4.8-1.el6.noarch @epel This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is our policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. This message is a reminder that EPEL 6 is nearing its end of life. Fedora will stop maintaining and issuing updates for EPEL 6 on 2020-11-30. It is policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of 'el6'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later EPEL version. Thank you for reporting this issue and we are sorry that we were not able to fix it before EPEL 6 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version, you are encouraged to change the 'version' to a later version prior this bug is closed as described in the policy above. EPEL el6 changed to end-of-life (EOL) status on 2020-11-30. EPEL el6 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of EPEL please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |