Last modified: 2013-09-04 11:49:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T31747, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 29747 - Not found installed eAccelerator
Not found installed eAccelerator
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Installer (Other open bugs)
1.17.x
All Linux
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 33693
  Show dependency treegraph
 
Reported: 2011-07-06 20:40 UTC by JSkart
Modified: 2013-09-04 11:49 UTC (History)
3 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description JSkart 2011-07-06 20:40:07 UTC
phpinfo show eAccelerator but mediawiki installer can't found it.
Comment 1 Sam Reed (reedy) 2011-07-06 20:41:41 UTC
Can you give us relevant version number (php, etc) for ease of reference?
Comment 2 JSkart 2011-07-06 20:54:14 UTC
mediawiki  1.17.0-1
lighttpd  1.4.28-6
php-fpm  5.3.6-4
eaccelerator  0.9.6.1-1
Comment 3 Sam Reed (reedy) 2011-07-06 20:57:52 UTC
It seems, from a quick google, there is some funky things about eaccelerator_get, and them being disabled

http://adminuser.wordpress.com/2008/01/15/fatal-error-unknown-function-eaccelerator_get-in-somefile/
Comment 4 JSkart 2011-07-06 21:00:10 UTC
yes, i changed script to check eaccelerator_info instead of eaccelerator_get. Is it good way?
Comment 5 Sam Reed (reedy) 2011-07-06 21:01:20 UTC
Seemingly not

Unless I'm mistaken, if there isn't the get/put functions, this caching isn't going to be usable, is it? :/
Comment 6 JSkart 2011-07-06 21:22:25 UTC
Seems i should just use eaccelerator 0.9.5.3
Comment 7 Brion Vibber 2011-07-07 00:42:14 UTC
Possibly the installer should detect that eaccelerator is present but the caching functions are disabled, and offer a link to info about that option.

Honestly though I'm very leery of any of the opcode-cache-plus caching options like this; they're already *totally unsafe* to use if you use any command-line scripts or have multiple web servers, and that can easily be something that a user isn't even aware of if they're on shared hosting. I tend to advocate removing support for eAccelerator-based caching entirely.
Comment 8 Chad H. 2011-11-22 22:56:26 UTC
Removed eAccelerator shared memory caching entirely in r103973.
Comment 9 Subfader 2012-01-12 08:11:04 UTC
I have the same problem with eAccelerator 0.9.6.1 (which I am forced to use)

"Removed eAccelerator shared memory caching entirely"

What does that mean? eAccelerator is not supported anymore?

http://www.mediawiki.org/wiki/Manual:Cache#PHP_caching
Comment 10 Chad H. 2012-01-12 15:01:30 UTC
(In reply to comment #9)
> What does that mean? eAccelerator is not supported anymore?
> 

Yes, that's exactly what it means.

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


Navigation
Links