1

I am running EE 1.14.0.1 and PHP 5.6 and got below error on production server only. I cleared the cache and implement the solutions suggested by @folektoras133 at Security Patch SUPEE-9767 - Possible issues?. nothing worked. Any suggestion ?

a:5:{i:0;s:29:"Decoding failed: Syntax error";i:1;s:1397:"#0 //htdoc/app/code/local/Enterprise/PageCache/Model/Observer.php(178): Zend_Json::decode('a:0:{}')
packet_write_wait: Connection to 52.26.63.162 port 22: Broken pipegeCache/Model/logouter.php(214): Enterprise_PageCache_Model_Observer->_loadDesignExceptions()
Saving session.../htdoc/app/code/local/Enterprise/PageCache/Model/...copying shared history...e_PageCache_Model_Observer->_saveDesignException()
...saving history...truncating history files...core/Mage/Core/Model/App.php(1339...completed._PageCache_Model_Observer->cacheResponse(Object(Varien_Event_Observer))
[Process completed]#4 //htdoc/app/code/core/Mage/Core): Mage_Core_Model_App->_callObserverMethod(Object(Enterprise_PageCache_Model_Observer), 'cacheResponse', Object(Varien_Event_Observer))
#5 //htdoc/app/Mage.php(448): Mage_Core_Model_App->dispatchEvent('controller_fron...', Array)
#6 //htdoc/app/code/core/Mage/Core/Controller/Varien/Front.php(182): Mage::dispatchEvent('controller_fron...', Array)
#7 //htdoc/app/code/core/Mage/Core/Model/App.php(354): Mage_Core_Controller_Varien_Front->dispatch()
#8 //htdoc/app/Mage.php(684): Mage_Core_Model_App->run(Array)
#9 //htdoc/index.php(90): Mage::run('', 'store')
#10 {main}";s:3:"url";s:161:"/product_page?utm_source=google_shopping&gclid=CjwKEAjwgtTJBRDRmd6ZtLrGyxwSJAA7Fy-hBnSgpddfHXC9mP9HkKPPk3WbbtZfbd7voy-K2NSd5BoC0eLw_wcB";s:11:"script_name";s:10:"/index.php";s:4:"skin";s:7:"default";}

closed as off-topic by Jai, Manoj Deswal, liyakat, Prince Patel, Manthan Dave Oct 24 '17 at 12:02

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions describing a problem that can't be reproduced OR seemingly went away on its own (or went away when a typo was fixed) are off-topic as they are unlikely to help future readers." – Jai, Manoj Deswal, liyakat, Prince Patel, Manthan Dave
If this question can be reworded to fit the rules in the help center, please edit the question.

1

I found the solution. We are using Redis Caching. So I had to disable the default caching on production Magento. Once I did that the site worked fine. Also another thing to be take in consideration we have multiple AWS EC2 instances running on production. but one EC2 instance for development. I am not sure why this would cause the problem but its solved now.

Thanks everyone.

  • What is the "Default" cache? Can you explain more on this? Do we need to disable Magento's default caching(i.e. Configuration, Layouts, Blocks HTML output, Translations, Collections Data, EAV types and attributes, Web Services Configuration, Web Services Configuration, Amasty Improved Navigation) – groy Mar 7 at 18:09
  • yes, you need to disable them because they are conflicting with Redis. – Zeedia Mar 9 at 1:31
  • But if we disable the default cache then how redis will work? Redis get same cache data from default cache right? – groy Mar 9 at 14:28

Not the answer you're looking for? Browse other questions tagged or ask your own question.