1:C 20 Feb 2025 16:32:33.382 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 20 Feb 2025 16:32:33.382 # Redis version=6.2.14, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 20 Feb 2025 16:32:33.382 # 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 20 Feb 2025 16:32:33.382 * monotonic clock: POSIX clock_gettime
1:M 20 Feb 2025 16:32:33.383 * Running mode=standalone, port=6379.
1:M 20 Feb 2025 16:32:33.383 # Server initialized
1:M 20 Feb 2025 16:32:33.383 # 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 20 Feb 2025 16:32:33.383 * Loading RDB produced by version 6.2.14
1:M 20 Feb 2025 16:32:33.383 * RDB age 2 seconds
1:M 20 Feb 2025 16:32:33.383 * RDB memory usage when created 0.82 Mb
1:M 20 Feb 2025 16:32:33.383 # Done loading RDB, keys loaded: 2, keys expired: 0.
1:M 20 Feb 2025 16:32:33.383 * DB loaded from disk: 0.000 seconds
1:M 20 Feb 2025 16:32:33.383 * Ready to accept connections
1:M 20 Feb 2025 17:32:34.002 * 1 changes in 3600 seconds. Saving...
1:M 20 Feb 2025 17:32:34.006 * Background saving started by pid 20
20:C 20 Feb 2025 17:32:34.016 * DB saved on disk
20:C 20 Feb 2025 17:32:34.017 * RDB: 0 MB of memory used by copy-on-write
1:M 20 Feb 2025 17:32:34.106 * Background saving terminated with success
1:signal-handler (1740078490) Received SIGTERM scheduling shutdown...
1:M 20 Feb 2025 19:08:10.436 # User requested shutdown...
1:M 20 Feb 2025 19:08:10.436 * Saving the final RDB snapshot before exiting.
1:M 20 Feb 2025 19:08:10.441 * DB saved on disk
1:M 20 Feb 2025 19:08:10.441 # Redis is now ready to exit, bye bye...