Common SQL Errors

MySQL Error 2023: CR_PROBE_REPLICA_HOSTS - How to Fix and Prevent

Galaxy Team
August 5, 2025

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.

Sign up for the latest in common SQL errors from the Galaxy Team!
Welcome to the Galaxy, Guardian!
You'll be receiving a confirmation email

Follow us on twitter :)
Oops! Something went wrong while submitting the form.

What is MySQL error 2023 CR_PROBE_REPLICA_HOSTS?

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 Highlights

Typical Error Message

Error on SHOW REPLICA HOSTS: CR_PROBE_REPLICA_HOSTS was added in 8.0.33.

Error Type

Client Error

Language

MySQL

Symbol

CR_PROBE_REPLICA_HOSTS

Error Code

2023

SQL State

Explanation

Table of Contents

What is MySQL error 2023 (CR_PROBE_REPLICA_HOSTS)?<\/h2>

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>.

Common Causes

Related Errors

FAQs

Does upgrading only the server trigger error 2023?<\/h3>Yes. If the server is 8.0.33+ but the client is older, the new error code cannot be parsed and error 2023 appears.<\/p>

Can I keep using SHOW SLAVE HOSTS instead?<\/h3>SHOW SLAVE HOSTS is deprecated and removed in future versions. Upgrading the client to support SHOW REPLICA HOSTS is recommended.<\/p>

Is this a security issue?<\/h3>No. It is a compatibility warning. No data corruption or privilege escalation is involved.<\/p>

How does Galaxy help?<\/h3>Galaxy flags deprecated commands in real time and suggests modern syntax, reducing the chance of version-mismatch errors like 2023.<\/p>

Start Querying with the Modern SQL Editor Today!
Welcome to the Galaxy, Guardian!
You'll be receiving a confirmation email

Follow us on twitter :)
Oops! Something went wrong while submitting the form.

Check out some other errors

Trusted by top engineers on high-velocity teams
Aryeo Logo
Assort Health
Curri
Rubie Logo
Bauhealth Logo
Truvideo Logo