hi, I got my server down.

  • Resolved benlee

    (@benlee)


    3 years ago

    Hi, I’m using w3 total cache plugin.
    and I’m using cloudways hosting which provide redis server management.
    so i turn on “object cache – redis”
    and i also read about “terminal SSH” and i put the code “redis-cli monitor” at the end of my applications terminal ssh.

    but after a day passed. my site is all stuck, so i asked my cloudways service team to fix this, and they said, this w3 total cache plugin conflicts with something, so my site is stuck. so they deactivate w3 cache plugin.

    for your information, the stuck message : translation ( ” this site has crucial error, learn more about to fix this serious error”)

    is it because of redis-cli monitor code setting ? what is causing the conflicts with this plugin?

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter benlee

    (@benlee)

    For now, as soon as I activate “w3 total cache plugin”, my site’s down.

    I thought the “redis-cli monitor” code I put in the SSH terminal was the cause, so I asked the hosting server team to delete it, but they said it didn’t exist at all.

    I’m worried about setting all the option’s gonna disappear. I hope it will be fixed soon.

    thank you always.

    this is from email from wordpress

    ?? E_ERROR? ??? /home/660919.cloudwaysapps.com/wdcnunnbtn/public_html/wp-content/plugins/w3-total-cache/Cache_Redis.php ??? 163 ??? ??????. ?? ???: Uncaught RedisException: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error. in /home/660919.cloudwaysapps.com/wdcnunnbtn/public_html/wp-content/plugins/w3-total-cache/Cache_Redis.php:163
Stack trace:
#0 /home/660919.cloudwaysapps.com/wdcnunnbtn/public_html/wp-content/plugins/w3-total-cache/Cache_Redis.php(163): Redis->setex()
#1 /home/660919.cloudwaysapps.com/wdcnunnbtn/public_html/wp-content/plugins/w3-total-cache/ObjectCache_WpObjectCache_Regular.php(351): W3TC\Cache_Redis->delete()
#2 /home/660919.cloudwaysapps.com/wdcnunnbtn/public_html/wp-content/plugins/w3-total-cache/ObjectCache_WpObjectCache.php(63): W3TC\ObjectCache_WpObjectCache_Regular->delete()
#3 /home/660919.cloudwaysapps.com/wdcnunnbtn/public_html/wp-conten

    for your information, it is from cloudways service team.

    [Tue Nov 23 09:12:27.457211 2021] [proxy_fcgi:error] [pid 30456:tid 140375477536512] [client 141.136.201.82:22838] AH01071: Got error 'PHP message: require_once('wp-admin/admin.php'), require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), include_once('/plugins/yoast-seo-settings-xml-csv-import/yoast-addon.php'), yoast_seo_addon_get_post_type, W3TC\\DbCache_WpdbNew->query, W3TC\\DbCache_WpdbInjection_QueryCaching->query, W3TC\\_CallUnderlying->query, W3TC\\DbCache_WpdbNew->query, W3TC\\DbCache_WpdbInjection->query, W3TC\\DbCache_WpdbNew->default_query\xec\x9d\xb4(\xea\xb0\x80) \xeb\xa7\x8c\xeb\x93\xa0 SELECT options FROM wp_pmxi_imports WHERE id = 0 \xec\xbf\xbc\xeb\xa6\xac\xec\x97\x90 \xec\x9b\x8c\xeb\x93\x9c\xed\x94\x84\xeb\xa0\x88\xec\x8a\xa4 \xeb\x8d\xb0\xec\x9d\xb4\xed\x84\xb0\xeb\xb2\xa0\xec\x9d\xb4\xec\x8a\xa4 \xec\x98\xa4\xeb\xa5\x98 Table 'neegvtmsdu.wp_pmxi_imports' doesn't exist(\xec\x9d\xb4)\xea\xb0\x80 \xec\x9e\x88\xec\x8a\xb5\xeb\x8b\x88\xeb\x8b\xa4'

?[Tue Nov 23 09:12:27.764782 2021] [proxy_fcgi:error] [pid 30456:tid 140375762888448] [client 141.136.201.82:22860] AH01071: Got error 'PHP message: PHP Fatal error: Uncaught RedisException: MISCONF Redis is configured to save RDB snapshots, but it is currently not able to persist on disk. Commands that may modify the data set are disabled, because this instance is configured to report errors during writes if RDB snapshotting fails (stop-writes-on-bgsave-error option). Please check the Redis logs for details about the RDB error. in /home/660919.cloudwaysapps.com/neegvtmsdu/public_html/wp-content/plugins/w3-total-cache/Cache_Redis.php:73\nStack trace:\n#0 /home/660919.cloudwaysapps.com/neegvtmsdu/public_html/wp-content/plugins/w3-total-cache/Cache_Redis.php(73): Redis->setex()\n#1 /home/660919.cloudwaysapps.com/neegvtmsdu/public_html/wp-content/plugins/w3-total-cache/ObjectCache_WpObjectCache_Regular.php(293): W3TC\\Cache_Redis->set()\n#2 /home/660919.cloudwaysapps.com/neegvtmsdu/public_html/wp-content/plugins/w3-total-cache/ObjectCache_WpObjectCache_Regular.php(388): W3TC\\ObjectCache_WpObjectCache_Regular->set()\n#3 /home/660919.cloudw...', referer: https://mint.stankorea.com/wp-admin/
    • This reply was modified 3 years ago by benlee.
    • This reply was modified 3 years ago by benlee.
    Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @benlee

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    The error message you received does not say much, so whenever the website encounters this kind of problem, the best thing to do si to check the debug.log
    In order to check this, you need to have WP_DEBUG defined in wp-config.php

    define( 'WP_DEBUG', true );
 define( 'WP_DEBUG_DISPLAY', false );
 define( 'WP_DEBUG_LOG', true );

    Debugging is now enabled on your site and errors will be written to the log. You can find the debug log in the wp-content folder, named debug.log.
    If you already had enabled the debug, the debug.log will show what may have happened.
    If not, I would recommend adding the provided constants, completely removing and re-install W3 Total Cache as I’ve suggested in the other topic you opened, and making sure that you are not using the same options in W3 Total Cache and some other plugin. Like for example Redis Object Cache. In this case, make sure that W3TC Object Caching is disabled.
    Let me know if this helps!
    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘hi, I got my server down.’ is closed to new replies.