1:C 22 Jun 2026 11:59:56.247 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it 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:C 22 Jun 2026 11:59:56.247 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 22 Jun 2026 11:59:56.247 * Redis version=7.4.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 22 Jun 2026 11:59:56.247 * Configuration loaded
1:M 22 Jun 2026 11:59:56.248 * monotonic clock: POSIX clock_gettime
1:M 22 Jun 2026 11:59:56.252 * Running mode=standalone, port=6379.
1:M 22 Jun 2026 11:59:56.253 * Server initialized
1:M 22 Jun 2026 11:59:56.256 * Creating AOF base file appendonly.aof.1.base.rdb on server start
1:M 22 Jun 2026 11:59:56.264 * Creating AOF incr file appendonly.aof.1.incr.aof on server start
1:M 22 Jun 2026 11:59:56.264 * Ready to accept connections tcp
1:M 22 Jun 2026 12:04:57.032 * 100 changes in 300 seconds. Saving...
1:M 22 Jun 2026 12:04:57.037 * Background saving started by pid 72
72:C 22 Jun 2026 12:04:57.053 * DB saved on disk
72:C 22 Jun 2026 12:04:57.054 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 22 Jun 2026 12:04:57.139 * Background saving terminated with success
1:signal-handler (1782129948) Received SIGTERM scheduling shutdown...
1:M 22 Jun 2026 12:05:48.040 * User requested shutdown...
1:M 22 Jun 2026 12:05:48.040 * Calling fsync() on the AOF file.
1:M 22 Jun 2026 12:05:48.040 * Saving the final RDB snapshot before exiting.
1:M 22 Jun 2026 12:05:48.054 * DB saved on disk
1:M 22 Jun 2026 12:05:48.054 # Redis is now ready to exit, bye bye...
1:C 22 Jun 2026 12:05:48.909 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it 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:C 22 Jun 2026 12:05:48.909 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 22 Jun 2026 12:05:48.909 * Redis version=7.4.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 22 Jun 2026 12:05:48.909 * Configuration loaded
1:M 22 Jun 2026 12:05:48.909 * monotonic clock: POSIX clock_gettime
1:M 22 Jun 2026 12:05:48.912 * Running mode=standalone, port=6379.
1:M 22 Jun 2026 12:05:48.913 * Server initialized
1:M 22 Jun 2026 12:05:48.914 * Reading RDB base file on AOF loading...
1:M 22 Jun 2026 12:05:48.914 * Loading RDB produced by version 7.4.6
1:M 22 Jun 2026 12:05:48.914 * RDB age 352 seconds
1:M 22 Jun 2026 12:05:48.914 * RDB memory usage when created 0.90 Mb
1:M 22 Jun 2026 12:05:48.914 * RDB is base AOF
1:M 22 Jun 2026 12:05:48.914 * Done loading RDB, keys loaded: 0, keys expired: 0.
1:M 22 Jun 2026 12:05:48.915 * DB loaded from base file appendonly.aof.1.base.rdb: 0.002 seconds
1:M 22 Jun 2026 12:05:48.920 * DB loaded from incr file appendonly.aof.1.incr.aof: 0.004 seconds
1:M 22 Jun 2026 12:05:48.920 * DB loaded from append only file: 0.007 seconds
1:M 22 Jun 2026 12:05:48.920 * Opening AOF incr file appendonly.aof.1.incr.aof on server start
1:M 22 Jun 2026 12:05:48.920 * Ready to accept connections tcp
1:M 22 Jun 2026 12:10:49.082 * 100 changes in 300 seconds. Saving...
1:M 22 Jun 2026 12:10:49.083 * Background saving started by pid 74
74:C 22 Jun 2026 12:10:49.097 * DB saved on disk
74:C 22 Jun 2026 12:10:49.100 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 22 Jun 2026 12:10:49.185 * Background saving terminated with success