1:C 03 Apr 2026 16:14:03.363 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 03 Apr 2026 16:14:03.363 # Redis version=6.2.21, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 03 Apr 2026 16:14:03.363 # 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 03 Apr 2026 16:14:03.363 * monotonic clock: POSIX clock_gettime
1:M 03 Apr 2026 16:14:03.364 * Running mode=standalone, port=6379.
1:M 03 Apr 2026 16:14:03.364 # Server initialized
1:M 03 Apr 2026 16:14:03.364 # 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 03 Apr 2026 16:14:03.364 * Loading RDB produced by version 6.2.21
1:M 03 Apr 2026 16:14:03.364 * RDB age 3 seconds
1:M 03 Apr 2026 16:14:03.364 * RDB memory usage when created 1.02 Mb
1:M 03 Apr 2026 16:14:03.364 # Done loading RDB, keys loaded: 3, keys expired: 0.
1:M 03 Apr 2026 16:14:03.364 * DB loaded from disk: 0.000 seconds
1:M 03 Apr 2026 16:14:03.364 * Ready to accept connections
1:M 03 Apr 2026 16:56:13.490 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 16:56:13.495 * Background saving started by pid 21
21:C 03 Apr 2026 16:56:13.499 * DB saved on disk
21:C 03 Apr 2026 16:56:13.499 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 16:56:13.595 * Background saving terminated with success
1:M 03 Apr 2026 17:20:18.658 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 17:20:18.658 * Background saving started by pid 22
22:C 03 Apr 2026 17:20:18.660 * DB saved on disk
22:C 03 Apr 2026 17:20:18.661 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 17:20:18.758 * Background saving terminated with success
1:M 03 Apr 2026 18:20:19.041 * 1 changes in 3600 seconds. Saving...
1:M 03 Apr 2026 18:20:19.041 * Background saving started by pid 23
23:C 03 Apr 2026 18:20:19.043 * DB saved on disk
23:C 03 Apr 2026 18:20:19.044 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 18:20:19.142 * Background saving terminated with success
1:M 03 Apr 2026 19:08:23.040 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 19:08:23.041 * Background saving started by pid 24
24:C 03 Apr 2026 19:08:23.043 * DB saved on disk
24:C 03 Apr 2026 19:08:23.043 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 19:08:23.141 * Background saving terminated with success
1:M 03 Apr 2026 20:08:24.060 * 1 changes in 3600 seconds. Saving...
1:M 03 Apr 2026 20:08:24.060 * Background saving started by pid 25
25:C 03 Apr 2026 20:08:24.062 * DB saved on disk
25:C 03 Apr 2026 20:08:24.062 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 20:08:24.161 * Background saving terminated with success
1:M 03 Apr 2026 20:52:09.960 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 20:52:09.961 * Background saving started by pid 26
26:C 03 Apr 2026 20:52:09.963 * DB saved on disk
26:C 03 Apr 2026 20:52:09.963 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 20:52:10.061 * Background saving terminated with success
1:M 03 Apr 2026 21:12:04.152 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 21:12:04.153 * Background saving started by pid 27
27:C 03 Apr 2026 21:12:04.155 * DB saved on disk
27:C 03 Apr 2026 21:12:04.155 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 21:12:04.253 * Background saving terminated with success
1:M 03 Apr 2026 21:32:30.483 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 21:32:30.484 * Background saving started by pid 28
28:C 03 Apr 2026 21:32:30.486 * DB saved on disk
28:C 03 Apr 2026 21:32:30.486 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 21:32:30.584 * Background saving terminated with success
1:M 03 Apr 2026 21:56:58.669 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 21:56:58.670 * Background saving started by pid 29
29:C 03 Apr 2026 21:56:58.672 * DB saved on disk
29:C 03 Apr 2026 21:56:58.673 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 21:56:58.770 * Background saving terminated with success
1:M 03 Apr 2026 22:56:59.006 * 1 changes in 3600 seconds. Saving...
1:M 03 Apr 2026 22:56:59.006 * Background saving started by pid 30
30:C 03 Apr 2026 22:56:59.008 * DB saved on disk
30:C 03 Apr 2026 22:56:59.008 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 22:56:59.107 * Background saving terminated with success
1:M 03 Apr 2026 23:13:17.389 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 23:13:17.390 * Background saving started by pid 31
31:C 03 Apr 2026 23:13:17.392 * DB saved on disk
31:C 03 Apr 2026 23:13:17.392 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 23:13:17.490 * Background saving terminated with success
1:M 03 Apr 2026 23:44:51.478 * 100 changes in 300 seconds. Saving...
1:M 03 Apr 2026 23:44:51.479 * Background saving started by pid 32
32:C 03 Apr 2026 23:44:51.481 * DB saved on disk
32:C 03 Apr 2026 23:44:51.482 * RDB: 0 MB of memory used by copy-on-write
1:M 03 Apr 2026 23:44:51.580 * Background saving terminated with success
1:signal-handler (1775261654) Received SIGTERM scheduling shutdown...
1:M 04 Apr 2026 00:14:14.163 # User requested shutdown...
1:M 04 Apr 2026 00:14:14.163 * Saving the final RDB snapshot before exiting.
1:M 04 Apr 2026 00:14:14.164 * DB saved on disk
1:M 04 Apr 2026 00:14:14.164 # Redis is now ready to exit, bye bye...