1:C 24 Jan 2026 16:12:35.301 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 24 Jan 2026 16:12:35.301 # Redis version=6.2.21, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 24 Jan 2026 16:12:35.301 # 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 24 Jan 2026 16:12:35.301 * monotonic clock: POSIX clock_gettime
1:M 24 Jan 2026 16:12:35.302 * Running mode=standalone, port=6379.
1:M 24 Jan 2026 16:12:35.302 # Server initialized
1:M 24 Jan 2026 16:12:35.302 # 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 24 Jan 2026 16:12:35.303 * Loading RDB produced by version 6.2.21
1:M 24 Jan 2026 16:12:35.303 * RDB age 3 seconds
1:M 24 Jan 2026 16:12:35.303 * RDB memory usage when created 1.08 Mb
1:M 24 Jan 2026 16:12:35.303 # Done loading RDB, keys loaded: 3, keys expired: 0.
1:M 24 Jan 2026 16:12:35.303 * DB loaded from disk: 0.000 seconds
1:M 24 Jan 2026 16:12:35.303 * Ready to accept connections
1:M 24 Jan 2026 16:43:16.308 * 100 changes in 300 seconds. Saving...
1:M 24 Jan 2026 16:43:16.312 * Background saving started by pid 21
21:C 24 Jan 2026 16:43:16.320 * DB saved on disk
21:C 24 Jan 2026 16:43:16.321 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 16:43:16.412 * Background saving terminated with success
1:M 24 Jan 2026 16:53:25.501 * 100 changes in 300 seconds. Saving...
1:M 24 Jan 2026 16:53:25.502 * Background saving started by pid 22
22:C 24 Jan 2026 16:53:25.508 * DB saved on disk
22:C 24 Jan 2026 16:53:25.509 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 16:53:25.603 * Background saving terminated with success
1:M 24 Jan 2026 16:58:26.099 * 100 changes in 300 seconds. Saving...
1:M 24 Jan 2026 16:58:26.100 * Background saving started by pid 23
23:C 24 Jan 2026 16:58:26.101 * DB saved on disk
23:C 24 Jan 2026 16:58:26.102 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 16:58:26.200 * Background saving terminated with success
1:M 24 Jan 2026 17:16:29.203 * 100 changes in 300 seconds. Saving...
1:M 24 Jan 2026 17:16:29.204 * Background saving started by pid 24
24:C 24 Jan 2026 17:16:29.206 * DB saved on disk
24:C 24 Jan 2026 17:16:29.206 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 17:16:29.304 * Background saving terminated with success
1:M 24 Jan 2026 17:36:06.446 * 100 changes in 300 seconds. Saving...
1:M 24 Jan 2026 17:36:06.447 * Background saving started by pid 25
25:C 24 Jan 2026 17:36:06.449 * DB saved on disk
25:C 24 Jan 2026 17:36:06.449 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 17:36:06.548 * Background saving terminated with success
1:M 24 Jan 2026 17:55:33.196 * 100 changes in 300 seconds. Saving...
1:M 24 Jan 2026 17:55:33.197 * Background saving started by pid 26
26:C 24 Jan 2026 17:55:33.199 * DB saved on disk
26:C 24 Jan 2026 17:55:33.199 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 17:55:33.297 * Background saving terminated with success
1:M 24 Jan 2026 18:21:33.616 * 100 changes in 300 seconds. Saving...
1:M 24 Jan 2026 18:21:33.616 * Background saving started by pid 27
27:C 24 Jan 2026 18:21:33.618 * DB saved on disk
27:C 24 Jan 2026 18:21:33.619 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 18:21:33.717 * Background saving terminated with success
1:M 24 Jan 2026 19:21:34.092 * 1 changes in 3600 seconds. Saving...
1:M 24 Jan 2026 19:21:34.092 * Background saving started by pid 28
28:C 24 Jan 2026 19:21:34.094 * DB saved on disk
28:C 24 Jan 2026 19:21:34.095 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 19:21:34.193 * Background saving terminated with success
1:M 24 Jan 2026 20:39:02.512 * 1 changes in 3600 seconds. Saving...
1:M 24 Jan 2026 20:39:02.513 * Background saving started by pid 29
29:C 24 Jan 2026 20:39:02.515 * DB saved on disk
29:C 24 Jan 2026 20:39:02.516 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 20:39:02.613 * Background saving terminated with success
1:M 24 Jan 2026 21:39:03.097 * 1 changes in 3600 seconds. Saving...
1:M 24 Jan 2026 21:39:03.098 * Background saving started by pid 30
30:C 24 Jan 2026 21:39:03.099 * DB saved on disk
30:C 24 Jan 2026 21:39:03.100 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 21:39:03.198 * Background saving terminated with success
1:M 24 Jan 2026 22:39:04.047 * 1 changes in 3600 seconds. Saving...
1:M 24 Jan 2026 22:39:04.047 * Background saving started by pid 31
31:C 24 Jan 2026 22:39:04.049 * DB saved on disk
31:C 24 Jan 2026 22:39:04.049 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 22:39:04.148 * Background saving terminated with success
1:M 24 Jan 2026 23:39:05.099 * 1 changes in 3600 seconds. Saving...
1:M 24 Jan 2026 23:39:05.100 * Background saving started by pid 32
32:C 24 Jan 2026 23:39:05.102 * DB saved on disk
32:C 24 Jan 2026 23:39:05.102 * RDB: 0 MB of memory used by copy-on-write
1:M 24 Jan 2026 23:39:05.200 * Background saving terminated with success
1:signal-handler (1769300013) Received SIGTERM scheduling shutdown...
1:M 25 Jan 2026 00:13:34.012 # User requested shutdown...
1:M 25 Jan 2026 00:13:34.012 * Saving the final RDB snapshot before exiting.
1:M 25 Jan 2026 00:13:34.017 * DB saved on disk
1:M 25 Jan 2026 00:13:34.017 # Redis is now ready to exit, bye bye...