wordpress down

[girish]

@ghstandard If you go to Services, restart the redis there. Then go to WP and repair the app. Can you let me know if that works?

[ghstandard]

@girish Im unable to restart the redis in the services page. I increased the memory to 1gb, still nothing...

[girish]

@ghstandard what does it say in the redis logs?

[ghstandard]

Redis
Aug 12 15:25:21 51:M 12 Aug 2023 15:25:21.273 * RDB age 18 seconds
Aug 12 15:25:21 51:M 12 Aug 2023 15:25:21.273 * RDB memory usage when created 100.42 Mb
Aug 12 15:25:21 51:M 12 Aug 2023 15:25:21.631 * DB loaded from disk: 0.358 seconds
Aug 12 15:25:21 51:M 12 Aug 2023 15:25:21.631 * Ready to accept connections
Aug 12 15:25:22 2023-08-12 15:25:22,633 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 12 15:25:25 2023-08-12 15:25:25,260 INFO exited: redis (terminated by SIGKILL; not expected)
Aug 12 15:25:25 2023-08-12 15:25:25,365 INFO spawned: 'redis' with pid 59
Aug 12 15:25:25 59:C 12 Aug 2023 15:25:25.388 # Configuration loaded
Aug 12 15:25:25 59:C 12 Aug 2023 15:25:25.388 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=59, just started
Aug 12 15:25:25 59:C 12 Aug 2023 15:25:25.388 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 12 15:25:25 59:M 12 Aug 2023 15:25:25.391 # Server initialized
Aug 12 15:25:25 59:M 12 Aug 2023 15:25:25.391 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
Aug 12 15:25:25 59:M 12 Aug 2023 15:25:25.391 * Loading RDB produced by version 6.0.16
Aug 12 15:25:25 59:M 12 Aug 2023 15:25:25.391 * RDB age 22 seconds
Aug 12 15:25:25 59:M 12 Aug 2023 15:25:25.391 * RDB memory usage when created 100.42 Mb
Aug 12 15:25:25 59:M 12 Aug 2023 15:25:25.391 * Running mode=standalone, port=6379.
Aug 12 15:25:25 59:M 12 Aug 2023 15:25:25.750 * DB loaded from disk: 0.359 seconds
Aug 12 15:25:25 59:M 12 Aug 2023 15:25:25.750 * Ready to accept connections
Aug 12 15:25:25 [GET] /healthcheck
Aug 12 15:25:26 2023-08-12 15:25:26,752 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 12 15:25:29 2023-08-12 15:25:29,526 INFO exited: redis (terminated by SIGKILL; not expected)
Aug 12 15:25:29 2023-08-12 15:25:29,625 INFO spawned: 'redis' with pid 67
Aug 12 15:25:29 67:C 12 Aug 2023 15:25:29.646 # Configuration loaded
Aug 12 15:25:29 67:C 12 Aug 2023 15:25:29.646 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=67, just started
Aug 12 15:25:29 67:C 12 Aug 2023 15:25:29.646 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 12 15:25:29 67:M 12 Aug 2023 15:25:29.648 # Server initialized
Aug 12 15:25:29 67:M 12 Aug 2023 15:25:29.648 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
Aug 12 15:25:29 67:M 12 Aug 2023 15:25:29.648 * Loading RDB produced by version 6.0.16
Aug 12 15:25:29 67:M 12 Aug 2023 15:25:29.648 * RDB age 26 seconds
Aug 12 15:25:29 67:M 12 Aug 2023 15:25:29.648 * RDB memory usage when created 100.42 Mb
Aug 12 15:25:29 67:M 12 Aug 2023 15:25:29.648 * Running mode=standalone, port=6379.
Aug 12 15:25:29 67:M 12 Aug 2023 15:25:29.998 * DB loaded from disk: 0.350 seconds
Aug 12 15:25:29 67:M 12 Aug 2023 15:25:29.998 * Ready to accept connections
Aug 12 15:25:29 [GET] /healthcheck
Aug 12 15:25:31 2023-08-12 15:25:31,000 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 12 15:25:33 2023-08-12 15:25:33,770 INFO exited: redis (terminated by SIGKILL; not expected)
Aug 12 15:25:33 2023-08-12 15:25:33,889 INFO spawned: 'redis' with pid 75
Aug 12 15:25:33 75:C 12 Aug 2023 15:25:33.917 # Configuration loaded
Aug 12 15:25:33 75:C 12 Aug 2023 15:25:33.917 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=75, just started
Aug 12 15:25:33 75:C 12 Aug 2023 15:25:33.917 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 12 15:25:33 75:M 12 Aug 2023 15:25:33.920 # Server initialized
Aug 12 15:25:33 75:M 12 Aug 2023 15:25:33.920 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
Aug 12 15:25:33 75:M 12 Aug 2023 15:25:33.920 * Loading RDB produced by version 6.0.16
Aug 12 15:25:33 75:M 12 Aug 2023 15:25:33.920 * RDB age 30 seconds
Aug 12 15:25:33 75:M 12 Aug 2023 15:25:33.920 * RDB memory usage when created 100.42 Mb
Aug 12 15:25:33 75:M 12 Aug 2023 15:25:33.920 * Running mode=standalone, port=6379.
Aug 12 15:25:33 [GET] /healthcheck
Aug 12 15:25:34 75:M 12 Aug 2023 15:25:34.297 * DB loaded from disk: 0.376 seconds
Aug 12 15:25:34 75:M 12 Aug 2023 15:25:34.297 * Ready to accept connections
Aug 12 15:25:35 2023-08-12 15:25:35,299 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 12 15:25:37 [GET] /healthcheck
Aug 12 15:25:38 2023-08-12 15:25:38,075 INFO exited: redis (terminated by SIGKILL; not expected)
Aug 12 15:25:38 2023-08-12 15:25:38,189 INFO spawned: 'redis' with pid 83
Aug 12 15:25:38 83:C 12 Aug 2023 15:25:38.212 # Configuration loaded
Aug 12 15:25:38 83:C 12 Aug 2023 15:25:38.212 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=83, just started
Aug 12 15:25:38 83:C 12 Aug 2023 15:25:38.212 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 12 15:25:38 83:M 12 Aug 2023 15:25:38.214 # Server initialized
Aug 12 15:25:38 83:M 12 Aug 2023 15:25:38.214 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
Aug 12 15:25:38 83:M 12 Aug 2023 15:25:38.214 * Loading RDB produced by version 6.0.16
Aug 12 15:25:38 83:M 12 Aug 2023 15:25:38.214 * RDB age 35 seconds
Aug 12 15:25:38 83:M 12 Aug 2023 15:25:38.214 * RDB memory usage when created 100.42 Mb
Aug 12 15:25:38 83:M 12 Aug 2023 15:25:38.214 * Running mode=standalone, port=6379.
Aug 12 15:25:38 83:M 12 Aug 2023 15:25:38.594 * DB loaded from disk: 0.379 seconds
Aug 12 15:25:38 83:M 12 Aug 2023 15:25:38.594 * Ready to accept connections
Aug 12 15:25:39 2023-08-12 15:25:39,596 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 12 15:25:41 2023-08-12 15:25:41,566 INFO exited: redis (terminated by SIGKILL; not expected)
Aug 12 15:25:41 2023-08-12 15:25:41,575 INFO spawned: 'redis' with pid 91
Aug 12 15:25:41 91:C 12 Aug 2023 15:25:41.604 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 12 15:25:41 91:C 12 Aug 2023 15:25:41.605 # Configuration loaded
Aug 12 15:25:41 91:C 12 Aug 2023 15:25:41.605 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=91, just started
Aug 12 15:25:41 91:M 12 Aug 2023 15:25:41.607 # Server initialized
Aug 12 15:25:41 91:M 12 Aug 2023 15:25:41.607 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
Aug 12 15:25:41 91:M 12 Aug 2023 15:25:41.607 * Running mode=standalone, port=6379.
Aug 12 15:25:41 91:M 12 Aug 2023 15:25:41.608 * Loading RDB produced by version 6.0.16
Aug 12 15:25:41 91:M 12 Aug 2023 15:25:41.608 * RDB age 38 seconds
Aug 12 15:25:41 91:M 12 Aug 2023 15:25:41.608 * RDB memory usage when created 100.42 Mb
Aug 12 15:25:41 91:M 12 Aug 2023 15:25:41.994 * DB loaded from disk: 0.386 seconds
Aug 12 15:25:41 91:M 12 Aug 2023 15:25:41.994 * Ready to accept connections
Aug 12 15:25:41 [GET] /healthcheck
Aug 12 15:25:42 2023-08-12 15:25:42,997 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 12 15:25:45 2023-08-12 15:25:45,265 INFO exited: redis (terminated by SIGKILL; not expected)
Aug 12 15:25:45 2023-08-12 15:25:45,366 INFO spawned: 'redis' with pid 99
Aug 12 15:25:45 99:C 12 Aug 2023 15:25:45.387 # Configuration loaded
Aug 12 15:25:45 99:C 12 Aug 2023 15:25:45.387 # Redis version=6.0.16, bits=64, commit=00000000, modified=0, pid=99, just started
Aug 12 15:25:45 99:C 12 Aug 2023 15:25:45.387 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Aug 12 15:25:45 99:M 12 Aug 2023 15:25:45.389 # Server initialized
Aug 12 15:25:45 99:M 12 Aug 2023 15:25:45.389 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. 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.
Aug 12 15:25:45 99:M 12 Aug 2023 15:25:45.389 * Loading RDB produced by version 6.0.16
Aug 12 15:25:45 99:M 12 Aug 2023 15:25:45.389 * RDB age 42 seconds
Aug 12 15:25:45 99:M 12 Aug 2023 15:25:45.389 * RDB memory usage when created 100.42 Mb
Aug 12 15:25:45 99:M 12 Aug 2023 15:25:45.389 * Running mode=standalone, port=6379.
Aug 12 15:25:45 99:M 12 Aug 2023 15:25:45.747 * DB loaded from disk: 0.358 seconds
Aug 12 15:25:45 99:M 12 Aug 2023 15:25:45.747 * Ready to accept connections
Aug 12 15:25:45 [GET] /healthcheck
Aug 12 15:25:46 2023-08-12 15:25:46,749 INFO success: redis entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
Aug 12 15:25:49 Debug mode. Sleeping
Aug 12 15:26:04 Debug mode. Sleeping
Aug 12 15:28:11 Debug mode. Sleeping
Aug 12 15:38:26 Debug mode. Sleeping
Aug 12 15:38:36 Debug mode. Sleeping

[girish]

@ghstandard redis is in debug mode. if you click the edit button next to redis, there is a checkbox. Uncheck it to remove the recovery mode. It will start up after that.

[ghstandard]

I have, and the redis error is gone. But I am unable to restart the app.

[ghstandard]

Ah ... right... It's working now... Thanks

[p44]

I had same problem only on one Wp instance, after latest package update. I had to increase redis memory size, but I think problem should be more investigated

[girish]

The issue is that WordPress does not start if redis is down that is how the redis plugin is designed.

[p44]

@girish Thank's Girish