Critical error on this website

I got the error showing after few hours :

PHP Fatal error: Uncaught RedisException: read error on connection to redis:6379 in /var/www/html/wp-content/object-cache.php:1622\nStack trace:
\n#0/var/www/html/wp-content/object-cache.php(1622): Redis->flushDB()
\n#1 /var/www/html/wp-content/object-cache.php(149): WP_Object_Cache->flush()
\n#2 /var/www/html/wp-content/plugins/redis-cache/includes/class-plugin.php(777): wp_cache_flush()
\n#3 /var/www/html/wp-includes/class-wp-hook.php(308): Rhubarb\RedisCache\Plugin->do_admin_actions(”)
\n#4 /var/www/html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(”, Array)
\n#5 /var/www/html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
\n#6 /var/www/html/wp-admin/admin.php(237): do_action(‘load-settings_p…’)
\n#7 /var/www/html/wp-admin/options-general.php(10): require_once(‘/var/www/html/w…’)
\n#8 {main}\n thrown in /var/www/html/wp-content/object-cache.php on line 1622, r

Hey!

The error read error on connection mean Redis is not available. We recommend using supervisord to keep Redis Server up and running.

More in the FAQ: https://github.com/rhubarbgroup/redis-cache/blob/develop/FAQ.md

Monitored and the redis server is still running pretty fine even when the error occurs , ill try with a previous version and tell u what happens till its a new bug :).

if not i still have the solution to purge by cron anyway but i wanna know whats causing that ??

Another info : memory usage on redis server keeps growing until flush :

I am having the same problem with Redis Object Cache on all my websites. All The websites break if I do the latest update 2.3.0. I was thinking maybe you would have corrected this error by now with a new update? Your reply about read error on connection is NOT the same as totally breaking the websites and I don’t see a way to solve this with your reply.

@fiddlinground: please open a dedicated support threat and post your diagnostics, happy to help.

@banzine: It’s good to set a eviction policy on Redis Server, if you’re limited by memory.

If you post your full diagnostics I can probably help out.

What is the support request link?

https://www.ads-software.com/support/plugin/redis-cache/

onitored this week, it seems to be caused by a timeout on a specific script (removed timeout on php side to better see that problem)

Lua slow script detected: still in execution after 5015 milliseconds. You can try killing the script using the SCRIPT KILL command. Script SHA1 is: c259f127d603969c44f4a3671ba77cb03ca56e8a

And

RedisException: BUSY Redis is busy running a script. You can only call SCRIPT KILL or SHUTDOWN NOSAVE. on php site.

Any advice to track the script causing the problem?

@banzine: That’s common, can you post your full Diagnostics?