Error Reading Master Configuration Mysql
Contents |
here for a quick overview of the site Help Center Detailed answers to any questions error 1201 hy000 could not initialize master info structure you might have Meta Discuss the workings and policies of error counting relay log space this site About Us Learn more about Stack Overflow the company Business Learn more about hiring failed to open the relay log developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is could not find target log during relay log initialization 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 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
Failed To Open The Relay Log 'first' (relay_log_pos 4)
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 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,231145589 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 M
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: Replication :: [ERROR] Failed to initialize the master info structure New Topic Advanced Search
Got Fatal Error 1236 From Master When Reading Data From Binary Log:
[ERROR] Failed to initialize the master info structure Posted by: Gilles change master to GAUDIN () Date: May 10, 2010 03:04AM Hi ! I have a problem with my replication environment. could not find first log file name in binary log index file I have 1 master and 3 slaves. Every sunday, I restart the master mysql daemon to rotate log files (mysqld.log and slow log), I use a script for this http://stackoverflow.com/questions/5029485/error-could-not-initailize-master-info-structure-while-doing-master-slave-rep who move log files, create new log files, chown them and then restart mysqld. On the 3 slaves there is mk-slave-restart from maatkit tool, so when the master restart, mk-slave-restart skip error on slaves. On two slaves there is no problem but on the third replication stop and I can see this error in the log file: http://forums.mysql.com/read.php?26,366829 [ERROR] Error reading master configuration [ERROR] Failed to initialize the master info structure I have to reset this slave and 'change master to' with info that are displayed into master.info and then restart the slave. Replication is ok after that. My questions are: Why slave can't continue his replication ? why this error is not present on others slaves ? Is there a way to solve this problem ? Thanks in advance for support. Navigate:Previous Message•Next Message Options:Reply•Quote Subject Views Written By Posted [ERROR] Failed to initialize the master info structure 6717 Gilles GAUDIN 05/10/2010 03:04AM Re: [ERROR] Failed to initialize the master info structure 2868 Rick James 05/11/2010 07:27AM Re: [ERROR] Failed to initialize the master info structure 2453 Gilles GAUDIN 05/11/2010 07:47AM Re: [ERROR] Failed to initialize the master info structure 2128 Rick James 05/11/2010 08:36AM Sorry, you can't reply to this topic. It has been closed. powered by phorum Content reproduced on this site is the property of the respective copyright holders. It is not revie
created relay files in /var/run/mysqld/ which filled up the whole of the partition and caused errors http://perplexed.co.uk/301_restoring_a_broken_slave.htm in the logs. To repair the problem i ran {{{RESET MASTER}}} on the master db server and removed the relay files from 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 blog documented a similar problem whereby relay log 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 slave from master using bash Handling other failed to open 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.000125' at position 920655371 080718 10:35:34 [ERROR] Error reading packet from server: log event entry exceeded max_allowed_packet;