Closed jonathanvaughn closed 10 years ago
Derp. Apparently someone goofed while doing some dev work on our dev instance and accidentally a core_config_data path of '1', which of course would be invalid XML ... we don't normally use cache while developing to make sure changes are reflected, so it went unnoticed for awhile. I still am not quite sure why it wasn't failing config cache on and Turpentine off, but regular (no Turpentine) install using same DB had the same problem with just config cache. Closing issue.
Using turpentine 0.6.0 release on 1.11.2.0, with varnish 3.0.5 on CentOS 6.5, running PHP 5.4.31 via PHP-FPM. There's a large number of extensions, but none that should interact with caching or the config (beyond configuring themselves).
If I don't enable the Varnish cache in the Magento Cache admin page, then this error doesn't occur, and the site works normally (with Varnish doing not much of course). EE's FPC is disabled. Enabling just 'Varnish Pages' without 'Varnish ESI Blocks' also has this error, so it seems to be specific to 'Varnish Pages'.