Mysql Error 1201 Hy000 Could Not Initialize Master Info Structure
Contents |
log in tour help Tour Start here for a quick overview of the site Help Center Detailed error reading master configuration answers to any questions you might have Meta Discuss the error counting relay log space workings and policies of this site About Us Learn more about Stack Overflow the company Business
Failed To Open The Relay Log
Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is
Could Not Find Target Log During Relay Log Initialization
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 failed to open the relay log 'first' (relay_log_pos 4) 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_File: mysqld-relay-bin.0000
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the
Got Fatal Error 1236 From Master When Reading Data From Binary Log:
workings and policies of this site About Us Learn more about change master to Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions could not find first log file name in binary log index file 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 http://dba.stackexchange.com/questions/16321/slave-settings-not-working 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 http://serverfault.com/questions/715849/hard-reboot-causes-mysql-replication-to-break (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_Lo
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}}} http://tech.akom.net/archives/50-MySQL-replication-dies-with-ERROR-1201-HY000-Could-not-initialize-master-info-structure.html 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_
server autostart (gdm) on Ubuntu Karmic (9.10) | Software RAID in Ubuntu Karmic 9.10 > MySQL replication dies with ERROR 1201 (HY000): Could not initialize master info structure Posted by Admin • Friday, February 12. 2010 • Category: Linux On a fine happy morning I am greeted with an alert that slave is not running. Running start slave yields this: ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the MySQL error log Enabling the log yielded nothing. Googling yielded This Page that helped me a lot, but I didn't have to do quite as much work all over again. Here is what I did. First, I saved my "SHOW SLAVE STATUS\G" output: ************************** 1. row ************************** Slave_IO_State: Master_Host: 127.0.0.1 Master_User: replication Master_Port: 3307 Connect_Retry: 60 Master_Log_File: mysqld-bin.000401 Read_Master_Log_Pos: 98 Relay_Log_File: mysqld-relay-bin.006135 Relay_Log_Pos: 242 Relay_Master_Log_File: mysqld-bin.000401 Slave_IO_Running: No Slave_SQL_Running: No 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: 98 Relay_Log_Space: 0 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: NULL 1 row in set (0.00 sec) Next I followed instructions from the blog I mentioned above: STOP SLAVE; RESET SLAVE; Instead of fully reconfiguring I simply tried to start slave. This is a bad idea because it seems to just try to start slaving off the front of the first binlog file it finds, getting conflicts (or worse). So I tried something simple: mysql> CHANGE MASTER TO MASTER_LOG_POS=98 , MASTER_LOG_FILE = 'mysqld-bin.000401'; Query OK, 0 rows affected (0.04 sec) mysql> start slave; Query OK, 0 rows affected (0.00 sec) The position comes from the output I saved before It's working fine again. Still don't know what caused this - possibly random remote server power cycling... 0 Trackbacks Trackback specific URI for this entry No Trackbacks 2 Comments Display comments as (Linear | Threaded) Anonymous on 2010-12-22 09:15: dude you are awesome..thanks alot Anonymous on