Error Failed To Initialize The Master Info Structure
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About
Error Reading Master Configuration
Us Learn more about Stack Overflow the company Business Learn more about hiring error counting relay log space developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the failed to open the relay log Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Error: “could not initailize master
Could Not Find Target Log During Relay Log Initialization
info structure” while doing Master Slave Replication in MySQL up vote 26 down vote favorite 6 I am trying to do Master Slave Replication for MySQL. When i am typing the following command: CHANGE MASTER TO MASTER_HOST='10.1.100.1', MASTER_USER='slave_user', MASTER_PASSWORD='slave_password', MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=451228; mysql> START SLAVE; it throws the following error: ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the
Error 1202
MySQL error log Any help would be greatly appreciated. mysql replication master slave share|improve this question edited Feb 17 '11 at 20:51 Vijay Dev 9,211145388 asked Feb 17 '11 at 13:22 user619684 131123 add a comment| 2 Answers 2 active oldest votes up vote 89 down vote TRY TO RESET IT, IT DOES MAGIC! ON SLAVE THE SLAVE MYSQL COMMAND TYPE: RESET SLAVE; THEN TRY AGAIN: CHANGE MASTER TO MASTER_HOST='10.1.100.1', MASTER_USER='slave_user', MASTER_PASSWORD='slave_password', MASTER_LOG_FILE='mysql-bin.000001', MASTER_LOG_POS=451228; mysql> START SLAVE; share|improve this answer answered Mar 29 '12 at 21:10 Neo 4,70913655 1 thanks a lot, had same problem here... –eran Nov 12 '12 at 16:15 1 Thanks a lot. This worked for me :D Power! (y) hehe –marknt15 May 15 '14 at 7:13 2 Worked for me. This blew my mind. –Logan Bissonnette May 28 '14 at 20:51 2 This is the solution, in my case in happened after doing start slave with a wrong server_id in the slave, stop and start did not work before doing reset. –danigosa Oct 8 '14 at 11:49 awesome man !!! –Pankaj Katiyar Aug 10 at 12:57 add a comment| up vote 4 down vote Please check
created relay files in /var/run/mysqld/ which filled up the whole of the partition and got fatal error 1236 from master when reading data from binary log caused errors in the logs. To repair the problem
Change Master To
i ran {{{RESET MASTER}}} on the master db server and removed the relay files from could not find first log file name in binary log index file the slave. This didn't have the desired affect. >Start slave; "Error reading slave log configuration" I then banged my head against the wall. A http://stackoverflow.com/questions/5029485/error-could-not-initailize-master-info-structure-while-doing-master-slave-rep blog documented a similar problem whereby the files master.info and relay-bin.info were both empty. And to delete them Gung-Ho I deleted the following sudo rm /var/lib/mysql/relay-log.info sudo rm /var/lib/mysql/master.info sudo rm /var/runmysqld/* Restarted slave and everything was back to normal.... apart from the data loss. See Mysqldump and restore http://perplexed.co.uk/301_restoring_a_broken_slave.htm slave from master using bash Handling other Errors Error "ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the MySQL error log" I opened the syslog where the message said >sudo less /var/log/syslog [ERROR] Failed to open the relay log '/var/run/mysqld/mysqld-relay-bin.000040' (relay_log_pos 202987) I opened up the relay-log.info file >sudo nano /var/lib/mysql/relay-log.info /var/run/mysqld/mysqld-relay-bin.000040 ... In the directory /var/run/mysqld/ and the mysql directory log file mysqld-relay-bin.index there were only three files mentioned, which did not include mysqld-relay-bin.000040. I deleted the the relay-log.info file sudo rm /var/lib/mysql/relay-log.info And restarted mysql slave successfully. Error: "Slave_IO_Running: No" I got this another day mysql> SHOW SLAVE STATUS\G ... Slave_IO_Running: No Slave_SQL_Running: Yes ... The log file defined in "my.cnf" err-log=/data/logs/mysqld/mysqld.log Looking in err-log=/data/logs/mysqld/mysqld.log contained the following lines. 080718 10:35:34 [Note] Slave I/O thread: connected to master 'replicateuser@1.2.3.4:3306', replication started in log 'db1-bin.
into a little issue setting up a MySQL slave. I have done this a least a have dozen times http://dev.nuclearrooster.com/2009/03/06/relay-log-issues-when-starting-mysql-replication-slave/ before, and it is always pretty painless, but this time, http://serverfault.com/questions/715849/hard-reboot-causes-mysql-replication-to-break I kept getting hung up on error that looked like this: 071118 16:44:10 [ERROR] Failed to open the relay log './-relay-bin.003525' (relay_log_pos 22940879) 071118 16:44:10 [ERROR] Could not find target log during relay log initialization 071118 16:44:10 [ERROR] Failed to initialize the relay log master info structure Googling a little turned up this mysql forum, http://forums.mysql.com/read.php?26,112490,223025#msg-223025 Which then led me to this mysql doc page http://dev.mysql.com/doc/refman/5.0/en/replication-howto-additionalslaves.html This was confusing, and didn't really seem like it got to the root of the problem. Why would one slave care about another, if they were both reading from the could not find master? I think that article would more accurately be called "Making a slave of a slave" or some such, because "Introducing Additional Slaves to an Existing Replication Environment" does not convey that they are talking about a slave of a slave (which I think they are). Anyway, long and short of it, I removed the ‘master.info' ‘mysqld-relay-bin.*' ‘relay-log.info' ‘relay-log-index.*' from the MySQL data directory, restarted mysql (‘/etc/init.d/mysql restart'), and off to the races. Sometimes, depending on the order you do edit the configs or restart mysql, you can get bad data in those files, and it can lead to crpytic errors. Remove those, and you can always start fresh. This entry was posted in Uncategorized. Bookmark the permalink. 6 thoughts on “Relay log issues when starting MySQL replication slave” Akom says: May 2, 2011 at 1:33 pm That really helped - mine broke with a 5.0 to 5.1 upgrade on the slave (master i
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Hard reboot causes MySQL replication to break up vote 0 down vote favorite I have encountered an issue with my replication setup. Under normal circumstances it performs as intended, but it breaks if it encounters a hard reboot (I pull the power cable). Setup The setup consists of two servers, server-1 and server-2. The replication setup is a circular replication. Both servers are slaves replicating from the other host as if it were the master. Software Red Hat 6.5 MySQL 5.1.73-3 MySQL-libs 5.1.73-3 MySQL-server 5.1.73-3 Redundancy configuration The replication configuration is as follows for server-1, and is mirrored for server-2: GRANT REPLICATION SLAVE ON *.* TO 'replicant'; FLUSH TABLES WITH READ LOCK;" #Use "SHOW MASTER STATUS \G;" to determine log position and log file UNLOCK TABLES; # set status on slave server using the values retieved earlier CHANGE MASTER TO MASTER_HOST='server-2', MASTER_USER='replicant', MASTER_LOG_FILE='[log file]', MASTER_LOG_POS=[log pos];" START SLAVE; Error information This information is retrieved when the server-2 has encountered a hard reboot and the replication is broken. server-1 slave status *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: server-2 Master_User: replicant Master_Port: 3306 Connect_Retry: 60 Master_Log_File: bin.000004 Read_Master_Log_Pos: 37550 Relay_Log_File: relay.000427 Relay_Log_Pos: 245 Relay_Master_Log_File: bin.000004 Slave_IO_Running: Yes Slave_SQL_Running: Yes Replicate_Do_DB: Replicate_Ignore_DB: Replicate_Do_Table: Replicate_Ignore_Table: Replicate_Wild_Do_Table: Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0 Exec_Master_Log_Pos: 37550 Relay_Log_Space: 529 Until_Condition: None Until_Log_File: Until_Log_Pos: 0 Master_SSL_Allowed: No Master_SSL_CA_File: Master_SSL_CA_Path: Master_SSL_Cert: Master_SSL_Cipher: Master_SSL_Key: Seconds_Behind_Master: 0 Master_SSL_Verify_Server_Cert: No Last_IO_Errno: 0 Last_IO_Error: