MySQL error 2023 (CR_PROBE_REPLICA_HOSTS) appears when a client or connector that predates MySQL 8.0.33 tries to run SHOW REPLICA HOSTS and receives an unknown client-side error code.
MySQL Error 2023: CR_PROBE_REPLICA_HOSTS is a client-side compatibility error raised when an outdated MySQL client calls SHOW REPLICA HOSTS against a server version 8.0.33 or later. Upgrade the client library or switch to a supported query to resolve the issue.
Error on SHOW REPLICA HOSTS: CR_PROBE_REPLICA_HOSTS was added in 8.0.33.
Error 2023 with condition name CR_PROBE_REPLICA_HOSTS is thrown by the MySQL client library when it receives an error code that was only added in MySQL 8.0.33.<\/p>
The message usually appears as: Error on SHOW REPLICA HOSTS: CR_PROBE_REPLICA_HOSTS was added in 8.0.33.<\/code> It signals that the client or connector does not understand the newer error enumeration returned by the server.<\/p>
What Causes This Error?<\/h3>
Version mismatch between the MySQL server (8.0.33+) and an older client library is the primary cause.
The outdated client cannot map the new error code to a known symbol.<\/p>
Running SHOW REPLICA HOSTS<\/code> on a server that disabled or removed legacy SHOW SLAVE HOSTS<\/code> can also surface the error if the client lacks updated metadata support.<\/p>
How to Fix MySQL Error 2023: CR_PROBE_REPLICA_HOSTS<\/h3>
Upgrade the MySQL client, connector, or driver to version 8.0.33 or later so it recognizes the new error constants.<\/p>
If an upgrade is impossible, avoid the affected statement by querying performance_schema.replication_group_members<\/code> or other metadata tables instead of SHOW REPLICA HOSTS<\/code>.<\/p>
Common Scenarios and Solutions<\/h3>
CI pipelines running MySQL 5.7 client binaries against an 8.0.34 server frequently hit this error.
Container images should pin both client and server to the same major.minor version.<\/p>
Language drivers (Python mysqlclient, Node mysql2) compiled against libmysqlclient 8.0.32 will also fail. Reinstall the driver after updating the system MySQL libraries.<\/p>
Best Practices to Avoid This Error<\/h3>
Always match client and server minor versions in production. Automate compatibility checks in your deployment scripts.<\/p>
Use Galaxy collections to document approved client versions.
Galaxy AI copilot can detect deprecated commands and suggest modern equivalents, preventing the mismatch early.<\/p>
Related Errors and Solutions<\/h3>
Error 2059 (CR_AUTH_PLUGIN_ERR) occurs during mismatched authentication plugins. The fix is similar: upgrade the client or enable the required plugin.<\/p>
Error 2055 (CR_SERVER_LOST) signals a dropped connection, often after issuing an unsupported command. Matching client and server versions reduces both issues.<\/p>.