Not Connected

  • Resolved creactivemind

    (@creactivemind)


    2 years, 3 months ago

    Overview

    Status:?Not connected

    Drop-in:?Valid

    Filesystem:?Writeable

    ————–

    Everything seems to work for some hours and then when I open it up a while later, I see the status is “not connected.”

    This happens usually a few hours after I installed Redis. (i have Redis working normally on the server)

    On the server, the port is 6379 to 6379 and the memory usage is unlimited. I doubt these have to do with the problem, because Redis works fine for the first several hours.

    I wonder why..

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Till Krüss

    (@tillkruess)

    Make sure Redis Server is running and can be access via PHP.

    Thread Starter creactivemind

    (@creactivemind)

    Yeah it is running, but I get this message in the log when it gets disconnected:



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

What could it mean?
    Plugin Author Till Krüss

    (@tillkruess)

    It seems you use master-replica replication, please consult your hosting company or developer about the Redis Server failure. We can’t assist with that, we only provide a WordPress plugin that allows WP to communicate with Redis.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Not Connected’ is closed to new replies.