Error Reading Master Configuration
Contents |
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions error reading master configuration mysql replication you might have Meta Discuss the workings and policies of this
Failed To Initialize The Master Info Structure
site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers error 1201 hy000 could not initialize master info structure or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database
Error Counting Relay Log Space
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 rise to the top Disable MySQL replication up vote 1 down vote failed to open the relay log favorite I'm running following: # cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.6 (Santiago) # uname -a Linux X 2.6.32-504.3.3.el6.x86_64 #1 SMP Fri Dec 12 16:05:43 EST 2014 x86_64 x86_64 x86_64 GNU/Linux # rpm -q mysql-server mysql-server-5.1.73-3.el6_5.x86_64 # I issued STOP SLAVE; and deleted master.info and now /var/log/mysqld-error.log is producing following: [ERROR] Error reading master configuration [ERROR] Failed to initialize the master info structure What's the proper way to disable MySQL replication? mysql replication share|improve this question asked Feb 11 '15 at 15:49 alexus 16511 add a comment| 2 Answers 2 active oldest votes up vote 1 down vote accepted After you ran RESET SLAVE; make sure there is no slave status. Run this SHOW SLAVE STATUS\G If there is any information still being presented, you need to run this CHANGE MASTER TO master_host = ''; Then, go run SHOW SLAVE STATUS\G You should get nothing and master.info should be gone. From the MySQL 5.1 Documentation If any startup option
created relay files in /var/run/mysqld/ which filled up the whole of the partition and caused errors in the logs. To repair the problem i ran {{{RESET MASTER}}} on the master
Could Not Find Target Log During Relay Log Initialization
db server and removed the relay files from the slave. This didn't have
Failed To Open The Relay Log 'first' (relay_log_pos 4)
the desired affect. >Start slave; "Error reading slave log configuration" I then banged my head against the wall. A blog got fatal error 1236 from master when reading data from binary log: 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 http://dba.stackexchange.com/questions/91706/disable-mysql-replication 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): 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 http://perplexed.co.uk/301_restoring_a_broken_slave.htm 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 fatal error 1236: 'log event entry exceeded max_allowed_packet; Increase max_allowed_packet on master' from master when reading data from binary log 080718 10:35:34 [ERROR] Slave I/O thread exiting, read up to log 'db1-bin.000125', position 920655371 It tells us what to do Update the mysql parameter on the master. So edit my.cnf with... max_allowed_packet=16M Edit Article Comments greatgreat information!Created 05/11/09willow315I am attempting to resolve an issue with mySQL timing out and bringing my site down....about
mysql Log in Or connect using: Facebook Twitter VK Google+ Mail.ru OpenID Error Username: Error Password: Forgot password? Remember me Log in http://mysql.livejournal.com/129177.html Forgot password? Create an Account Your OpenID URL: Log in kiltum http://serverfault.com/questions/715849/hard-reboot-causes-mysql-replication-to-break (kiltum) wrote in mysql, 2008-06-17 12:53:00 kiltum kiltum mysql 2008-06-17 12:53:00 Previous Share Next ERROR 1201 (HY000): Could not initialize master info structure ... Hello all. I'm so bored to kill this error ... can anybody help me?I have one master and about 10 relay log slave servers. Time to time one (absolutely random) slave server lost replication connection. When i type slave stop; slave start; i see "ERROR 1201 (HY000): Could not initialize master info structure; more error messages can be found in the MySQL error log"When i look at /var/log/mysql.log, i see[ERROR] Failed to open the relay log error reading master '/var/run/mysqld/mysqld-relay-bin.000759' (relay_log_pos 235)080617 12:25:45 [ERROR] Could not find target log during relay log initializationOK, "slave reset", drop databases , set MASTER etc, slave start - and replication does just fine. without any errors. Until the next time.I add to my.cnf next lines:max-relay-log-size=1Mmax-binlog-size=2Mrelay-log=/var/run/mysqld/mysqld-relay-binBut without any effect: replication may work fine long time or break at next hour.Question: how can set replication, that always work ? :)Platform: Linux Fedora 6 & 7, mysql 5.0.45, no any errors about disk or memory. Size of replication tables - about 1-2Mb Post a new comment Error We will log you in after post We will log you in after post We will log you in after post We will log you in after post We will log you in after post Anonymously switch LiveJournal Facebook Twitter OpenId Google MailRu VKontakte Anonymously default userpic Insert Bold Insert Italic Insert Underline Insert Strikethrough Insert Link Insert LJ User Insert Photo Insert Media Post a new comment Preview comment Help
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: Last_SQL_Errno: 0 Last_SQL_Error: server-2 slave s