-
Bug
-
Resolution: Fixed
-
Minor
-
3.6.4, 3.7, 3.9.3, 3.10, 4.0
-
MOODLE_310_STABLE, MOODLE_36_STABLE, MOODLE_37_STABLE, MOODLE_39_STABLE, MOODLE_400_STABLE
-
MOODLE_310_STABLE, MOODLE_39_STABLE
-
MDL-65941-master -
If you have an instance of the redis cache store, and Moodle is unable to connect to the redis server, the cache configuration page fails with an exception. This is unlike the behaviour of other stores, like memcached, where the instance is simply marked as "not ready" if the server can't be contacted.
This is potentially a pretty serious issue for server administrators as it makes it impossible to switch to another cache store while a redis server is unavailable.
To reproduce (with a working redis server):
- Create a redis cache instance. Confirm that it shows as "ready".
- Kill the redis server (either kill the process, or the container)
- Go back to the cache page.
- You will see an error message (either "Connection refused" or "getaddrinfo failed" depending on what you did in step 2) and be unable to edit your cache configuration.
I'm seeing this with versions 4.1.1 and 4.3.0 of the redis plugin.