Wordpress LScache Plugin: Fatal error: Uncaught RedisException
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hey, I had today this error bellow. Maybe its my fault because I was running too many things at the same moment in WP, but how to avoid this in future? This error was everywhere also at front-end and I must stop my Redis server to get rid of this. This Redis has 128MB RAM and I guess I overloaded this, but is it possible to set this somehow to not let this happened again? Fatal error: Uncaught RedisException: OOM command not allowed when used memory > maxmemory. in /home/path_to_my_site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php:488 Stack trace: #0 /home/path_to_my_site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php(488): Redis->setex(faf0boptions.al?, 360, a:1: s:4: data ?) #1 /home/path_to_my_site/public_html/wp-content/plugins/litespeed-cache/src/object.lib.php(323): LiteSpeed Object_Cache->set(faf0boptions.al?, a:1: s:4: data ?, 0) #2 /home/path_to_my_site/public_html/wp-content/plugins/litespeed-cache/src/object.lib.php(52): WP_Object_Cache->set(alloptions, Array, options, 0) #3 /home/path_to_my_site/public_html/wp-includes/option.php(405): wp_cache_set(alloptions, Array, options) #4 /home/path_to_my_site/public_html/wp-content/plugins/lit in /home/path_to_my_site/public_html/wp-content/plugins/litespeed-cache/src/object-cache.cls.php on line 488 This topic was modified 2 years, 6 months ago by elparts. Ok its worse than I thought .. even if nothing happens now on the website, I still have this error every time I turn on Redis :/ And I purged all few times .. I dont have Memcached I must use this and it works well few days.. Hi, Did you set TTL very long ? try shorten it Or raise the memory Best regards, Hi, Thank you, I thought maybe there is something to set in addon or WP, but I will try something from here https://ma.ttias.be/redis-oom-command-not-allowed-used-memory-maxmemory/ , as you advised. BR Hi, Well, from the message , its due to out of RAM , so either store less data, or set higher RAM. Best regards, Ok then, so it seems that LiteSpeed Cache Image Optimization was responsible for that. I just turned off option Auto Request Cron to run this manually, and this error was gone. Also, helpdesk increased RAM in my Redis to 512MB and I still had this problem. Is it possible to make this to store less data? I mean LiteSpeed Cache Image Optimization. Maybe I turn off Redis for a while until this optimization is done, and then turn it on again. I have a few thousand images but I dont think this caused problem? BR, Hi, image optimization would involves a lot of data , source file , remote file , source size , md5sum ?.etc I will ask our dev to do an improvement to handle this exception , for the time being please turn it off during the image optimization Best regards,
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference