uawdijnntqw1x1x1
IP : 216.73.216.214
Hostname : octopus.securecp.top
Kernel : Linux octopus.securecp.top 5.14.0-687.15.1.el9_8.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Jun 11 08:51:45 EDT 2026 x86_64
Disable Function : exec,system,passthru,shell_exec,proc_nice,proc_terminate,pfsockopen,dl,show_source,posix_kill,posix_mkfifo,posix_getpwuid,posix_setpgid,posix_setsid,posix_setuid,posix_setgid,posix_seteuid,posix_setegid,posix_uname,leak,apache_child_terminate
OS : Linux
PATH:
/
home
/
admiracreativos
/
wordpress-backups
/
..
/
.
/
.spamassassin
/
.
/
..
/
.clwpos
/
redis.log
/
/
3296066:C 29 Mar 2026 13:22:02.217 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 3296066:C 29 Mar 2026 13:22:02.217 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=3296066, just started 3296066:C 29 Mar 2026 13:22:02.217 # Configuration loaded 3296066:M 29 Mar 2026 13:22:02.218 # Server initialized 3296066:M 29 Mar 2026 13:22:02.218 # 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. 3754702:C 03 Apr 2026 03:41:27.352 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 3754702:C 03 Apr 2026 03:41:27.353 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=3754702, just started 3754702:C 03 Apr 2026 03:41:27.353 # Configuration loaded 3754702:M 03 Apr 2026 03:41:27.355 # Server initialized 3754702:M 03 Apr 2026 03:41:27.355 # 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. 3754702:signal-handler (1775562421) Received SIGTERM scheduling shutdown... 3754702:M 07 Apr 2026 11:47:01.802 # User requested shutdown... 3754702:M 07 Apr 2026 11:47:01.805 # Redis is now ready to exit, bye bye... 414157:C 07 Apr 2026 11:47:06.826 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 414157:C 07 Apr 2026 11:47:06.826 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=414157, just started 414157:C 07 Apr 2026 11:47:06.826 # Configuration loaded 414157:M 07 Apr 2026 11:47:06.827 # Server initialized 414157:M 07 Apr 2026 11:47:06.827 # 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. 4188493:C 15 Apr 2026 04:00:23.973 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 4188493:C 15 Apr 2026 04:00:23.973 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=4188493, just started 4188493:C 15 Apr 2026 04:00:23.973 # Configuration loaded 4188493:M 15 Apr 2026 04:00:23.974 # Server initialized 4188493:M 15 Apr 2026 04:00:23.975 # 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. 2913340:C 21 Apr 2026 07:02:33.730 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 2913340:C 21 Apr 2026 07:02:33.731 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=2913340, just started 2913340:C 21 Apr 2026 07:02:33.731 # Configuration loaded 2913340:M 21 Apr 2026 07:02:33.732 # Server initialized 2913340:M 21 Apr 2026 07:02:33.732 # 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. 3648854:C 22 Apr 2026 04:28:39.494 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 3648854:C 22 Apr 2026 04:28:39.494 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=3648854, just started 3648854:C 22 Apr 2026 04:28:39.494 # Configuration loaded 3648854:M 22 Apr 2026 04:28:39.495 # Server initialized 3648854:M 22 Apr 2026 04:28:39.495 # 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. 1664369:C 24 Apr 2026 18:09:48.971 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1664369:C 24 Apr 2026 18:09:48.971 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=1664369, just started 1664369:C 24 Apr 2026 18:09:48.972 # Configuration loaded 1664369:M 24 Apr 2026 18:09:48.973 # Server initialized 1664369:M 24 Apr 2026 18:09:48.973 # 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. 1664369:signal-handler (1777431684) Received SIGTERM scheduling shutdown... 1664369:M 29 Apr 2026 03:01:24.367 # User requested shutdown... 1664369:M 29 Apr 2026 03:01:24.375 # Redis is now ready to exit, bye bye... 1405399:C 29 Apr 2026 03:01:29.354 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1405399:C 29 Apr 2026 03:01:29.354 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=1405399, just started 1405399:C 29 Apr 2026 03:01:29.354 # Configuration loaded 1405399:M 29 Apr 2026 03:01:29.356 # Server initialized 1405399:M 29 Apr 2026 03:01:29.356 # 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. 2651:C 01 May 2026 03:40:49.249 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 2651:C 01 May 2026 03:40:49.249 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=2651, just started 2651:C 01 May 2026 03:40:49.249 # Configuration loaded 2651:M 01 May 2026 03:40:49.250 # Server initialized 2651:M 01 May 2026 03:40:49.250 # 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. 1070372:C 07 May 2026 03:38:40.838 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 1070372:C 07 May 2026 03:38:40.839 # Redis version=6.2.20, bits=64, commit=00000000, modified=0, pid=1070372, just started 1070372:C 07 May 2026 03:38:40.839 # Configuration loaded 1070372:M 07 May 2026 03:38:40.843 # Server initialized 1070372:M 07 May 2026 03:38:40.843 # 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. 1070372:signal-handler (1779446742) Received SIGTERM scheduling shutdown... 1070372:M 22 May 2026 10:45:42.875 # User requested shutdown... 1070372:M 22 May 2026 10:45:42.878 # Redis is now ready to exit, bye bye... 766145:C 22 May 2026 10:46:53.017 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 766145:C 22 May 2026 10:46:53.017 # Redis version=6.2.22, bits=64, commit=00000000, modified=0, pid=766145, just started 766145:C 22 May 2026 10:46:53.017 # Configuration loaded 766145:M 22 May 2026 10:46:53.018 # Server initialized 766145:M 22 May 2026 10:46:53.018 # 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. 766145:signal-handler (1780193297) Received SIGTERM scheduling shutdown... 766145:M 31 May 2026 02:08:17.778 # User requested shutdown... 766145:M 31 May 2026 02:08:17.780 # Redis is now ready to exit, bye bye... 3766349:C 31 May 2026 02:08:24.247 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 3766349:C 31 May 2026 02:08:24.247 # Redis version=6.2.22, bits=64, commit=00000000, modified=0, pid=3766349, just started 3766349:C 31 May 2026 02:08:24.248 # Configuration loaded 3766349:M 31 May 2026 02:08:24.249 # Server initialized 3766349:M 31 May 2026 02:08:24.249 # 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. 3824534:C 31 May 2026 02:18:43.180 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 3824534:C 31 May 2026 02:18:43.180 # Redis version=6.2.22, bits=64, commit=00000000, modified=0, pid=3824534, just started 3824534:C 31 May 2026 02:18:43.180 # Configuration loaded 3824534:M 31 May 2026 02:18:43.182 # Server initialized 3824534:M 31 May 2026 02:18:43.182 # 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. 318263:C 31 May 2026 23:55:30.085 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 318263:C 31 May 2026 23:55:30.085 # Redis version=6.2.22, bits=64, commit=00000000, modified=0, pid=318263, just started 318263:C 31 May 2026 23:55:30.085 # Configuration loaded 318263:M 31 May 2026 23:55:30.086 # Server initialized 318263:M 31 May 2026 23:55:30.086 # 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. 318263:signal-handler (1780479743) Received SIGTERM scheduling shutdown... 318263:M 03 Jun 2026 09:42:23.315 # User requested shutdown... 318263:M 03 Jun 2026 09:42:23.315 # Redis is now ready to exit, bye bye... 2407751:C 03 Jun 2026 09:42:29.614 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo 2407751:C 03 Jun 2026 09:42:29.614 # Redis version=6.2.22, bits=64, commit=00000000, modified=0, pid=2407751, just started 2407751:C 03 Jun 2026 09:42:29.614 # Configuration loaded 2407751:M 03 Jun 2026 09:42:29.615 # Server initialized 2407751:M 03 Jun 2026 09:42:29.615 # 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.
/home/admiracreativos/wordpress-backups/.././.spamassassin/./../.clwpos/redis.log