640:C 03 Aug 2025 22:19:19.636 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
640:C 03 Aug 2025 22:19:19.637 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=640, just started
640:C 03 Aug 2025 22:19:19.637 # Configuration loaded
640:M 03 Aug 2025 22:19:19.637 * monotonic clock: POSIX clock_gettime
640:M 03 Aug 2025 22:19:19.638 * Running mode=standalone, port=6379.
640:M 03 Aug 2025 22:19:19.638 # Server initialized
640:M 03 Aug 2025 22:19:19.639 # 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.
640:M 03 Aug 2025 22:19:19.639 * Ready to accept connections
233:C 03 Aug 2025 22:25:09.559 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
233:C 03 Aug 2025 22:25:09.559 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=233, just started
233:C 03 Aug 2025 22:25:09.559 # Configuration loaded
233:M 03 Aug 2025 22:25:09.560 * monotonic clock: POSIX clock_gettime
233:M 03 Aug 2025 22:25:09.561 * Running mode=standalone, port=6379.
233:M 03 Aug 2025 22:25:09.561 # Server initialized
233:M 03 Aug 2025 22:25:09.561 # 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.
233:M 03 Aug 2025 22:25:09.562 * Ready to accept connections
233:C 03 Aug 2025 22:37:35.295 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
233:C 03 Aug 2025 22:37:35.295 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=233, just started
233:C 03 Aug 2025 22:37:35.295 # Configuration loaded
233:M 03 Aug 2025 22:37:35.296 * monotonic clock: POSIX clock_gettime
233:M 03 Aug 2025 22:37:35.296 * Running mode=standalone, port=6379.
233:M 03 Aug 2025 22:37:35.296 # Server initialized
233:M 03 Aug 2025 22:37:35.297 # 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.
233:M 03 Aug 2025 22:37:35.297 * Ready to accept connections
233:signal-handler (1754424826) Received SIGTERM scheduling shutdown...
233:M 05 Aug 2025 13:13:46.424 # User requested shutdown...
233:M 05 Aug 2025 13:13:46.425 * Saving the final RDB snapshot before exiting.
233:M 05 Aug 2025 13:13:46.426 * DB saved on disk
233:M 05 Aug 2025 13:13:46.427 * Removing the pid file.
233:M 05 Aug 2025 13:13:46.427 # Redis is now ready to exit, bye bye...
233:C 05 Aug 2025 13:13:50.774 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
233:C 05 Aug 2025 13:13:50.774 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=233, just started
233:C 05 Aug 2025 13:13:50.774 # Configuration loaded
233:M 05 Aug 2025 13:13:50.775 * monotonic clock: POSIX clock_gettime
233:M 05 Aug 2025 13:13:50.775 * Running mode=standalone, port=6379.
233:M 05 Aug 2025 13:13:50.776 # Server initialized
233:M 05 Aug 2025 13:13:50.776 # 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.
233:M 05 Aug 2025 13:13:50.777 * Loading RDB produced by version 7.0.15
233:M 05 Aug 2025 13:13:50.777 * RDB age 4 seconds
233:M 05 Aug 2025 13:13:50.777 * RDB memory usage when created 0.84 Mb
233:M 05 Aug 2025 13:13:50.777 * Done loading RDB, keys loaded: 0, keys expired: 0.
233:M 05 Aug 2025 13:13:50.778 * DB loaded from disk: 0.001 seconds
233:M 05 Aug 2025 13:13:50.778 * Ready to accept connections
233:signal-handler (1754426671) Received SIGTERM scheduling shutdown...
233:M 05 Aug 2025 13:44:31.441 # User requested shutdown...
233:M 05 Aug 2025 13:44:31.441 * Saving the final RDB snapshot before exiting.
233:M 05 Aug 2025 13:44:31.443 * DB saved on disk
233:M 05 Aug 2025 13:44:31.443 * Removing the pid file.
233:M 05 Aug 2025 13:44:31.443 # Redis is now ready to exit, bye bye...
645:C 05 Aug 2025 13:44:44.407 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
645:C 05 Aug 2025 13:44:44.407 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=645, just started
645:C 05 Aug 2025 13:44:44.407 # Configuration loaded
645:M 05 Aug 2025 13:44:44.408 * monotonic clock: POSIX clock_gettime
645:M 05 Aug 2025 13:44:44.408 * Running mode=standalone, port=6379.
645:M 05 Aug 2025 13:44:44.409 # Server initialized
645:M 05 Aug 2025 13:44:44.409 # 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.
645:M 05 Aug 2025 13:44:44.410 * Loading RDB produced by version 7.0.15
645:M 05 Aug 2025 13:44:44.410 * RDB age 13 seconds
645:M 05 Aug 2025 13:44:44.411 * RDB memory usage when created 0.84 Mb
645:M 05 Aug 2025 13:44:44.411 * Done loading RDB, keys loaded: 0, keys expired: 0.
645:M 05 Aug 2025 13:44:44.411 * DB loaded from disk: 0.001 seconds
645:M 05 Aug 2025 13:44:44.411 * Ready to accept connections
639:C 05 Aug 2025 13:46:37.737 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
639:C 05 Aug 2025 13:46:37.738 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=639, just started
639:C 05 Aug 2025 13:46:37.738 # Configuration loaded
639:M 05 Aug 2025 13:46:37.739 * monotonic clock: POSIX clock_gettime
639:M 05 Aug 2025 13:46:37.739 * Running mode=standalone, port=6379.
639:M 05 Aug 2025 13:46:37.740 # Server initialized
639:M 05 Aug 2025 13:46:37.740 # 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.
639:M 05 Aug 2025 13:46:37.741 * Loading RDB produced by version 7.0.15
639:M 05 Aug 2025 13:46:37.741 * RDB age 126 seconds
639:M 05 Aug 2025 13:46:37.741 * RDB memory usage when created 0.84 Mb
639:M 05 Aug 2025 13:46:37.742 * Done loading RDB, keys loaded: 0, keys expired: 0.
639:M 05 Aug 2025 13:46:37.742 * DB loaded from disk: 0.001 seconds
639:M 05 Aug 2025 13:46:37.742 * Ready to accept connections
639:signal-handler (1755990198) Received SIGTERM scheduling shutdown...
639:M 23 Aug 2025 16:03:18.428 # User requested shutdown...
639:M 23 Aug 2025 16:03:18.429 * Saving the final RDB snapshot before exiting.
639:M 23 Aug 2025 16:03:18.430 * DB saved on disk
639:M 23 Aug 2025 16:03:18.431 * Removing the pid file.
639:M 23 Aug 2025 16:03:18.431 # Redis is now ready to exit, bye bye...
639:C 23 Aug 2025 16:03:30.956 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
639:C 23 Aug 2025 16:03:30.957 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=639, just started
639:C 23 Aug 2025 16:03:30.957 # Configuration loaded
639:M 23 Aug 2025 16:03:30.957 * monotonic clock: POSIX clock_gettime
639:M 23 Aug 2025 16:03:30.958 * Running mode=standalone, port=6379.
639:M 23 Aug 2025 16:03:30.959 # Server initialized
639:M 23 Aug 2025 16:03:30.959 # 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.
639:M 23 Aug 2025 16:03:30.960 * Loading RDB produced by version 7.0.15
639:M 23 Aug 2025 16:03:30.960 * RDB age 12 seconds
639:M 23 Aug 2025 16:03:30.960 * RDB memory usage when created 0.84 Mb
639:M 23 Aug 2025 16:03:30.961 * Done loading RDB, keys loaded: 0, keys expired: 0.
639:M 23 Aug 2025 16:03:30.961 * DB loaded from disk: 0.001 seconds
639:M 23 Aug 2025 16:03:30.961 * Ready to accept connections