Custom Query (312 matches)
Results (10 - 12 of 312)
I upgrade to xcache 2.0.0 and found 2 issues:
1) When the xcache.size is full the websites start showing 500 errors (Internal Server Error). With the previous xcache version the websites still load but didn't show the correct result.
2) I have a script that runs for 30-40 minutes. With older xcache version it works fine (or no xcache at all). With version 2.0.0 it randomly shows 500 error.
|#51||PHP v5.2.3 coredumps if using xcache r272 on pfSense HEAD||moo||DanielSHaischt|
At pfSense we are currently trying to integrate Xcache together with PHP 5.2.0. Unfortunatly XCache behaves quite unstable and causes lots of core dumps.
Disabling XCache, solves these issues.
I was able to track it down to the fact, that the following page allways results in a HTTP 500 if beeing saved and if using Xcache:
If trying to save the above page using EAccelerator I do not get a HTTP 500.
I even tried to use XCache v1.1.0 but the issue remains.
Enabled/Used? modules (in that order):
# add additional extensions below
# standard PHP extension
|#170||duplicate||xcache loads cached PHP files when directory name is changed||moo||Dark Light|
xcache loads cached PHP files when directory name is changed
xcache will load a pre-compiled PHP file if the directory name is changed. For example:
+ Create folder1 + Create file1.php ++ Inside file1 type:
<?php echo dirname(FILE); ?>
+ Save file1.php + Browse to http://dom.ext/folder1/file1.php + Copy contents to text editor
+ Rename folder1 to folder2. Keep file1.php name intact. + Browse to http://dom.ext/folder2/file1.php + Copy contents to text editor
+ You will notice the contents are the same and xcache is using the older version of the PHP script even though clearly the directory path has changed.
-- Note: Might not be an xcache bug, but it's annoying and replicable on other systems all the same. Happens with APC (Alternative PHP Cache) too.
Thank you, Best Regards,