Rafael HenglesOriginal post
Rank 2: Process
I just stopped and restarted my server. Now Redis is failing to start. I got the following from docker compose logs:
appwrite-redis | 1:C 14 Feb 2023 17:55:57.130 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
appwrite-redis | 1:C 14 Feb 2023 17:55:57.130 # Redis version=7.0.4, bits=64, commit=00000000, modified=0, pid=1, just started
appwrite-redis | 1:C 14 Feb 2023 17:55:57.130 # Configuration loaded
appwrite-redis | 1:M 14 Feb 2023 17:55:57.137 * monotonic clock: POSIX clock_gettime
appwrite-redis | 1:M 14 Feb 2023 17:55:57.145 * Running mode=standalone, port=6379.
appwrite-redis | 1:M 14 Feb 2023 17:55:57.145 # Server initialized
appwrite-redis | 1:M 14 Feb 2023 17:55:57.145 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
appwrite-redis | 1:M 14 Feb 2023 17:55:57.145 # 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.
appwrite-redis | 1:M 14 Feb 2023 17:55:57.147 # Wrong signature trying to load DB from file
appwrite-redis | 1:M 14 Feb 2023 17:55:57.147 # Fatal error loading the DB: Invalid argument. Exiting.
I also just upgraded my server from 2gb RAM to 4gb. Is there something I can do to reset the DB of Redis ?
Summary
The user is experiencing a fatal error while starting Redis after upgrading their server's RAM. They received the error "Fatal error loading the DB: Invalid argument. Exiting." The user also mentioned they restarted their server.
One solution suggested by another user is to reset all data by deleting the volumes using the command `docker compose down -v`.