From f798ddd4922d793d5e6ccb7c4111810d549ff4f4 Mon Sep 17 00:00:00 2001 From: Gaspard d'Hautefeuille Date: Wed, 9 Jul 2025 07:55:37 +0200 Subject: [mod] migrate from Redis to Valkey (#4795) This patch migrates from `redis==5.2.1` [1] to `valkey==6.1.0` [2]. The migration to valkey is necessary because the company behind Redis has decided to abandon the open source license. After experiencing a drop in user numbers, they now want to run it under a dual license again. But this move demonstrates once again how unreliable the company is and how it treats open source developers. To review first, read the docs:: $ make docs.live Follow the instructions to remove redis: - http://0.0.0.0:8000/admin/settings/settings_redis.html Config and install a local valkey DB: - http://0.0.0.0:8000/admin/settings/settings_valkey.html [1] https://pypi.org/project/redis/ [2] https://pypi.org/project/valkey/ Co-authored-by: HLFH Co-authored-by: Markus Heiser --- docs/admin/installation-uwsgi.rst | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'docs/admin/installation-uwsgi.rst') diff --git a/docs/admin/installation-uwsgi.rst b/docs/admin/installation-uwsgi.rst index 78da22f45..a2152409e 100644 --- a/docs/admin/installation-uwsgi.rst +++ b/docs/admin/installation-uwsgi.rst @@ -235,19 +235,19 @@ major release is from Dec. 2013, since the there had been only bugfix releases **In Tyrant mode, there is no way to get additional groups, and the uWSGI process misses additional permissions that may be needed.** -For example on Fedora (RHEL): If you try to install a redis DB with socket +For example on Fedora (RHEL): If you try to install a valkey DB with socket communication and you want to connect to it from the SearXNG uWSGI, you will see a *Permission denied* in the log of your instance:: - ERROR:searx.redisdb: [searxng (993)] can't connect redis DB ... - ERROR:searx.redisdb: Error 13 connecting to unix socket: /usr/local/searxng-redis/run/redis.sock. Permission denied. + ERROR:searx.valkeydb: [searxng (993)] can't connect valkey DB ... + ERROR:searx.valkeydb: Error 13 connecting to unix socket: /usr/local/searxng-valkey/run/valkey.sock. Permission denied. ERROR:searx.plugins.limiter: init limiter DB failed!!! Even if your *searxng* user of the uWSGI process is added to additional groups -to give access to the socket from the redis DB:: +to give access to the socket from the valkey DB:: $ groups searxng - searxng : searxng searxng-redis + searxng : searxng searxng-valkey To see the effective groups of the uwsgi process, you have to look at the status of the process, by example:: @@ -257,7 +257,7 @@ of the process, by example:: searxng 186 93 0 12:44 ? 00:00:01 /usr/sbin/uwsgi --ini searxng.ini Here you can see that the additional "Groups" of PID 186 are unset (missing gid -of ``searxng-redis``):: +of ``searxng-valkey``):: $ cat /proc/186/task/186/status ... -- cgit v1.2.3