Hallo,
Since last update on Monday, the Redis Server keeps restarting with following message:
redis-server_1 | 7:C 11 Aug 2023 06:54:58.451 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
redis-server_1 | 7:C 11 Aug 2023 06:54:58.451 # Redis version=7.0.11, bits=64, commit=00000000, modified=0, pid=7, just started
redis-server_1 | 7:C 11 Aug 2023 06:54:58.451 # Configuration loaded
redis-server_1 | 7:M 11 Aug 2023 06:54:58.452 * monotonic clock: POSIX clock_gettime
redis-server_1 | 7:M 11 Aug 2023 06:54:58.454 * Running mode=standalone, port=0.
redis-server_1 | 7:M 11 Aug 2023 06:54:58.454 # Server initialized
redis-server_1 | 7:M 11 Aug 2023 06:54:58.455 # WARNING Your system is configured to use the ‘xen’ clocksource which might lead to degraded performance. Check the result of the [slow-clocksource] system check: run ‘redis-server --check-system’ to check if the system’s clocksource isn’t degrading performance.
redis-server_1 | 7:M 11 Aug 2023 06:54:58.455 # Fatal: Can’t initialize Background Jobs.
This seems to be the error to look for. What OS are you running the containers on?
You can find a discussion on the Redi GitHub page here. Perhaps a mismatch between Redis version and Docker. The instructions at the link should point you in the right direction or else there are other discussions on line regarding this Redis failure.
I’m having the same issue. I’m running on Ubuntu 22.04 and just did the standard apt update && apt dist-upgrade -y. Then updated all the docker images. When I look ate the redis logs it show a permissions error.
This is another issue and a solution is described here
Redis Server keeps restarting rm: cannot remove‘/run/redis/redis.sock’: Permission denied
Under some circumstances the Unix Domain Socket of the redis server has got wrong permissions. To fix this issue it is required to shutdown the redis-server and ospd-openvas containers and remove the redis_socket_voldocker volume. The volume can be removed safely because it gets re-created on the next startup.
I’ve upgrade the OS to Debian 11. Afterwards the Redis comes up as expected. It seems to be an incompatibility between the Docker Image an the underlining OS.