Geek asks and answers

Magento IP Cached

We have different database IP addresses for our development and production environment. Our development environment runs locally on our development machines and points to a single development database server on our local network. Our production environment uses a database hosted on RackSpace and is hosted on a local network. One way or another, it looks like our development IP was cached during production. Here is what I have done so far:

  • Make sure the IP address in the /etc/local.xml application is on the right production.
  • Deleted the contents of var / cache / * and var / full_page_cache / *
  • Rebooted our memcached servers to clear any weird caches.
  • grepped our entire code base for the dev IP address
  • Reset mysql database and grepped dump for dev IP (we were desperate)
  • Deleted / tmp content
  • Disabled User Modules

This works for weeks without problems. This was when I turned off the cache configuration in which the problem was running. I know that you think that you just collected the configuration change that someone has made since the last time the cache was cleared. It makes sense. What doesn't make sense is that I cleared every cache mentioned above, turned on the configuration cache using MageTool , and everything works like a charm.

+5
source share
1 answer

As it turns out, fixing all of this was a two-step process.

IP-, app/etc/local.xml , app/etc/local-example.xml, app/etc/local.xml . , . , , Magento xml app/etc/.

, , IP- - , . app/etc/local.xml.example IP- . !

, , . xml , .

PHP Fatal error: Call to a member function setQueryHook() on a non-object in app/code/core/Mage/Core/Model/Resource/Setup.php on line 347

<default_setup /> node. IP- , <default_setup /> node <default_read /> <default_write />. , , / fooobar.com/questions/906657/... .

<default_write /> node <default_setup />, . , , , , .

+9

More articles:


All Articles