How to Debug {“identifier”:”LOCKED_RECORD_INFO_SYSTEM_CONFIG”}} []

My Centos – Nginx Configuration, etc/nginx/conf.d/magento.conf upstream fastcgi_backend { server 127.0.0.1:9000; } server { listen 8085; server_name 192.168.1.64:8085; set $MAGE_ROOT /usr/share/nginx/html/magento; include /usr/share/nginx/html/magento/nginx.conf.sample; error_log /var/log/nginx/mage_error.log; access_log /var/log/nginx/mage_access.log; } And i am getting following response, [2020-01-18 07:02:27] main.DEBUG: cache_invalidate: {“method”:”GET”,”url”:”http://192.168.1.64:8085/“,”invalidateInfo”:{“identifier”:”interception”}} [] [2020-01-18 07:02:31] main.DEBUG: cache_invalidate: {“method”:”GET”,”url”:”http://192.168.1.64:8085/“,”invalidateInfo”:{“identifier”:”LOCKED_RECORD_INFO_SYSTEM_CONFIG”}} [] How to debug above response?

Details

IPVS: Is it still neccessary to handle ARP problems with newer kernel?

I set up a load balancer with ipvs and several howtos are claiming that it is neccessary to set net.ipv4.conf.<interface>.arp_ignore=1 and net.ipv4.conf.<interface>.arp_announce=2 at the backend servers for routed setup. By accident the sysctl.conf was overwritten and those option were set to 0—and the LB is still working as expected. This raises the question: Is it…

Details