3067
MariaDBERRORNotableReplicationHIGH confidence
Replication channel does not exist
Production Risk
Medium — replication is not running for the intended channel.
What this means
An operation was attempted on a named replication channel that has not been created.
Why it happens
- 1Specifying a FOR CHANNEL clause with a channel name that does not exist.
- 2Mistyped channel name in START/STOP/RESET SLAVE … FOR CHANNEL.
How to reproduce
trigger — this will error
trigger — this will error
START SLAVE FOR CHANNEL 'nonexistent_channel';
expected output
ERROR 3067 (HY000): Channel 'nonexistent_channel' does not exist.
Fix 1
List existing channels and verify the name
List existing channels and verify the name
SELECT CHANNEL_NAME FROM performance_schema.replication_connection_status;
Why this works
Confirms which channels are configured.
Fix 2
Create the channel first via CHANGE MASTER TO
Create the channel first via CHANGE MASTER TO
CHANGE MASTER TO MASTER_HOST='host', MASTER_PORT=3306, MASTER_USER='repl', MASTER_PASSWORD='pass' FOR CHANNEL 'ch1';
Why this works
Registers the channel before starting replication.
What not to do
✕
Sources
Official documentation ↗
MySQL 8.0 — 3067 ER_CHANNEL_DOES_NOT_EXISTS2
Content generated with AI assistance and reviewed for accuracy. Found an error? hello@errcodes.dev