MySQL client error 2022 occurs when the client cannot retrieve replication information with SHOW REPLICA STATUS, often due to version mismatch, missing privileges, or the target server not acting as a replica.
MySQL Error 2022: CR_PROBE_REPLICA_STATUS appears when SHOW REPLICA STATUS fails because the server is not a replica, the user lacks REPLICATION CLIENT privilege, or client and server versions differ. Confirm the server’s replica role, grant privileges, or use SHOW SLAVE STATUS to fix the issue.
Error on SHOW REPLICA STATUS: CR_PROBE_REPLICA_STATUS was added in 8.0.33.
Error 2022 is a MySQL client-side error raised when the client library probes replication status and fails.
The accompanying message is “Error on SHOW REPLICA STATUS: CR_PROBE_REPLICA_STATUS was added in 8.0.33.”<\/p>
The error usually surfaces when you run SHOW REPLICA STATUS (or its alias SHOW SLAVE STATUS) against a server that is not configured as a replica or when the client cannot execute the statement due to permission or version problems.<\/p>
The client emits CR_PROBE_REPLICA_STATUS if the target server returns an empty result or an error to SHOW REPLICA STATUS.
This happens when the server is a primary, replication is disabled, or the user lacks REPLICATION CLIENT privilege.<\/p>
Version mismatches can also trigger the error. The client code that introduced CR_PROBE_REPLICA_STATUS first shipped in MySQL 8.0.33. Older servers or connectors do not recognize the probing logic, so they return an unexpected response.<\/p>
Identify whether the target instance is a replica. If it is not, run SHOW MASTER STATUS instead.
If the instance should be a replica, confirm that replica threads run and that the account has REPLICATION CLIENT privilege.<\/p>
When you use a pre-8.0.33 server, downgrade the client or upgrade the server so both sides share a compatible version. Alternatively, run SHOW SLAVE STATUS manually to bypass the probing routine.<\/p>
Scenario: A monitoring script upgraded to MySQL 8.0.33 queries a 5.7 replica.
Solution: Upgrade the replica to 8.0 or use an older client binary.<\/p>
Scenario: A read-only user without REPLICATION CLIENT tries SHOW REPLICA STATUS.
Solution: GRANT REPLICATION CLIENT ON *.* TO 'user'@'host';.<\/p>
Standardize client and server versions across environments, automate privilege grants for monitoring accounts, and monitor replication state via performance_schema tables when possible.<\/p>
Galaxy users can store version-checked queries and share endorsed replication probes, ensuring teams invoke the correct command in every environment.<\/p>
Error 1201: HY000 - Could not connect to source.
Resolve network reachability or credential issues and restart replication.<\/p>
Error 1198: Unknown target host. Verify CHANGE REPLICATION SOURCE TO parameters.<\/p>.
.avif)
.avif){kind=logo}
