I have a magento 188.8.131.52 and all caches are turned on, why is
var/cache empty? I can only empty the cache from the backend, but when this is broken, I have a problem.
Where does magento write the cache files?
Could also be you are using a different cache storage like
If you have a
var dir or even a
var/cache dir, but Magento can't write to it, Magento will use
sys_get_temp_dir() to determine a good place to put the caching files.
Often this is
/tmp/ and results in
/tmp/magento/var/cache (Thanks to fschmengler)
I ran into this problem when magento writes it cache file to
This is weird issue, I had solved this SELinux issue by following command.
$ sudo restorecon -R /var/www/html $ sudo setsebool -P httpd_unified 1
To whom it affects. Any file that ends with "
.xml" can and will be used.
It is not enough to just rename the XML file to something like
oldsomething.xml you must do something like
local.xml.back where the file does not end a with dot XML. Leaving
oldlocal.xml will load both files.
I don't know enough about the inner workings to know why this is, but I have tested it to know it is true. You can prove this by putting in something that will break Magento in the renamed XML, and Magento stops working.
Maybe the Magento code does not discriminate the file name but just the extension in a certain location?
My website is still on Magento 184.108.40.206
Too shy to update (it ain't broke) but I did put the 1.8 Redis part in and it seems to work. I am testing 220.127.116.11 but not ready for prime time yet as some of my extensions no longer work.
Try https://github.com/steverobbins/Magento-Redismanager. I like it you may like it too!
Manage to solve the issue and it's the weirdest thing ever. When I change the
local.xml to fix the issue I put a backup of the old file saying
local_back.xml. I just delete that file and now everything is working fine. No idea why Magento pick that file up. Anyways issue has been solved.
Perhaps someone is not understanding what is happening or my answer, as in the other commits Magento is going to load all that ends with ".xml". So if you want backups or copies that are not used appending back or backup or anything else WILL NOT WORK!
back_local.xml will not work
If you want copies or backups you need to change the suffix of the file name, or in other word in the format of "local.xml.backup or kill the .xml altogether. I use local.xml.backup as a copy while I am testing, as I can easily remove the ".backup" to use it if I want. You can always use 'Save As' in an editor for different versions, like .back_today, or .back2 and such.
For your information Magento load .xml files in Mage_Core_Model_Config in function loadBase(). It takes all .xml with the PHP function glob() at the begining $files = glob($etcDir.DS.'*.xml'); – Matthéo Geoffray Feb 17 '16 at 14:56
So while testing different backends use the above format.
As for APC memcached, they are outdated and do not use keys like Redis. From what I understand there is no significant difference between
[files], [db], [memcache] or other cache as it seems to be more of a situation of the server response time and/or hard drives used on the server. See: "Magento Session Storage: Which to Choose and Why?"
When My VPS (InMotion) changed to strictly Solid State Hard drives everything was tremendously faster. I was getting Milli-second transfers!
On my own test servers at home the one box that uses HST 10k spindle speed and a boat load of cache, like 64 MB (Marked for server use), hard drive is very fast and the other box very slow with the Hard drives you get from an OEM box.
Also having 8 CPU cores and 32GB of RAM helps alot. So much of what is offered on-line as a VPS or even dedicated server is a cheat!!! You need to get into the details or the resources you will get as Unlimited means nothing if the server is in reality shared hosting passed off as something else. And don't let the Pictures mislead you as to what their facility might really be. You might get something like Hillary got for her email, just something in a bathroom closet. The hook is they often want a year or more contract to get the good price and it could take a month or more to optimize your setup before you learn you are just on a slow server!!!