MySQL Bugs: #66916: Error creating master info: Error while checking replication metadata

Bug #66916	Error creating master info: Error while checking replication metadata
Submitted:	21 Sep 2012 18:05	Modified:	25 Feb 2013 17:10
Reporter:	Ernesto Rodriguez	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S1 (Critical)
Version:	5.6.6-m9.1	OS:	Windows (Server 2008 R2)
Assigned to:		CPU Architecture:	Any

Description:
new installation of mysqsl, try to setup master/master replication, but it fails.

see log:

120921 10:51:32 [Note] Plugin 'FEDERATED' is disabled.
120921 10:51:32 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
120921 10:51:32 InnoDB: The InnoDB memory heap is disabled
120921 10:51:32 InnoDB: Mutexes and rw_locks use Windows interlocked functions
120921 10:51:32 InnoDB: Compressed tables use zlib 1.2.3
120921 10:51:32 InnoDB: CPU does not support crc32 instructions
120921 10:51:32 InnoDB: Initializing buffer pool, size = 8.0M
120921 10:51:32 InnoDB: Completed initialization of buffer pool
120921 10:51:32 InnoDB: highest supported file format is Barracuda.
120921 10:51:32 InnoDB: 128 rollback segment(s) are active.
120921 10:51:32 InnoDB: Waiting for the background threads to start
120921 10:51:33 InnoDB: 1.2.6 started; log sequence number 1600086
120921 10:51:33 [Note] Server hostname (bind-address): '*'; port: 3306
120921 10:51:33 [Note] - '::' resolves to '::';
120921 10:51:33 [Note] Server socket created on IP: '::'.
120921 10:51:33 [Warning] InnoDB: Cannot open table mysql/slave_master_info from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
120921 10:51:33 [Warning] Info table is not ready to be used. Table 'mysql.slave_master_info' cannot be opened.
120921 10:51:33 [ERROR] Error creating master info: Error while checking replication metadata. This might also happen when doing a live upgrade from a version that did not make use of the replication metadata tables. If that was the case, consider finishing the upgrade before starting replication..
120921 10:51:33 [Note] Event Scheduler: Loaded 0 events
120921 10:51:33 [Note] C:\Program Files\MySQL\MySQL Server 5.6\bin\mysqld: ready for connections.
Version: '5.6.6-m9-log' socket: '' port: 3306 MySQL Community Server (GPL)

How to repeat:
initial setup is fine, but you can not setup replication. the sever is up but your get error about the master info creation, thus can not setup replication.

Please describe step by step how you tried to setup master/master. Thanks.

added to server 1 my.ini

# Binary Logging.
log-bin="MYSQLDEV02-bin"
server-id=1
auto_increment_increment=2
auto_increment_offset=1
relay-log="MYSQLDEV02-relay-bin"
relay-log-index="MYSQLDEV02-relay-bin.index"

added to server 2 my.ini

# Binary Logging.
log-bin="MYSQLDEV03-bin"
server-id=2
auto_increment_offset=2
auto_increment_increment=2
relay-log="MYSQLDEV03-relay-bin"
relay-log-index="MYSQLDEV03-relay-bin.index"

Restarted both server

ran CHANGE MASTER TO command and i get the following error:
  Master_host=***
  master_port=***
  Master_user=***
  Master_password=***
  master_log_file=***
  master_log_pos=**

ERROR 1794 (HY000): Slave is not configured or failed to initialize properly. Yo
u must at least set --server-id to enable either a master or a slave. Additional
 error messages can be found in the MySQL error log.

Thank you for the feedback. You provided the configuration files contents not the step by step you did. Thanks.

The attached step by step is what I used to create a mater-mater setup in mysql 5.5.27 and it works great.  However when I try to follow the same steps in 5.6.6 I get stuck on STEP 6b with the following error:

ERROR 1794 (HY000): Slave is not configured or failed to initialize properly. You must at least set --server-id to enable either a master or a slave. Additional error messages can be found in the MySQL error log.

I opted 5.6.6-m9-log as it has  MASTER_DELAY = 60 option. But stuck in the same issue. Please look into it. Thanks!!

I've tested bug#66916 for mysql 5.6.6, 5.6.8.
I couldn't reproduce the failure by steps described above.
I still think that the issue based on the missed or corrupted slave_master_info.ibd file.
If the reporter can provide more details for the bug report (my.cnf, fresh/upgrade installation, etc) I can try to find again.

Serge, we have similar cases in Bug#67179 and Bug#67595 caused by the Win installer copying .idb files around. 

It should be fixed in 5.6.10.

Thank you for the feedback.

Please read Erlend's comment and either wait when version 5.6.10 is released or copy datadir from *zip package.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".