The client-side error occurs when a tool tries to run SHOW SLAVE STATUS against a MySQL 8.0.32+ server, where the CR_PROBE_SLAVE_STATUS probe was removed.
MySQL Error 2022: CR_PROBE_SLAVE_STATUS appears when a client still probes replication status with SHOW SLAVE STATUS against MySQL 8.0.32 or later, where that command was deprecated. Upgrade your client or switch to SHOW REPLICA STATUS to resolve the issue.
Error on SHOW SLAVE STATUS: CR_PROBE_SLAVE_STATUS was removed after 8.0.32.
The error is returned by libmysql-client when it executes an internal probe named CR_PROBE_SLAVE_STATUS that no longer exists on servers from MySQL 8.0.32 onward.
The server removes the probe and responds with an unknown command, which surfaces as error 2022 on the client.
Developers typically meet this error after upgrading their MySQL server but continuing to use an older client, connector, or monitoring script that still relies on the legacy SHOW SLAVE STATUS statement.
The root cause is a mismatch between server and client capabilities. Starting in 8.0.22 MySQL replaced the term “slave” with “replica” and fully removed SHOW SLAVE STATUS in 8.0.32.
Older clients hard-code that call and trigger the CR_PROBE_SLAVE_STATUS probe, which the new server rejects.
In mixed-version environments, connection pools or health-check queries may still reference the outdated statement, immediately throwing the 2022 client error on connection startup.
Update the client library, connector, or GUI to a release compiled against libmysql 8.0.32 or later.
Modern clients issue SHOW REPLICA STATUS or query replication performance_schema tables instead of the removed command.
If you cannot upgrade the client immediately, redefine the health-check SQL to SHOW REPLICA STATUS or a lightweight SELECT 1 query and restart the application.
MySQL Router prior to 8.0.32 fails – upgrade Router to 8.1+ where replication probes have been renamed. Monitoring platforms like Percona PMM throw 2022 – update the agent or change the probe command.
Legacy PHP apps using mysqlnd – recompile against the latest MySQL Connector/C.
Keep client and server major versions aligned during upgrades. In CI pipelines, validate that SHOW REPLICA STATUS succeeds before promoting new images. Deprecate hardcoded SHOW SLAVE STATUS in codebases and move to INFORMATION_SCHEMA or performance_schema views for replication health.
Error 2026: CR_SERVER_LOST often follows if the client repeatedly retries the obsolete probe.
Error 2047: CR_PROTOCOL_ERROR may appear when packet parsing fails because of mixed versions. Updating the client library resolves these derivative errors as well.
.
MySQL replaced the terminology with SHOW REPLICA STATUS to remove offensive language and simplify replication commands.
No. From MySQL 8.0.32 the command is fully removed. Only upgrading clients or rewriting queries will work.
Galaxy’s linter flags deprecated SQL like SHOW SLAVE STATUS and suggests SHOW REPLICA STATUS before execution, preventing the error.
The error is client-side only and does not affect on-disk data, but it can break monitoring and fail health checks.
.avif)
.avif){kind=logo}
