1:C 02 Jul 2026 18:36:35.023 # 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 02 Jul 2026 18:36:35.023 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 02 Jul 2026 18:36:35.023 * Redis version=7.4.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 02 Jul 2026 18:36:35.023 * Configuration loaded
1:M 02 Jul 2026 18:36:35.024 * monotonic clock: POSIX clock_gettime
1:M 02 Jul 2026 18:36:35.025 * Running mode=standalone, port=6379.
1:M 02 Jul 2026 18:36:35.025 * Server initialized
1:M 02 Jul 2026 18:36:35.029 * Creating AOF base file appendonly.aof.1.base.rdb on server start
1:M 02 Jul 2026 18:36:35.035 * Creating AOF incr file appendonly.aof.1.incr.aof on server start
1:M 02 Jul 2026 18:36:35.035 * Ready to accept connections tcp
1:M 02 Jul 2026 18:41:36.015 * 100 changes in 300 seconds. Saving...
1:M 02 Jul 2026 18:41:36.015 * Background saving started by pid 74
74:C 02 Jul 2026 18:41:36.025 * DB saved on disk
74:C 02 Jul 2026 18:41:36.026 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 02 Jul 2026 18:41:36.118 * Background saving terminated with success
1:signal-handler (1783017747) Received SIGTERM scheduling shutdown...
1:M 02 Jul 2026 18:42:27.131 * User requested shutdown...
1:M 02 Jul 2026 18:42:27.131 * Calling fsync() on the AOF file.
1:M 02 Jul 2026 18:42:27.131 * Saving the final RDB snapshot before exiting.
1:M 02 Jul 2026 18:42:27.138 * DB saved on disk
1:M 02 Jul 2026 18:42:27.138 # Redis is now ready to exit, bye bye...
1:C 02 Jul 2026 18:42:28.144 # 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 02 Jul 2026 18:42:28.145 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 02 Jul 2026 18:42:28.145 * Redis version=7.4.6, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 02 Jul 2026 18:42:28.145 * Configuration loaded
1:M 02 Jul 2026 18:42:28.146 * monotonic clock: POSIX clock_gettime
1:M 02 Jul 2026 18:42:28.148 * Running mode=standalone, port=6379.
1:M 02 Jul 2026 18:42:28.149 * Server initialized
1:M 02 Jul 2026 18:42:28.150 * Reading RDB base file on AOF loading...
1:M 02 Jul 2026 18:42:28.150 * Loading RDB produced by version 7.4.6
1:M 02 Jul 2026 18:42:28.151 * RDB age 353 seconds
1:M 02 Jul 2026 18:42:28.151 * RDB memory usage when created 0.90 Mb
1:M 02 Jul 2026 18:42:28.151 * RDB is base AOF
1:M 02 Jul 2026 18:42:28.151 * Done loading RDB, keys loaded: 0, keys expired: 0.
1:M 02 Jul 2026 18:42:28.154 * DB loaded from base file appendonly.aof.1.base.rdb: 0.004 seconds
1:M 02 Jul 2026 18:42:28.156 * DB loaded from incr file appendonly.aof.1.incr.aof: 0.002 seconds
1:M 02 Jul 2026 18:42:28.156 * DB loaded from append only file: 0.007 seconds
1:M 02 Jul 2026 18:42:28.156 * Opening AOF incr file appendonly.aof.1.incr.aof on server start
1:M 02 Jul 2026 18:42:28.156 * Ready to accept connections tcp
1:M 02 Jul 2026 18:47:29.096 * 100 changes in 300 seconds. Saving...
1:M 02 Jul 2026 18:47:29.097 * Background saving started by pid 75
75:C 02 Jul 2026 18:47:29.108 * DB saved on disk
75:C 02 Jul 2026 18:47:29.110 * Fork CoW for RDB: current 0 MB, peak 0 MB, average 0 MB
1:M 02 Jul 2026 18:47:29.198 * Background saving terminated with success