<p>The server refuses to start replication because GTID auto positioning is enabled but file-position parameters are also supplied.</p>
<p>MySQL Error 1776: ER_BAD_SLAVE_AUTO_POSITION occurs when MASTER_LOG_FILE or MASTER_LOG_POS is issued while MASTER_AUTO_POSITION = 1. Remove the file/position options or disable auto position to restart replication successfully.</p>
Parameters MASTER_LOG_FILE, MASTER_LOG_POS,
MySQL error 1776 shows the message "Parameters MASTER_LOG_FILE, MASTER_LOG_POS, RELAY_LOG_FILE and RELAY_LOG_POS cannot be set when MASTER_AUTO_POSITION is active." It appears when a replica uses GTID auto positioning yet the CHANGE MASTER statement also specifies manual coordinates.
MySQL blocks this unsafe mixture to protect replication integrity. Fixing the configuration quickly restores data flow and prevents relay log corruption.
The error fires when MASTER_AUTO_POSITION = 1 is present together with any *_LOG_FILE or *_LOG_POS option. It is common during migrations from classic replication, when scripts reuse old parameters, or when an administrator adds coordinates by habit.
Inconsistent GTID settings between primary and replica or partial resets that leave stale variables can also trigger the conflict.
Stop the replica, clear conflicting coordinates, and rely solely on GTID. Use CHANGE MASTER TO ... MASTER_AUTO_POSITION = 1 without file or position values, then start replication.
If file based replication is preferred, first set MASTER_AUTO_POSITION = 0, then supply MASTER_LOG_FILE and MASTER_LOG_POS.
GTID migration scripts: delete MASTER_LOG_FILE and MASTER_LOG_POS lines, keep MASTER_AUTO_POSITION = 1.
Existing replica repair: STOP REPLICA; RESET SLAVE ALL; reissue CHANGE MASTER with only GTID settings; START REPLICA; verify with SHOW REPLICA STATUS.
Maintain separate templates for GTID and legacy replication. Validate CHANGE MASTER commands in CI pipelines.
Monitor for code 1776 in error logs and alert. Version control replication scripts in Galaxy so peers catch conflicting parameters before deployment.
Error 1732 (ER_SLAVE_CONFIGURATION): occurs when GTID_MODE differs; align GTID_MODE on both servers.
Error 1236 (ER_MASTER_FATAL_ERROR_READING_BINLOG): indicates the replica cannot read the master binlog; check file presence and network.
Specifying MASTER_LOG_FILE or MASTER_LOG_POS while MASTER_AUTO_POSITION = 1 causes an immediate conflict.
Old deployment scripts inject file coordinates even after GTID adoption, triggering error 1776.
MASTER_AUTO_POSITION is enabled but stale relay log settings remain.
DBAs sometimes append LOG_FILE and LOG_POS options out of habit during interactive sessions.
Raised when GTID_MODE differs between master and replica. Align GTID settings.
Occurs when the replica cannot read the specified binary log. Verify log existence and network connectivity.
Appears when auto position is requested while GTID_MODE is OFF. Enable GTID_MODE or disable auto position.
No. MySQL requires choosing one method per connection. Mixing parameters triggers error 1776.
No. Replication will not start until the conflict is resolved.
Any version with GTID support, including 5.6, 5.7, and 8.0.
Galaxy versions replication scripts and surfaces conflicting parameters during code review, reducing configuration drift.
.avif)
.avif){kind=logo}
