dev

Indeed its a strange issue.

The exact error in the google merchant store is “Invalid image encoding [image link]” this is due to it being the page URL rather than an image.

This is the support page:
https://support.google.com/merchants/answer/6183365?hl=en

Ithemes security (hide login) had to be disabled before we could gain access to WP backend and restore of the .htaccess file

Not sure what caused the .htaccess file to break in the process but something removed the default wordpress lines.

• This reply was modified 5 years, 3 months ago by dev.

No worries, thank you for your support.

So when enabling object crashing eventually the whole multisite goes down not just the wordpress backend. This is where we start to see the issue before eventually the whole site does. A reboot of the server nor services brings it back and requires for it to be disabled within the master.php.

We’ve been using memcached tools to check the contents. This is how we know with the previous RDS config pagecache had some data chunks in there and could confirm DB caching works correctly now with the RDS changes.

Update: we created the custom options group in AWS for the RDS instance and DB caching started to work properly with Memcache. Seems Pagecache worked without this from reviewing the Memcache data.

Objectcache when enabled (DB caching disabled), starting to create 1-2k objects in Memcache before the website eventually went down again. Could be resource issues when objectcache is enabled and start a heavy load on the server but seems odd.

So we’ve copied the prod version of our multisite to a new dev site with no outbound internet access apart from cloudflare etc. It can be configured to use either object Memcached or disk cache without issue. It seems we cannot replicate the original issue within the Dev environment.

No errors in wp-log and nothing out of the ordinary with the W3TC debug on the dev site.

Tried again in the prod site and object caching seems fine with disk caching but with high PHP CPU usage (up to 70% instead of 1-15%). This slows the site down in general. When switched to Memcache it starts to slow the site before getting constant timeouts. Restart of the wordpress services and it starts up and will only serve timeouts within the access logs. Only way to stop it is to disabled object caching within the master.php and restart the wp services again.

Have tried using ‘wp cache flush’ and clearing the Memcache directly but still wont work with Object cache + Memcache enabled.

We’ve also moved the WP instance to a new host and cleared the cache folder within WP but the issue persists.

Hello,

So I’ve taken this from the master.php as the I can’t upload a screenshot but can email one over if preferable.

"objectcache.configuration_overloaded": false,
    "objectcache.enabled": false,
    "objectcache.debug": false,
    "objectcache.debug_purge": false,
    "objectcache.enabled_for_wp_admin": false,
    "objectcache.fallback_transients": true,
    "objectcache.engine": "memcached",
    "objectcache.file.gc": 3600,
    "objectcache.file.locking": false,
    "objectcache.memcached.servers": [
        "SERVER.cache.amazonaws.com:11211"
    ],
    "objectcache.memcached.persistent": true,
    "objectcache.memcached.aws_autodiscovery": false,
    "objectcache.memcached.username": "",
    "objectcache.memcached.password": "",
    "objectcache.memcached.binary_protocol": true,
<snipped>>
objectcache.groups.global": [
        "users",
        "userlogins",
        "usermeta",
        "user_meta",
        "site-transient",
        "site-options",
        "site-lookup",
        "blog-lookup",
        "blog-details",
        "rss",
        "global-posts"
    ],
    "objectcache.groups.nonpersistent": [
        "comment",
        "counts",
        "plugins"
    ],
    "objectcache.lifetime": 180,
    "objectcache.purge.all": false,

We have a single Memcached for DB caching, page caching etc which is very underutilised. When we disable DB caching, we clear the cache before enabling the Objecting caching.

Thank you for the assistance

Kind Regards

Can anyone confirm v3.0.2 fixes these issues ?