114379:C 20 May 2025 13:12:19.270 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
114379:C 20 May 2025 13:12:19.271 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=114379, just started
114379:C 20 May 2025 13:12:19.271 # Configuration loaded
114379:M 20 May 2025 13:12:19.271 * Increased maximum number of open files to 10032 (it was originally set to 1024).
114379:M 20 May 2025 13:12:19.271 * monotonic clock: POSIX clock_gettime
114379:M 20 May 2025 13:12:19.272 * Running mode=standalone, port=13000.
114379:M 20 May 2025 13:12:19.272 # Server initialized
114379:M 20 May 2025 13:12:19.272 # 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.
114379:M 20 May 2025 13:12:19.281 * Ready to accept connections
114379:signal-handler (1747746746) Received SIGTERM scheduling shutdown...
114379:M 20 May 2025 13:12:26.468 # User requested shutdown...
114379:M 20 May 2025 13:12:26.468 * Removing the pid file.
114379:M 20 May 2025 13:12:26.469 # Redis is now ready to exit, bye bye...
114461:C 20 May 2025 13:12:27.520 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
114461:C 20 May 2025 13:12:27.520 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=114461, just started
114461:C 20 May 2025 13:12:27.520 # Configuration loaded
114461:M 20 May 2025 13:12:27.520 * Increased maximum number of open files to 10032 (it was originally set to 1024).
114461:M 20 May 2025 13:12:27.520 * monotonic clock: POSIX clock_gettime
114461:M 20 May 2025 13:12:27.521 * Running mode=standalone, port=13000.
114461:M 20 May 2025 13:12:27.521 # Server initialized
114461:M 20 May 2025 13:12:27.521 # 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.
114461:M 20 May 2025 13:12:27.526 * Ready to accept connections
114461:signal-handler (1747748097) Received SIGTERM scheduling shutdown...
114461:M 20 May 2025 13:34:57.477 # User requested shutdown...
114461:M 20 May 2025 13:34:57.477 * Removing the pid file.
114461:M 20 May 2025 13:34:57.477 # Redis is now ready to exit, bye bye...
121208:C 20 May 2025 13:34:58.000 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
121208:C 20 May 2025 13:34:58.000 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=121208, just started
121208:C 20 May 2025 13:34:58.000 # Configuration loaded
121208:M 20 May 2025 13:34:58.000 * Increased maximum number of open files to 10032 (it was originally set to 1024).
121208:M 20 May 2025 13:34:58.000 * monotonic clock: POSIX clock_gettime
121208:M 20 May 2025 13:34:58.007 * Running mode=standalone, port=13000.
121208:M 20 May 2025 13:34:58.007 # Server initialized
121208:M 20 May 2025 13:34:58.007 # 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.
121208:M 20 May 2025 13:34:58.007 * Ready to accept connections
121208:signal-handler (1747748105) Received SIGTERM scheduling shutdown...
121208:M 20 May 2025 13:35:05.573 # User requested shutdown...
121208:M 20 May 2025 13:35:05.573 * Removing the pid file.
121208:M 20 May 2025 13:35:05.573 # Redis is now ready to exit, bye bye...
121293:C 20 May 2025 13:35:06.652 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
121293:C 20 May 2025 13:35:06.652 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=121293, just started
121293:C 20 May 2025 13:35:06.652 # Configuration loaded
121293:M 20 May 2025 13:35:06.659 * Increased maximum number of open files to 10032 (it was originally set to 1024).
121293:M 20 May 2025 13:35:06.659 * monotonic clock: POSIX clock_gettime
121293:M 20 May 2025 13:35:06.660 * Running mode=standalone, port=13000.
121293:M 20 May 2025 13:35:06.660 # Server initialized
121293:M 20 May 2025 13:35:06.660 # 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.
121293:M 20 May 2025 13:35:06.663 * Ready to accept connections
121293:signal-handler (1747748635) Received SIGTERM scheduling shutdown...
121293:M 20 May 2025 13:43:55.450 # User requested shutdown...
121293:M 20 May 2025 13:43:55.450 * Removing the pid file.
121293:M 20 May 2025 13:43:55.451 # Redis is now ready to exit, bye bye...
122838:C 20 May 2025 13:43:55.667 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
122838:C 20 May 2025 13:43:55.667 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=122838, just started
122838:C 20 May 2025 13:43:55.667 # Configuration loaded
122838:M 20 May 2025 13:43:55.667 * Increased maximum number of open files to 10032 (it was originally set to 1024).
122838:M 20 May 2025 13:43:55.667 * monotonic clock: POSIX clock_gettime
122838:M 20 May 2025 13:43:55.668 * Running mode=standalone, port=13000.
122838:M 20 May 2025 13:43:55.668 # Server initialized
122838:M 20 May 2025 13:43:55.668 # 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.
122838:M 20 May 2025 13:43:55.668 * Ready to accept connections
122838:signal-handler (1747748831) Received SIGTERM scheduling shutdown...
122838:M 20 May 2025 13:47:11.527 # User requested shutdown...
122838:M 20 May 2025 13:47:11.528 * Removing the pid file.
122838:M 20 May 2025 13:47:11.528 # Redis is now ready to exit, bye bye...
925:C 20 May 2025 13:47:30.843 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
925:C 20 May 2025 13:47:30.843 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=925, just started
925:C 20 May 2025 13:47:30.843 # Configuration loaded
925:M 20 May 2025 13:47:30.844 * Increased maximum number of open files to 10032 (it was originally set to 1024).
925:M 20 May 2025 13:47:30.844 * monotonic clock: POSIX clock_gettime
925:M 20 May 2025 13:47:30.877 * Running mode=standalone, port=13000.
925:M 20 May 2025 13:47:30.877 # Server initialized
925:M 20 May 2025 13:47:30.877 # 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.
925:M 20 May 2025 13:47:30.877 * Ready to accept connections
925:signal-handler (1747751076) Received SIGTERM scheduling shutdown...
925:M 20 May 2025 14:24:36.923 # User requested shutdown...
925:M 20 May 2025 14:24:36.923 * Removing the pid file.
925:M 20 May 2025 14:24:36.923 # Redis is now ready to exit, bye bye...
3154:C 20 May 2025 14:24:38.234 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
3154:C 20 May 2025 14:24:38.234 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=3154, just started
3154:C 20 May 2025 14:24:38.234 # Configuration loaded
3154:M 20 May 2025 14:24:38.237 * Increased maximum number of open files to 10032 (it was originally set to 1024).
3154:M 20 May 2025 14:24:38.237 * monotonic clock: POSIX clock_gettime
3154:M 20 May 2025 14:24:38.238 * Running mode=standalone, port=13000.
3154:M 20 May 2025 14:24:38.238 # Server initialized
3154:M 20 May 2025 14:24:38.238 # 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.
3154:M 20 May 2025 14:24:38.238 * Ready to accept connections
3154:signal-handler (1748552830) Received SIGTERM scheduling shutdown...
3154:M 29 May 2025 21:07:10.113 # User requested shutdown...
3154:M 29 May 2025 21:07:10.113 * Removing the pid file.
3154:M 29 May 2025 21:07:10.113 # Redis is now ready to exit, bye bye...
76135:C 29 May 2025 21:07:10.367 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
76135:C 29 May 2025 21:07:10.367 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=76135, just started
76135:C 29 May 2025 21:07:10.367 # Configuration loaded
76135:M 29 May 2025 21:07:10.367 * Increased maximum number of open files to 10032 (it was originally set to 1024).
76135:M 29 May 2025 21:07:10.367 * monotonic clock: POSIX clock_gettime
76135:M 29 May 2025 21:07:10.375 * Running mode=standalone, port=13000.
76135:M 29 May 2025 21:07:10.375 # Server initialized
76135:M 29 May 2025 21:07:10.375 # 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.
76135:M 29 May 2025 21:07:10.376 * Ready to accept connections
76135:signal-handler (1748553149) Received SIGTERM scheduling shutdown...
76135:M 29 May 2025 21:12:29.217 # User requested shutdown...
76135:M 29 May 2025 21:12:29.217 * Removing the pid file.
76135:M 29 May 2025 21:12:29.217 # Redis is now ready to exit, bye bye...
76240:C 29 May 2025 21:12:29.563 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
76240:C 29 May 2025 21:12:29.563 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=76240, just started
76240:C 29 May 2025 21:12:29.563 # Configuration loaded
76240:M 29 May 2025 21:12:29.563 * Increased maximum number of open files to 10032 (it was originally set to 1024).
76240:M 29 May 2025 21:12:29.563 * monotonic clock: POSIX clock_gettime
76240:M 29 May 2025 21:12:29.564 * Running mode=standalone, port=13000.
76240:M 29 May 2025 21:12:29.564 # Server initialized
76240:M 29 May 2025 21:12:29.564 # 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.
76240:M 29 May 2025 21:12:29.568 * Ready to accept connections
76240:signal-handler (1749157706) Received SIGTERM scheduling shutdown...
76240:M 05 Jun 2025 21:08:26.962 # User requested shutdown...
76240:M 05 Jun 2025 21:08:26.962 * Removing the pid file.
76240:M 05 Jun 2025 21:08:26.962 # Redis is now ready to exit, bye bye...
912:C 05 Jun 2025 21:09:08.108 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
912:C 05 Jun 2025 21:09:08.108 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=912, just started
912:C 05 Jun 2025 21:09:08.108 # Configuration loaded
912:M 05 Jun 2025 21:09:08.113 * Increased maximum number of open files to 10032 (it was originally set to 1024).
912:M 05 Jun 2025 21:09:08.113 * monotonic clock: POSIX clock_gettime
912:M 05 Jun 2025 21:09:08.133 * Running mode=standalone, port=13000.
912:M 05 Jun 2025 21:09:08.134 # Server initialized
912:M 05 Jun 2025 21:09:08.134 # 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.
912:M 05 Jun 2025 21:09:08.139 * Ready to accept connections
912:signal-handler (1749623926) Received SIGTERM scheduling shutdown...
912:M 11 Jun 2025 06:38:46.714 # User requested shutdown...
912:M 11 Jun 2025 06:38:46.714 * Removing the pid file.
912:M 11 Jun 2025 06:38:46.714 # Redis is now ready to exit, bye bye...
51803:C 11 Jun 2025 06:38:48.029 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
51803:C 11 Jun 2025 06:38:48.029 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=51803, just started
51803:C 11 Jun 2025 06:38:48.029 # Configuration loaded
51803:M 11 Jun 2025 06:38:48.029 * Increased maximum number of open files to 10032 (it was originally set to 1024).
51803:M 11 Jun 2025 06:38:48.029 * monotonic clock: POSIX clock_gettime
51803:M 11 Jun 2025 06:38:48.030 * Running mode=standalone, port=13000.
51803:M 11 Jun 2025 06:38:48.030 # Server initialized
51803:M 11 Jun 2025 06:38:48.030 # 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.
51803:M 11 Jun 2025 06:38:48.035 * Ready to accept connections
51803:signal-handler (1750228021) Received SIGTERM scheduling shutdown...
51803:M 18 Jun 2025 06:27:01.740 # User requested shutdown...
51803:M 18 Jun 2025 06:27:01.740 * Removing the pid file.
51803:M 18 Jun 2025 06:27:01.740 # Redis is now ready to exit, bye bye...
106411:C 18 Jun 2025 06:27:03.037 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
106411:C 18 Jun 2025 06:27:03.037 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=106411, just started
106411:C 18 Jun 2025 06:27:03.037 # Configuration loaded
106411:M 18 Jun 2025 06:27:03.037 * Increased maximum number of open files to 10032 (it was originally set to 1024).
106411:M 18 Jun 2025 06:27:03.037 * monotonic clock: POSIX clock_gettime
106411:M 18 Jun 2025 06:27:03.040 * Running mode=standalone, port=13000.
106411:M 18 Jun 2025 06:27:03.040 # Server initialized
106411:M 18 Jun 2025 06:27:03.040 # 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.
106411:M 18 Jun 2025 06:27:03.041 * Ready to accept connections
106411:signal-handler (1750399669) Received SIGTERM scheduling shutdown...
106411:M 20 Jun 2025 06:07:49.859 # User requested shutdown...
106411:M 20 Jun 2025 06:07:49.859 * Removing the pid file.
106411:M 20 Jun 2025 06:07:49.859 # Redis is now ready to exit, bye bye...
122833:C 20 Jun 2025 06:07:51.157 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
122833:C 20 Jun 2025 06:07:51.157 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=122833, just started
122833:C 20 Jun 2025 06:07:51.157 # Configuration loaded
122833:M 20 Jun 2025 06:07:51.164 * Increased maximum number of open files to 10032 (it was originally set to 1024).
122833:M 20 Jun 2025 06:07:51.164 * monotonic clock: POSIX clock_gettime
122833:M 20 Jun 2025 06:07:51.165 * Running mode=standalone, port=13000.
122833:M 20 Jun 2025 06:07:51.165 # Server initialized
122833:M 20 Jun 2025 06:07:51.165 # 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.
122833:M 20 Jun 2025 06:07:51.169 * Ready to accept connections
122833:signal-handler (1752560194) Received SIGTERM scheduling shutdown...
122833:M 15 Jul 2025 06:16:34.448 # User requested shutdown...
122833:M 15 Jul 2025 06:16:34.448 * Removing the pid file.
122833:M 15 Jul 2025 06:16:34.449 # Redis is now ready to exit, bye bye...
347152:C 15 Jul 2025 06:16:35.858 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
347152:C 15 Jul 2025 06:16:35.858 # Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=347152, just started
347152:C 15 Jul 2025 06:16:35.858 # Configuration loaded
347152:M 15 Jul 2025 06:16:35.858 * Increased maximum number of open files to 10032 (it was originally set to 1024).
347152:M 15 Jul 2025 06:16:35.858 * monotonic clock: POSIX clock_gettime
347152:M 15 Jul 2025 06:16:35.859 * Running mode=standalone, port=13000.
347152:M 15 Jul 2025 06:16:35.859 # Server initialized
347152:M 15 Jul 2025 06:16:35.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.
347152:M 15 Jul 2025 06:16:35.866 * Ready to accept connections