Debug Errors

Resolved

(@07stifler)

Hello, after redis works for a while, it disables itself, I think I made missing or incorrect installations, I am adding the log results that you may need, can you help me?

Diagnostics

Status: Not connected
Client: PhpRedis (v5.3.7)
Drop-in: Valid
Disabled: No
Ping: 1
Errors: [
    "READONLY You can't write against a read only replica."
]
PhpRedis: 5.3.7
Relay: Not loaded
Predis: Not loaded
Credis: Not loaded
PHP Version: 8.0.27
Plugin Version: 2.2.3
Redis Version: 7.0.7
Multisite: No
Metrics: Disabled
Metrics recorded: 0
Filesystem: Working
Global Prefix: "H4H7x_"
Blog Prefix: "H4H7x_"
WP_REDIS_PLUGIN_PATH: "/var/www/vhosts/alanyasmile.com/httpdocs/wp-content/plugins/redis-cache"
Global Groups: [
    "blog-details",
    "blog-id-cache",
    "blog-lookup",
    "global-posts",
    "networks",
    "rss",
    "sites",
    "site-details",
    "site-lookup",
    "site-options",
    "site-transient",
    "users",
    "useremail",
    "userlogins",
    "usermeta",
    "user_meta",
    "userslugs",
    "redis-cache",
    "blog_meta"
]
Ignored Groups: [
    "counts",
    "plugins",
    "themes",
    "blog-details",
    "blog-id-cache",
    "blog-lookup",
    "global-posts",
    "networks",
    "rss",
    "sites",
    "site-details",
    "site-lookup",
    "site-options",
    "site-transient",
    "users",
    "useremail",
    "userlogins",
    "usermeta",
    "user_meta",
    "userslugs",
    "redis-cache",
    "blog_meta",
    "wordfence",
    "wordfence-ls"
]
Unflushable Groups: []
Groups Types: {
    "blog-details": "ignored",
    "blog-id-cache": "ignored",
    "blog-lookup": "ignored",
    "global-posts": "ignored",
    "networks": "ignored",
    "rss": "ignored",
    "sites": "ignored",
    "site-details": "ignored",
    "site-lookup": "ignored",
    "site-options": "ignored",
    "site-transient": "ignored",
    "users": "ignored",
    "useremail": "ignored",
    "userlogins": "ignored",
    "usermeta": "ignored",
    "user_meta": "ignored",
    "userslugs": "ignored",
    "redis-cache": "ignored",
    "counts": "ignored",
    "plugins": "ignored",
    "themes": "ignored",
    "blog_meta": "ignored",
    "wordfence": "ignored",
    "wordfence-ls": "ignored"
}
Drop-ins: [
    "advanced-cache.php v by ",
    "maintenance.php v by ",
    "Redis Object Cache Drop-In v2.2.3 by Till Krüss"
]

Server Log

AH01071: Got error 'PHP message: RedisException: READONLY You can't write against a read only replica. in /var/www/vhosts/alanyasmile.com/httpdocs/wp-content/object-cache.php:1362\nStack trace:\n#0 /var/www/vhosts/alanyasmile.com/httpdocs/wp-content/object-cache.php(1362): Redis->set()\n#1 /var/www/vhosts/alanyasmile.com/httpdocs/wp-content/object-cache.php(1155): WP_Object_Cache->add_or_replace()\n#2 /var/www/vhosts/alanyasmile.com/httpdocs/wp-content/object-cache.php(63): WP_Object_Cache->add()\n#3 /var/www/vhosts/alanyasmile.com/httpdocs/wp-includes/option.php(333): wp_cache_add()\n#4 /var/www/vhosts/alanyasmile.com/httpdocs/wp-includes/functions.php(1766): wp_load_alloptions()\n#5 /var/www/vhosts/alanyasmile.com/httpdocs/wp-includes/load.php(771): is_blog_installed()\n#6 /var/www/vhosts/alanyasmile.com/httpdocs/wp-settings.php(160): wp_not_installed()\n#7 /var/www/vhosts/alanyasmile.com/httpdocs/wp-config.php(159): require_once('...')\n#8 /var/www/vhosts/alanyasmile.com/httpdocs/wp-load.php(50): require_once('...')\n#9 /var/www/vho...', referer: https://www.alanyasmile.com/wp-admin/options-general.php?page=redis-cache

and docker redis log

1:S 26 Jan 2023 14:26:19.525 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:19.525 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:19.563 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:22.290 * Master replied to PING, replication can continue...
1:S 26 Jan 2023 14:26:22.380 * Partial resynchronization not possible (no cached master)
1:S 26 Jan 2023 14:26:22.505 * Full resync from master: ZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZ:1
1:S 26 Jan 2023 14:26:22.505 * MASTER <-> REPLICA sync: receiving 54992 bytes from master to disk
1:S 26 Jan 2023 14:26:22.592 * MASTER <-> REPLICA sync: Flushing old data
1:S 26 Jan 2023 14:26:22.592 * MASTER <-> REPLICA sync: Loading DB in memory
1:S 26 Jan 2023 14:26:22.628 # Wrong signature trying to load DB from file
1:S 26 Jan 2023 14:26:22.628 # Failed trying to load the MASTER synchronization DB from disk: Invalid argument
1:S 26 Jan 2023 14:26:22.628 * Reconnecting to MASTER 194.40.243.206:8886 after failure
1:S 26 Jan 2023 14:26:22.628 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:22.682 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:24.299 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:24.299 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:24.551 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:24.552 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:24.606 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:25.929 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:25.929 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:26.563 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:26.563 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:26.604 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:27.778 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:27.778 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:28.573 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:28.573 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:28.611 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:29.643 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:29.643 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:30.582 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:30.583 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:30.641 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:32.380 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:32.380 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:32.591 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:32.591 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:32.632 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:34.324 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:34.324 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:34.600 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:34.600 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:34.641 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:36.324 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:36.324 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:36.609 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:36.609 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:36.649 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:37.510 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:37.510 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:37.614 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:37.614 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:37.652 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:38.595 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:38.595 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:38.617 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:38.618 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:38.657 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:40.465 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:40.465 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:40.625 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:40.625 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:40.665 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:41.879 # Failed to read response from the server: Success
1:S 26 Jan 2023 14:26:41.879 # Master did not respond to command during SYNC handshake
1:S 26 Jan 2023 14:26:42.634 * Connecting to MASTER 194.40.243.206:8886
1:S 26 Jan 2023 14:26:42.634 * MASTER <-> REPLICA sync started
1:S 26 Jan 2023 14:26:42.672 * Non blocking connect for SYNC fired the event.
1:S 26 Jan 2023 14:26:44.170 * Master replied to PING, replication can continue...
Close

The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)

Plugin Author Till Krüss
(@tillkruess)

3 years, 2 months ago

What kind of replication are you using, and did you configure Redis Object Cache to use replication?

Thread Starter 07stifler
(@07stifler)

3 years, 2 months ago

I have no idea about this, I just installed redis on docker in plesk and installed your plugin

Plugin Author Till Krüss
(@tillkruess)

3 years, 2 months ago

I’d suggest following a WordPress guide, using Redis replication is quite advanced.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Debug Errors’ is closed to new replies.