[ad_1]
(I realized I asked the same question below in a reply: please ignore this one)
My Redis stops working after a few hours. My status is “not connected” in the Redis pluging settings. It was working fine until then.
I checked the Redis log in Plesk and I see this log
1:S 26 Dec 2022 07:18:40.476 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:41.019 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:41.525 * Master replied to PING, replication can continue...
1:S 26 Dec 2022 07:18:42.583 * Partial resynchronization not possible (no cached master)
1:S 26 Dec 2022 07:18:43.089 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:1
1:S 26 Dec 2022 07:18:43.090 * MASTER <-> REPLICA sync: receiving 55664 bytes from master to disk
1:S 26 Dec 2022 07:18:44.120 * MASTER <-> REPLICA sync: Flushing old data
1:S 26 Dec 2022 07:18:44.120 * MASTER <-> REPLICA sync: Loading DB in memory
1:S 26 Dec 2022 07:18:44.122 # Wrong signature trying to load DB from file
1:S 26 Dec 2022 07:18:44.122 # Failed trying to load the MASTER synchronization DB from disk: Invalid argument
1:S 26 Dec 2022 07:18:44.122 * Reconnecting to MASTER 185.246.90.205:8886 after failure
1:S 26 Dec 2022 07:18:44.122 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:44.609 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:45.279 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:18:45.279 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:18:45.500 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:18:45.500 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:47.001 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:47.504 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:18:47.504 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:18:47.508 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:18:47.508 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:47.985 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:48.503 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:18:48.503 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:18:48.512 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:18:48.512 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:49.001 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:49.500 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:18:49.500 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:18:49.517 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:18:49.517 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:51.083 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:51.584 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:18:51.584 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:18:52.527 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:18:52.527 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:53.029 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:53.533 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:18:53.533 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:18:54.534 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:18:54.535 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:55.108 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:55.606 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:18:55.606 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:18:56.542 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:18:56.542 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:57.053 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:18:57.600 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:18:57.600 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:18:58.549 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:18:58.549 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:18:59.054 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:19:00.791 # Failed to read response from the server: Success
1:S 26 Dec 2022 07:19:00.791 # Master did not respond to command during SYNC handshake
1:S 26 Dec 2022 07:19:01.559 * Connecting to MASTER 185.246.90.205:8886
1:S 26 Dec 2022 07:19:01.560 * MASTER <-> REPLICA sync started
1:S 26 Dec 2022 07:19:03.088 * Non blocking connect for SYNC fired the event.
1:S 26 Dec 2022 07:19:03.588 * Master replied to PING, replication can continue...
1:S 26 Dec 2022 07:19:04.634 * Partial resynchronization not possible (no cached master)
1:S 26 Dec 2022 07:19:05.344 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:1
1:S 26 Dec 2022 07:19:05.345 * MASTER <-> REPLICA sync: receiving 55664 bytes from master to disk
1:S 26 Dec 2022 07:19:07.577 * MASTER <-> REPLICA sync: Flushing old data
1:S 26 Dec 2022 07:19:07.577 * MASTER <-> REPLICA sync: Loading DB in memory
1:S 26 Dec 2022 07:19:07.578 # Wrong signature trying to load DB from file
1:S 26 Dec 2022 07:19:07.578 # Failed trying to load the MASTER synchronization DB from disk: Invalid argument
1:S 26 Dec 2022 07:19:07.578 * Reconnecting to MASTER 185.246.90.205:8886 after failure
Basically, it’s a repeat of the same message over and over. When it was working, I used to get this message.
1:C 26 Dec 2022 02:03:43.833 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 26 Dec 2022 02:03:43.833 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 26 Dec 2022 02:03:43.833 # 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 26 Dec 2022 02:03:43.833 * monotonic clock: POSIX clock_gettime
1:M 26 Dec 2022 02:03:43.835 * Running mode=standalone, port=6379.
1:M 26 Dec 2022 02:03:43.835 # Server initialized
1:M 26 Dec 2022 02:03:43.835 # 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 . 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 26 Dec 2022 02:03:43.835 * Ready to accept connections
1:signal-handler (1672020266) Received SIGTERM scheduling shutdown...
1:M 26 Dec 2022 02:04:26.775 # User requested shutdown...
1:M 26 Dec 2022 02:04:26.775 * Saving the final RDB snapshot before exiting.
1:M 26 Dec 2022 02:04:26.776 * DB saved on disk
1:M 26 Dec 2022 02:04:26.776 # Redis is now ready to exit, bye bye...
1:C 26 Dec 2022 02:04:27.301 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 26 Dec 2022 02:04:27.301 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 26 Dec 2022 02:04:27.301 # 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 26 Dec 2022 02:04:27.302 * monotonic clock: POSIX clock_gettime
1:M 26 Dec 2022 02:04:27.303 * Running mode=standalone, port=6379.
1:M 26 Dec 2022 02:04:27.303 # Server initialized
1:M 26 Dec 2022 02:04:27.303 # 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 . 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 26 Dec 2022 02:04:27.303 * Loading RDB produced by version 7.0.7
1:M 26 Dec 2022 02:04:27.303 * RDB age 1 seconds
1:M 26 Dec 2022 02:04:27.303 * RDB memory usage when created 0.87 Mb
1:M 26 Dec 2022 02:04:27.303 * Done loading RDB, keys loaded: 0, keys expired: 0.
1:M 26 Dec 2022 02:04:27.303 * DB loaded from disk: 0.000 seconds
1:M 26 Dec 2022 02:04:27.303 * Ready to accept connections
1:signal-handler (1672020388) Received SIGTERM scheduling shutdown...
1:M 26 Dec 2022 02:06:28.280 # User requested shutdown...
1:M 26 Dec 2022 02:06:28.280 * Saving the final RDB snapshot before exiting.
1:M 26 Dec 2022 02:06:28.281 * DB saved on disk
1:M 26 Dec 2022 02:06:28.281 # Redis is now ready to exit, bye bye...
1:C 26 Dec 2022 02:06:28.764 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 26 Dec 2022 02:06:28.764 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=1, just started
1:C 26 Dec 2022 02:06:28.764 # 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 26 Dec 2022 02:06:28.765 * monotonic clock: POSIX clock_gettime
1:M 26 Dec 2022 02:06:28.766 * Running mode=standalone, port=6379.
1:M 26 Dec 2022 02:06:28.766 # Server initialized
1:M 26 Dec 2022 02:06:28.766 # 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 . 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 26 Dec 2022 02:06:28.766 * Loading RDB produced by version 7.0.7
1:M 26 Dec 2022 02:06:28.766 * RDB age 0 seconds
1:M 26 Dec 2022 02:06:28.766 * RDB memory usage when created 0.85 Mb
1:M 26 Dec 2022 02:06:28.766 * Done loading RDB, keys loaded: 0, keys expired: 0.
1:M 26 Dec 2022 02:06:28.766 * DB loaded from disk: 0.000 seconds
1:M 26 Dec 2022 02:06:28.766 * Ready to accept connections
1:M 26 Dec 2022 02:08:17.935 * 10000 changes in 60 seconds. Saving...
1:M 26 Dec 2022 02:08:17.937 * Background saving started by pid 20
20:C 26 Dec 2022 02:08:18.035 * DB saved on disk
20:C 26 Dec 2022 02:08:18.036 * Fork CoW for RDB: current 2 MB, peak 2 MB, average 1 MB
1:M 26 Dec 2022 02:08:18.038 * Background saving terminated with success
1:M 26 Dec 2022 02:13:19.034 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:13:19.039 * Background saving started by pid 21
21:C 26 Dec 2022 02:13:19.161 * DB saved on disk
21:C 26 Dec 2022 02:13:19.162 * Fork CoW for RDB: current 2 MB, peak 2 MB, average 1 MB
1:M 26 Dec 2022 02:13:19.240 * Background saving terminated with success
1:M 26 Dec 2022 02:18:20.082 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:18:20.085 * Background saving started by pid 22
22:C 26 Dec 2022 02:18:20.331 * DB saved on disk
22:C 26 Dec 2022 02:18:20.332 * Fork CoW for RDB: current 4 MB, peak 4 MB, average 2 MB
1:M 26 Dec 2022 02:18:20.388 * Background saving terminated with success
1:M 26 Dec 2022 02:23:21.047 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:23:21.051 * Background saving started by pid 23
23:C 26 Dec 2022 02:23:21.372 * DB saved on disk
23:C 26 Dec 2022 02:23:21.374 * Fork CoW for RDB: current 3 MB, peak 3 MB, average 1 MB
1:M 26 Dec 2022 02:23:21.453 * Background saving terminated with success
1:M 26 Dec 2022 02:28:22.098 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:28:22.103 * Background saving started by pid 24
24:C 26 Dec 2022 02:28:22.482 * DB saved on disk
24:C 26 Dec 2022 02:28:22.484 * Fork CoW for RDB: current 3 MB, peak 3 MB, average 1 MB
1:M 26 Dec 2022 02:28:22.505 * Background saving terminated with success
1:M 26 Dec 2022 02:33:23.071 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:33:23.076 * Background saving started by pid 25
25:C 26 Dec 2022 02:33:23.550 * DB saved on disk
25:C 26 Dec 2022 02:33:23.551 * Fork CoW for RDB: current 2 MB, peak 2 MB, average 1 MB
1:M 26 Dec 2022 02:33:23.577 * Background saving terminated with success
1:M 26 Dec 2022 02:36:40.515 # Possible SECURITY ATTACK detected. It looks like somebody is sending POST or Host: commands to Redis. This is likely due to an attacker attempting to use Cross Protocol Scripting to compromise your Redis instance. Connection aborted.
1:M 26 Dec 2022 02:38:24.031 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:38:24.036 * Background saving started by pid 26
26:C 26 Dec 2022 02:38:24.563 * DB saved on disk
26:C 26 Dec 2022 02:38:24.565 * Fork CoW for RDB: current 3 MB, peak 3 MB, average 1 MB
1:M 26 Dec 2022 02:38:24.638 * Background saving terminated with success
1:M 26 Dec 2022 02:43:25.055 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:43:25.061 * Background saving started by pid 27
27:C 26 Dec 2022 02:43:25.625 * DB saved on disk
27:C 26 Dec 2022 02:43:25.627 * Fork CoW for RDB: current 3 MB, peak 3 MB, average 1 MB
1:M 26 Dec 2022 02:43:25.665 * Background saving terminated with success
1:M 26 Dec 2022 02:48:26.037 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:48:26.047 * Background saving started by pid 28
28:C 26 Dec 2022 02:48:26.662 * DB saved on disk
28:C 26 Dec 2022 02:48:26.663 * Fork CoW for RDB: current 4 MB, peak 4 MB, average 2 MB
1:M 26 Dec 2022 02:48:26.751 * Background saving terminated with success
1:M 26 Dec 2022 02:53:27.019 * 100 changes in 300 seconds. Saving...
1:M 26 Dec 2022 02:53:27.028 * Background saving started by pid 29
29:C 26 Dec 2022 02:53:27.712 * DB saved on disk
29:C 26 Dec 2022 02:53:27.715 * Fork CoW for RDB: current 3 MB, peak 3 MB, average 1 MB
1:M 26 Dec 2022 02:53:27.741 * Background saving terminated with success Would you be able to provide any insight on why Redis stops operating and gets disconnected after a while? I’d really love to get this pluging going… Thanks