1:C 06 Nov 2025 19:22:03.485 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 06 Nov 2025 19:22:03.485 # Redis version=6.2.21, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 06 Nov 2025 19:22:03.485 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
1:M 06 Nov 2025 19:22:03.486 * monotonic clock: POSIX clock_gettime
1:M 06 Nov 2025 19:22:03.486 * Running mode=standalone, port=6379.
1:M 06 Nov 2025 19:22:03.486 # Server initialized
1:M 06 Nov 2025 19:22:03.486 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. 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.
1:M 06 Nov 2025 19:22:03.486 * Loading RDB produced by version 6.2.21
1:M 06 Nov 2025 19:22:03.486 * RDB age 3 seconds
1:M 06 Nov 2025 19:22:03.486 * RDB memory usage when created 0.86 Mb
1:M 06 Nov 2025 19:22:03.486 # Done loading RDB, keys loaded: 2, keys expired: 0.
1:M 06 Nov 2025 19:22:03.486 * DB loaded from disk: 0.000 seconds
1:M 06 Nov 2025 19:22:03.486 * Ready to accept connections
1:M 06 Nov 2025 20:22:04.095 * 1 changes in 3600 seconds. Saving...
1:M 06 Nov 2025 20:22:04.099 * Background saving started by pid 21
21:C 06 Nov 2025 20:22:04.103 * DB saved on disk
21:C 06 Nov 2025 20:22:04.104 * RDB: 0 MB of memory used by copy-on-write
1:M 06 Nov 2025 20:22:04.199 * Background saving terminated with success
1:signal-handler (1762474557) Received SIGTERM scheduling shutdown...
1:M 07 Nov 2025 00:15:57.566 # User requested shutdown...
1:M 07 Nov 2025 00:15:57.566 * Saving the final RDB snapshot before exiting.
1:M 07 Nov 2025 00:15:57.571 * DB saved on disk
1:M 07 Nov 2025 00:15:57.571 # Redis is now ready to exit, bye bye...