Bug 9628

Summary:	phpmyadmin or wordpress doesn't work if php eaccelerator is enabled
Product:	Mageia	Reporter:	Christian D <christian_duhaut>
Component:	RPM Packages	Assignee:	Thomas Spuhler <thomas>
Status:	RESOLVED FIXED	QA Contact:
Severity:	major
Priority:	Normal	CC:	olivier.delaune
Version:	Cauldron	Keywords:	Triaged
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	php-eaccelerator-0.9.6.1git20120725	CVE:
Status comment:

Description Christian D 2013-04-05 23:06:50 CEST

Description of problem:
several PHP/mysql applications (phpmyadmin, worddpress, piwigo) are not working if eaccelerator is enabled :
- the browser return a blank page with a server error
- the httpd error_log file contains errors concerning "eaccelerator"

Version-Release number of selected component (if applicable): mageia 3 beta 3 or beta 4

How reproducible: 
Every time I try to access to wordpress (installation process) or phpmyadmin through various browsers (firefox, chromium, konqueror).
Oddly, phpmyadmin works on a AMD Athlon X2 5000 PC. Doesn't work on Intel PCs (Core 2 duo processor or VirtualBox VM on a i7 host).
Wordpress doesn't work nor in my Intel or AMD based PCs.

If I disable "eaccelerator" in "/etc/php.d/Z99_eaccelerator.ini", the applications are working (I tested phpmyadmin, wordpress, piwigo)

Steps to Reproduce:
1. install mageia 3 beta 3 or beta 4 : on a VirtualBox VM (32 or 64 - intel host) or on a hard drive (core 2 duo)
1b. update the distribution : urpmi --auto-update (optional)
2. install the task-lamp package
3. install the wordpress package (from mageia)
4. set a root password for mysql - comment "skip-networking" in my.conf
5. try phpmyadmin : doesn't work
6. try wordpress install process (after creattion of a database ..) : doesn't work
7 : disable "eaccelerator" and restart apache : everything works.

Maybe this problem si similar to these ones related to Mageia 1 and 2 :  https://bugs.mageia.org/show_bug.cgi?id=2780
https://bugs.mageia.org/show_bug.cgi?id=5781


Reproducible: 

Steps to Reproduce:

Christian D 2013-04-05 23:28:16 CEST

Source RPM: (none) => php-eaccelerator 0.9.6.1git20120725 5.mga3

Olivier Delaune 2013-04-06 11:41:46 CEST

CC: (none) => olivier.delaune

Comment 1 Christian D 2013-04-06 15:12:50 CEST

I found some additionnal information concerning php-eaccelerator :

- according to this post dedicated to fedora, php-eaccelerator seems to be not very active, or at least, not compatible with the latest versions of php : http://blog.famillecollet.com/post/2013/03/25/PHP-opcode-and-user-data-cache
- I checked the official packages list of fedora 18 : it seems php-eaccelerator is not included

So, maybe php-eaccelerator should be simply removed from the Mageia packages, or at least from the dependencies of task-lamp and task-lamp-php.

Manuel Hiebel 2013-04-06 22:43:14 CEST

Keywords: (none) => Triaged
Assignee: bugsquad => thomas
Source RPM: php-eaccelerator 0.9.6.1git20120725 5.mga3 => php-eaccelerator-0.9.6.1git20120725

Comment 2 Thomas Spuhler 2013-04-07 02:40:33 CEST

Thanks for your report
I experienced similar problems ( I recall pear update not working anymore if this is installed)
Since there have been no other bug reports, I assume this package isn't used anymore by anybody using Mageia.
If nobody objects, I will get it removed.

Status: NEW => ASSIGNED

Comment 3 Christian D 2013-04-07 10:43:17 CEST

In fact, I think this package is used by a lot of people, but without knowing it, because it is installed automatically with the package "task-lamp-php". In the french cauldron Mageia forum, a thread concerning php/mysql problems is one of the most consulted (1158 times at that moment) : http://www.mageialinux-online.org/forum/topic-14380+apache-mysql-avec-mageia3.php.
Some bug was reported, but without knowing the origin of the bug : for example this one : https://bugs.mageia.org/show_bug.cgi?id=9511 . Maybe others.

Comment 4 Thomas Spuhler 2013-04-07 20:30:00 CEST

Hmmm..., so we may put it in task-obsolete.
If it doesn't, and it's not fixable  we should remove it.

But there is the requires

$ urpmq --whatrequires php-eaccelerator
php-eaccelerator
php-eaccelerator-admin

$ urpmq --whatrequires php-eaccelerator-admin
php-eaccelerator-admin
task-lamp-php
The maintainer of task-lamp is nobody

Comment 5 Christian D 2013-04-07 23:10:31 CEST

I agree with you : if you cannot fix it, php-eaccelerator and php-eaccelerator-admin should be removed (as they did in fc18).

Il think that tweaking web servers performances is more a question for experts and only useful for heavy loaded web servers.

I just wanted to point out, in my previous comment, that this problem can raise automatically because non specialists will use the task-lamp or the task-lamp-php package (as I used to do). So it is important to remove eaccelerator from the dependencies of task-lamp-php (which is an empty package - if I am right).

Comment 6 Thomas Spuhler 2013-04-08 00:49:16 CEST

should be fixed now. Could you please test it.
(Removed the packages from repo and task-lamp)
put them into task-obsolete

Comment 7 Christian D 2013-04-08 09:10:32 CEST

I just test it in a virtual machine 64. The result if OK.
I did the following test :
- re-activation of eaccelerator : just to confirm phpmyadmin doesn't work
- "urpmi --auto-update" : eaccelerator was desinstalled during the process
- test of phpmyadmin and wordpress : OK

Thanks a lot.

Comment 8 Christian D 2013-04-08 10:42:31 CEST

I did a other test in VM 586. The problem is fixed too (wordpress was unable to run, and now, it is OK).

Comment 9 Thomas Spuhler 2013-04-08 17:16:36 CEST

Thanks for all the testing. I will close this bug now as resolved.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED