1:C 25 Sep 2025 10:22:11.754 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 25 Sep 2025 10:22:11.754 # Redis version=6.2.19, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 25 Sep 2025 10:22:11.754 # 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 25 Sep 2025 10:22:11.754 * monotonic clock: POSIX clock_gettime
1:M 25 Sep 2025 10:22:11.755 * Running mode=standalone, port=6379.
1:M 25 Sep 2025 10:22:11.755 # Server initialized
1:M 25 Sep 2025 10:22:11.755 # 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 25 Sep 2025 10:22:11.756 * Loading RDB produced by version 6.2.19
1:M 25 Sep 2025 10:22:11.756 * RDB age 3 seconds
1:M 25 Sep 2025 10:22:11.756 * RDB memory usage when created 0.84 Mb
1:M 25 Sep 2025 10:22:11.756 # Done loading RDB, keys loaded: 2, keys expired: 0.
1:M 25 Sep 2025 10:22:11.756 * DB loaded from disk: 0.000 seconds
1:M 25 Sep 2025 10:22:11.756 * Ready to accept connections
1:M 25 Sep 2025 11:22:12.030 * 1 changes in 3600 seconds. Saving...
1:M 25 Sep 2025 11:22:12.034 * Background saving started by pid 20
20:C 25 Sep 2025 11:22:12.036 * DB saved on disk
20:C 25 Sep 2025 11:22:12.037 * RDB: 0 MB of memory used by copy-on-write
1:M 25 Sep 2025 11:22:12.135 * Background saving terminated with success
1:signal-handler (1758817060) Received SIGTERM scheduling shutdown...
1:M 25 Sep 2025 16:17:40.354 # User requested shutdown...
1:M 25 Sep 2025 16:17:40.354 * Saving the final RDB snapshot before exiting.
1:M 25 Sep 2025 16:17:40.355 * DB saved on disk
1:M 25 Sep 2025 16:17:40.355 # Redis is now ready to exit, bye bye...