Mysql Error 1201
Contents |
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: Replication :: Could not initialize master info structure, more error messages can be found in the MySQL error log New Topic Advanced Search Could error reading master configuration not initialize master info structure, more error messages can be found in the error counting relay log space MySQL error log Posted by: Prakash Nallusamy () Date: July 19, 2007 09:23AM Hi, I am facing this issue. I failed to open the relay log am having 1 master server and 7 slaves . due to some problem one of my slave got out of sync with master. wen i tried to start the slave am getting this error
Could Not Find Target Log During Relay Log Initialization
: mysql> start slave; ERROR 1201: Could not initialize master info structure, more error messages can be found in the MySQL error log my mysqlbinlog file contains : 070719 15:53:36 Could not find target log during relay log initialization070719 15:57:38 Failed to open the relay log 'sn-uk-1-relay-bin.027' (relay_log_pos 458832187) and I have searched google and i got some information with that i have tried in this way change master to mysql> CHANGE MASTER TO master_log_file='sn-sj-1-bin.021',master_log_pos=275410644; ERROR 1201: Could not initialize master info structure, more error messages can be found in the MySQL error log but still am getting this error. Note : My master server is having the version :4.0.20 One of my slave which is out of sync with master is having the version :4.0.18 Above problem is because of version problem ?. If version is the problem then how to make the slave with sync with master without changing the version. else if version differ is not the problem then how can i reslove this problem . please help me. Thanks Prakash Edited 1 time(s). Last edit at 07/26/2007 04:04AM by Prakash Nallusamy. Navigate:Previous Message•Next Message Options:Reply•Quote Subject Views Written By Posted Could not initialize master info structure, more error messages can be found in the MySQL error log 58335 Prakash Nallusamy 07/19/2007 09:23AM Re: Could not initialize master info structure, more error messages can be found in the MySQL error log 31269 eni 07/19/2007 10:13AM Re: Could not initialize master info structure, more error messages can be found in the MySQL error log 23979 Helder Morais 07/25/2007 12:00PM Re: Could not initialize master info structure, mo
log in tour help Tour Start here for a quick overview of the site Help Center Detailed mysql replication 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 Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange http://forums.mysql.com/read.php?26,163227,163227 is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. 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 http://dba.stackexchange.com/questions/16321/slave-settings-not-working rise to the top Slave settings not working up vote 1 down vote favorite I have this machine as slave. Below is the command I ran and stuck. I done the change on the config file and set the id=2 too. Anything else I am missing here? slave start; ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the MySQL error log mysql> change master to MASTER_HOST='192.168.1.15', MASTER_USER='replication1', MASTER_PASSWORD='*******',MASTER_LOG_FILE='mysql-bin.000001'; ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the MySQL error log ? Below is the results of show master status\G *************************** 1. row *************************** File: mysql-bin.000001 Position: 98 Binlog_Do_DB: fms,sms Binlog_Ignore_DB: 1 row in set (0.00 sec) show slave status\G *************************** 1. row *************************** Slave_IO_State: Waiting for master to send event Master_Host: 192.168.1.15 Master_User: replication1 Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000001 Read_Master_Log_Pos: 98 Relay_Log_Fil
created relay files in /var/run/mysqld/ which filled up the whole of the partition and caused errors in the http://perplexed.co.uk/301_restoring_a_broken_slave.htm 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 the files master.info relay log 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 Errors Error "ERROR 1201 (HY000): mysql error 1201 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; Increase max_allowed_packet on master (server_errno=1236) 080718 10:35:34 [ERROR] Got