1:C 20 Mar 2025 23:34:19.328 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 20 Mar 2025 23:34:19.328 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 20 Mar 2025 23:34:19.328 # 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 20 Mar 2025 23:34:19.329 * monotonic clock: POSIX clock_gettime
1:M 20 Mar 2025 23:34:19.330 * Running mode=standalone, port=6379.
1:M 20 Mar 2025 23:34:19.330 # Server initialized
1:M 20 Mar 2025 23:34:19.330 # 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 20 Mar 2025 23:34:19.330 * Loading RDB produced by version 6.2.17
1:M 20 Mar 2025 23:34:19.330 * RDB age 3 seconds
1:M 20 Mar 2025 23:34:19.330 * RDB memory usage when created 0.80 Mb
1:M 20 Mar 2025 23:34:19.331 # Done loading RDB, keys loaded: 2, keys expired: 0.
1:M 20 Mar 2025 23:34:19.331 * DB loaded from disk: 0.000 seconds
1:M 20 Mar 2025 23:34:19.331 * Ready to accept connections
1:signal-handler (1742513715) Received SIGTERM scheduling shutdown...
1:M 20 Mar 2025 23:35:15.397 # User requested shutdown...
1:M 20 Mar 2025 23:35:15.398 * Saving the final RDB snapshot before exiting.
1:M 20 Mar 2025 23:35:15.402 * DB saved on disk
1:M 20 Mar 2025 23:35:15.403 # Redis is now ready to exit, bye bye...
1:C 20 Mar 2025 23:34:19.328 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 20 Mar 2025 23:34:19.328 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 20 Mar 2025 23:34:19.328 # 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 20 Mar 2025 23:34:19.329 * monotonic clock: POSIX clock_gettime
1:M 20 Mar 2025 23:34:19.330 * Running mode=standalone, port=6379.
1:M 20 Mar 2025 23:34:19.330 # Server initialized
1:M 20 Mar 2025 23:34:19.330 # 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 20 Mar 2025 23:34:19.330 * Loading RDB produced by version 6.2.17
1:M 20 Mar 2025 23:34:19.330 * RDB age 3 seconds
1:M 20 Mar 2025 23:34:19.330 * RDB memory usage when created 0.80 Mb
1:M 20 Mar 2025 23:34:19.331 # Done loading RDB, keys loaded: 2, keys expired: 0.
1:M 20 Mar 2025 23:34:19.331 * DB loaded from disk: 0.000 seconds
1:M 20 Mar 2025 23:34:19.331 * Ready to accept connections
1:signal-handler (1742513715) Received SIGTERM scheduling shutdown...
1:M 20 Mar 2025 23:35:15.397 # User requested shutdown...
1:M 20 Mar 2025 23:35:15.398 * Saving the final RDB snapshot before exiting.
1:M 20 Mar 2025 23:35:15.402 * DB saved on disk
1:M 20 Mar 2025 23:35:15.403 # Redis is now ready to exit, bye bye...
1:C 20 Mar 2025 23:35:15.859 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 20 Mar 2025 23:35:15.859 # Redis version=6.2.17, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 20 Mar 2025 23:35:15.859 # 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 20 Mar 2025 23:35:15.859 * monotonic clock: POSIX clock_gettime
1:M 20 Mar 2025 23:35:15.859 * Running mode=standalone, port=6379.
1:M 20 Mar 2025 23:35:15.859 # Server initialized
1:M 20 Mar 2025 23:35:15.859 # 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 20 Mar 2025 23:35:15.860 * Loading RDB produced by version 6.2.17
1:M 20 Mar 2025 23:35:15.860 * RDB age 0 seconds
1:M 20 Mar 2025 23:35:15.860 * RDB memory usage when created 1.00 Mb
1:M 20 Mar 2025 23:35:15.860 # Done loading RDB, keys loaded: 2, keys expired: 0.
1:M 20 Mar 2025 23:35:15.860 * DB loaded from disk: 0.000 seconds
1:M 20 Mar 2025 23:35:15.860 * Ready to accept connections
1:M 21 Mar 2025 00:35:16.061 * 1 changes in 3600 seconds. Saving...
1:M 21 Mar 2025 00:35:16.067 * Background saving started by pid 19
19:C 21 Mar 2025 00:35:16.072 * DB saved on disk
19:C 21 Mar 2025 00:35:16.072 * RDB: 0 MB of memory used by copy-on-write
1:M 21 Mar 2025 00:35:16.168 * Background saving terminated with success
1:signal-handler (1742544866) Received SIGTERM scheduling shutdown...
1:M 21 Mar 2025 08:14:26.819 # User requested shutdown...
1:M 21 Mar 2025 08:14:26.819 * Saving the final RDB snapshot before exiting.
1:M 21 Mar 2025 08:14:26.847 * DB saved on disk
1:M 21 Mar 2025 08:14:26.847 # Redis is now ready to exit, bye bye...