1:C 02 Feb 2026 16:13:29.383 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 02 Feb 2026 16:13:29.383 # Redis version=6.2.21, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 02 Feb 2026 16:13:29.383 # 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 02 Feb 2026 16:13:29.384 * monotonic clock: POSIX clock_gettime
1:M 02 Feb 2026 16:13:29.385 * Running mode=standalone, port=6379.
1:M 02 Feb 2026 16:13:29.385 # Server initialized
1:M 02 Feb 2026 16:13:29.385 # 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 02 Feb 2026 16:13:29.386 * Loading RDB produced by version 6.2.21
1:M 02 Feb 2026 16:13:29.386 * RDB age 4 seconds
1:M 02 Feb 2026 16:13:29.386 * RDB memory usage when created 1.04 Mb
1:M 02 Feb 2026 16:13:29.386 # Done loading RDB, keys loaded: 3, keys expired: 0.
1:M 02 Feb 2026 16:13:29.386 * DB loaded from disk: 0.000 seconds
1:M 02 Feb 2026 16:13:29.386 * Ready to accept connections
1:M 02 Feb 2026 16:33:47.325 * 100 changes in 300 seconds. Saving...
1:M 02 Feb 2026 16:33:47.330 * Background saving started by pid 20
20:C 02 Feb 2026 16:33:47.333 * DB saved on disk
20:C 02 Feb 2026 16:33:47.333 * RDB: 0 MB of memory used by copy-on-write
1:M 02 Feb 2026 16:33:47.430 * Background saving terminated with success
1:M 02 Feb 2026 16:38:48.043 * 100 changes in 300 seconds. Saving...
1:M 02 Feb 2026 16:38:48.043 * Background saving started by pid 21
21:C 02 Feb 2026 16:38:48.045 * DB saved on disk
21:C 02 Feb 2026 16:38:48.045 * RDB: 0 MB of memory used by copy-on-write
1:M 02 Feb 2026 16:38:48.144 * Background saving terminated with success
1:signal-handler (1770050776) Received SIGTERM scheduling shutdown...
1:M 02 Feb 2026 16:46:16.666 # User requested shutdown...
1:M 02 Feb 2026 16:46:16.666 * Saving the final RDB snapshot before exiting.
1:M 02 Feb 2026 16:46:16.680 * DB saved on disk
1:M 02 Feb 2026 16:46:16.680 # Redis is now ready to exit, bye bye...