On older versions of OpenPanel, Redis cannot be stopped and restarted from the OpenPanel interface due to an ongoing background process: ps aux | grep 6379 redis 466884 1.9 4.9 1929588 1634912 ? Ssl 07:02 0:24 /usr/bin/redis-server 127.0.0.1:6379 redis 467266 90.4 4.9 1929984 1628444 ? R 07:23 0:04 redis-rdb-bgsave 127.0.0.1:6379 if(window.hljsLoader && !document.currentScript.parentNode.hasAttribute('data-s9e-livepreview-onupdate')) { window.hljsLoader.highlightBlocks(document.currentScript.parentNode); } The redis-rdb-bgsave process, used by some WordPress caching plugins, temporarily copies data from memory to disk for later restoration. This makes sense when using Redis as a database but can be problematic for object caching. It requires additional disk space, and if the account runs out of space, the process will freeze, preventing Redis from restarting. In newer versions, I have added checks to prevent this issue and ensure that wp websites do not run out of disk space simply because of a redis service restart.

REDIS fails to restart on OpenPanel <0.1.9

stefan

On older versions of OpenPanel, Redis cannot be stopped and restarted from the OpenPanel interface due to an ongoing background process:

ps aux  | grep 6379
redis     466884  1.9  4.9 1929588 1634912 ?     Ssl  07:02   0:24 /usr/bin/redis-server 127.0.0.1:6379
redis     467266 90.4  4.9 1929984 1628444 ?     R    07:23   0:04 redis-rdb-bgsave 127.0.0.1:6379

The redis-rdb-bgsave process, used by some WordPress caching plugins, temporarily copies data from memory to disk for later restoration. This makes sense when using Redis as a database but can be problematic for object caching. It requires additional disk space, and if the account runs out of space, the process will freeze, preventing Redis from restarting.

In newer versions, I have added checks to prevent this issue and ensure that wp websites do not run out of disk space simply because of a redis service restart.