1:C 22 Apr 2025 08:03:36.984 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 22 Apr 2025 08:03:36.985 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 22 Apr 2025 08:03:36.985 # 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 22 Apr 2025 08:03:36.985 * monotonic clock: POSIX clock_gettime
1:M 22 Apr 2025 08:03:36.987 * Running mode=standalone, port=6379.
1:M 22 Apr 2025 08:03:36.987 # Server initialized
1:M 22 Apr 2025 08:03:36.987 # 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 22 Apr 2025 08:03:36.987 * Loading RDB produced by version 6.2.17
1:M 22 Apr 2025 08:03:36.988 * RDB age 4 seconds
1:M 22 Apr 2025 08:03:36.988 * RDB memory usage when created 0.80 Mb
1:M 22 Apr 2025 08:03:36.988 # Done loading RDB, keys loaded: 2, keys expired: 0.
1:M 22 Apr 2025 08:03:36.988 * DB loaded from disk: 0.001 seconds
1:M 22 Apr 2025 08:03:36.988 * Ready to accept connections
1:M 22 Apr 2025 09:03:37.053 * 1 changes in 3600 seconds. Saving...
1:M 22 Apr 2025 09:03:37.056 * Background saving started by pid 20
20:C 22 Apr 2025 09:03:37.061 * DB saved on disk
20:C 22 Apr 2025 09:03:37.062 * RDB: 0 MB of memory used by copy-on-write
1:M 22 Apr 2025 09:03:37.157 * Background saving terminated with success
1:signal-handler (1745317525) Received SIGTERM scheduling shutdown...
1:M 22 Apr 2025 10:25:25.603 # User requested shutdown...
1:M 22 Apr 2025 10:25:25.603 * Saving the final RDB snapshot before exiting.
1:M 22 Apr 2025 10:25:25.608 * DB saved on disk
1:M 22 Apr 2025 10:25:25.608 # Redis is now ready to exit, bye bye...