forked from pool/redis
a5451d0ee4
- redis 6.2.1 Bug fixes: * Fix sanitize-dump-payload for stream with deleted records (#8568) * Prevent client-query-buffer-limit config from being set to lower than 1mb (#8557) Improvements: * Make port, tls-port and bind config options modifiable at runtime (#8510) Platform and deployment-related changes: * Fix compilation error on non-glibc systems if jemalloc is not used (#8533) * Improved memory consumption and memory usage tracking on FreeBSD (#8545) * Fix compilation on ARM64 MacOS with jemalloc (#8458) Modules: * New Module API for getting user name of a client (#8508) * Optimize RM_Call by utilizing a shared reusable client (#8516) * Fix crash running CLIENT INFO via RM_Call (#8560) - includes changes from 6.2.0 GA: * Integer overflow on 32-bit systems (CVE-2021-21309) Bug fixes: * Avoid 32-bit overflows when proto-max-bulk-len is set high (#8522) * Fix broken protocol in client tracking tracking-redir-broken message (#8456) * Avoid unsafe field name characters in INFO commandstats, errorstats, modules (#8492) * XINFO able to access expired keys during CLIENT PAUSE WRITE (#8436) * Fix allowed length for REPLCONF ip-address, needed due to Sentinel's support for hostnames (#8517) * Fix broken protocol in redis-benchmark when used with -a or --dbnum (#8486) * XADD counts deleted records too when considering switching to a new listpack (#8390) Bug fixes that are only applicable to previous releases of Redis 6.2: * Fixes in GEOSEARCH bybox (accuracy and mismatch between width and height) (#8445) * Fix risk of OOM panic in HRANDFIELD, ZRANDMEMBER commands with huge negative count (#8429) * Fix duplicate replicas issue in Sentinel, needed due to hostname support (#8481) * Fix Sentinel configuration rewrite, an improvement of #8271 (#8480) OBS-URL: https://build.opensuse.org/request/show/877720 OBS-URL: https://build.opensuse.org/package/show/server:database/redis?expand=0&rev=169
README.SUSE ------------- Redis Server ============== 1. cp -a /etc/redis/default.conf.example /etc/redis/instancename.conf We use the "cp -a" here, so that our permissions are preserved. In case you copied the file with out the "-a" chown root:redis /etc/redis/instancename.conf chmod u=rw,g=r,o= /etc/redis/instancename.conf 2. change at least pidfile, logfile and dir setting # the pid file *has* to match your config filename without the ".conf" pidfile /var/run/redis/instancename.pid logfile /var/log/redis/instancename.log dir /var/lib/redis/instancename/ If you want to run more than one instance you also have to change the socket path and/or the ip:port combination. e.g. /var/run/redis/instancename.sock Also make sure if you copy configurations from somewhere, that "daemonize" should be set to "no". 3. create the database dir: $ install -d -o redis -g redis -m 0750 /var/lib/redis/instancename/ 4. systemctl start redis@instancename 5. systemctl enable redis@instancename 6. To stop/restart all instances at the same time use: systemctl restart redis.target systemctl stop redis.target Redis Sentinel ================ 1. cp -a /etc/redis/sentinel.conf.example /etc/redis/sentinel-instancename.conf We use the "cp -a" here, so that our permissions are preserved. In case you copied the file with out the "-a" chown root:redis /etc/redis/sentinel-instancename.conf chmod u=rw,g=rw,o= /etc/redis/sentinel-instancename.conf Please note that the sentinel config needs write permissions for the group. The chmod line differs from the line for the normal redis server. 2. change at least pidfile, logfile setting # the pid file *has* to match your config filename without the ".conf" pidfile /var/run/redis/instancename.pid logfile /var/log/redis/instancename.log If you want to run more than one instance you also have to change the socket path and/or the ip:port combination. e.g. /var/run/redis/instancename.sock Also make sure if you copy configurations from somewhere, that "daemonize" should be set to "no". 4. systemctl start redis-sentinel@instancename 5. systemctl enable redis-sentinel@instancename 6. To stop/restart all instances at the same time use: systemctl restart redis-sentinel.target systemctl stop redis-sentinel.target Integration with apache when using unix domain sockets ========================================================= If you plan to use redis in combination with apache, then you should add 'redis' to apache group and set 'unixsocketperm 770': $ usermod -a -G redis wwwrun $ systemctl restart apache2 then apache is able to connect to redis socket