mysql主从同步错误解决

mysql主从同步错误解决和Slave_IO_Running: NO

一:

Slave I/O: error connecting to master ‘[email protected]:3306‘ - retry-time: 60  retries: 86400, Error_code: 1045

解决方法

从服务器上删除掉所有的二进制日志文件,包括一个数据目录下的master.info文件和hostname-relay-bin开头的文件。

master.info::记录了Mysql主服务器上的日志文件和记录位置、连接的密码。

或者是防火墙问题

二:出现错误提示

Error reading packet from server: File ‘/home/mysql/mysqlLog/log.000001‘ not found (Errcode: 2) ( server_errno=29)

解决方法:

由于主服务器运行了一段时间,产生了二进制文件,而slave是从log.000001开始读取的,删除主机二进制文件,包括log.index文件。

三:错误提示如下

Slave SQL: Error ‘Table ‘xxxx‘ doesn‘t exist‘ on query. Default database: ‘t591‘. Query: ‘INSERT INTO `xxxx`(type,post_id,browsenum)

SELECT type,post_id,browsenum FROM xxxx WHERE hitdate=‘20090209‘‘, Error_code: 1146

解决方法:

由于slave没有此table表,添加这个表,使用slave start 就可以继续同步。

四:错误提示如下

Error ‘Duplicate entry ‘1‘ for key 1‘ on query. Default database: ‘movivi1‘. Query: ‘INSERT INTO `v1vid0_user_samename`

VALUES(null,1,‘123‘,‘11‘,‘4545‘,‘123‘)‘

Error ‘You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax

to use near ‘‘ at line 1‘ on query. Default database: ‘club‘. Query: ‘INSERT INTO club.point_process ( GIVEID, GETID, POINT, CREATETIME, DEMO )

VALUES ( 0, 4971112, 5, ‘2010-12-19 16:29:28‘,‘

1 row in set (0.00 sec)

Mysql > Slave status\G;

显示:Slave_SQL_Running 为 NO

解决方法:

Mysql > stop slave;

Mysql > set global sql_slave_skip_counter =1 ;

Mysql > start slave;

五:错误提示如下

show slave status\G;

Master_Log_File: mysql-bin.000029

Read_Master_Log_Pos: 3154083

Relay_Log_File: c7-relay-bin.000178

Relay_Log_Pos: 633

Relay_Master_Log_File: mysql-bin.000025

Slave_IO_Running: Yes

Slave_SQL_Running: No

Replicate_Do_DB: club

Replicate_Ignore_DB:

Replicate_Do_Table:

Replicate_Ignore_Table:

Replicate_Wild_Do_Table:

Replicate_Wild_Ignore_Table:

Last_Errno: 1594

Last_Error: Relay log read failure: Could not parse relay log event entry. The possible reasons are:

the master‘s binary log is corrupted (you can check this by running ‘mysqlbinlog‘ on the binary log),

the slave‘s relay log is corrupted (you can check this by running ‘mysqlbinlog‘ on the relay log),

a network problem, or a bug in the master‘s or slave‘s MySQL code. If you want to check the master‘s

binary log or slave‘s relay log, you will be able to know their names by issuing ‘SHOW SLAVE STATUS‘ on this slave.

Skip_Counter: 0

Exec_Master_Log_Pos: 1010663436

这个问题原因是,主数据库突然停止或问题终止,更改了mysql-bin.xxx日志,slave服务器找不到这个文件,需要找到同步的点和日志文件,然后chage master即可。

解决方法:

change master to

master_host=‘IP‘,

master_user=‘同步帐号‘,

master_password=‘同步密码‘,

master_port=3306,

master_log_file=‘mysql-bin.000025‘,

master_log_pos=1010663436;

六:错误提示如下

Error ‘Unknown column ‘qdir‘ in ‘field list‘‘ on query. Default database: ‘club‘. Query: ‘insert into club.question_del (id, pid,

ques_name, givepoint, title, subject, subject_pid, createtime, approve, did, status, intime, order_d, endtime,banzhu_uid,

banzhu_uname,del_cause,qdir) select id, pid, ques_name, givepoint, title, subject, subject_pid, createtime, approve, did,

status, intime, order_d, endtime,‘1521859‘,‘admin0523‘,‘无意义回复‘,qdir from club.question where id=7330212‘

1 row in set (0.00 sec)

这个错误就说club.question_del 表里面没有qdir这个字段 造成的加上就可以了~!

在主的mysql : 里面查询 Desc club.question_del;

在 错误的从服务器上执行 : alter table question_del add qdir varchar(30) not null;

七:错误提示如下

Slave_IO_Running: NO

这个错误就是IO 进程没连接上  ,想办法连接上把 把与主的POS 号和文件一定要对,然后重新加载下数据。具体步骤:

slave stop;

change master to master_host=‘IP地址‘,master_user=‘club‘,master_password=‘mima ‘,master_log_file=‘mysqld-bin.000048‘,MASTER_LOG_POS=396549485;

注:master_log_file=‘mysqld-bin.000048‘,MASTER_LOG_POS=396549485;是从主的上面查出 来的 :show master status\G;

LOAD DATA FROM MASTER;

load data from master;

slave start;

八 ,mysql报错如下:

mysql> show slave status\G;

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: 192.168.0.198

Master_User: rootclub

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: mysql-bin.000061

Read_Master_Log_Pos: 494107148

Relay_Log_File: xyxyclub-relay-bin.006609

Relay_Log_Pos: 1073365

Relay_Master_Log_File: mysql-bin.000061

Slave_IO_Running: Yes

Slave_SQL_Running: Yes

Replicate_Do_DB: club

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: 494107148

Relay_Log_Space: 1073365

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

1 row in set (0.00 sec)

ERROR:

No query specified  #这里提示有错误,刚开始我以为数据库的问题呢,经过查询验证,发现并不是数据库的问题,而是我们操作的问题,

看下面操作。就没有报错误吧。

mysql> mysql> show slave status\G

*************************** 1. row ***************************

Slave_IO_State:

Master_Host: 192.168.0.198

Master_User: rootclub

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: mysql-bin.000061

Read_Master_Log_Pos: 494248077

Relay_Log_File: xyxyclub-relay-bin.006609

Relay_Log_Pos: 1213077

Relay_Master_Log_File: mysql-bin.000061

Slave_IO_Running: No

Slave_SQL_Running: No

Replicate_Do_DB: club

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: 494246860

Relay_Log_Space: 1214294

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)

mysql>

解释:

show slave status\G

\G就是结束  再加一个";" 就多余了,所以才报错,这2个结束符号别重复使用就是...

九.mysql> show slave status\G

*************************** 1. row ***************************

Slave_IO_State:

Master_Host: 192.168.1.18

Master_User: tongbu

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: mysql-bin.000022

Read_Master_Log_Pos: 106

Relay_Log_File: mysqld-relay-bin.000035

Relay_Log_Pos: 251

Relay_Master_Log_File: mysql-bin.000022

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: 1

Exec_Master_Log_Pos: 106

Relay_Log_Space: 552

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

Master_SSL_Verify_Server_Cert: No

Last_IO_Errno: 1236

Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: ‘Could not find first log file name in binary log index file‘

Last_SQL_Errno: 0

Last_SQL_Error:

1 row in set (0.00 sec)

解决方法是在master端从新看一下master状态

在master那边,执行:

flush logs;

show master status;

记下File, Position。

在slave端,执行:

Slave stop

CHANGE MASTER TO MASTER_LOG_FILE=‘testdbbinlog.000008‘,MASTER_LOG_POS=107;

slave start;

show slave status \G

一切正常。

原文地址:https://www.cnblogs.com/zhangan/p/10899594.html

时间: 2024-10-03 18:38:42

mysql主从同步错误解决的相关文章

mysql主从同步错误解决和Slave_IO_Running: NO

1.出现错误提示. Slave I/O: error connecting to master '[email protected]:3306' - retry-time: 60  retries: 86400, Error_code: 1045 解决方法 从服务器上删除掉所有的二进制日志文件,包括一个数据目录下的master.info文件和hostname-relay-bin开头的文件. master.info::记录了Mysql主服务器上的日志文件和记录位置.连接的密码. 2.出现错误提示

mysql主从同步错误记录。

mysql主从同步失败,原因是主跟从已经有相同的数据在里面了. 解决方法:在从库的/etc/my.cnf里添加如下代码 [mysqld] slave-skip-errors = 1032,1062,1007,1050 案例一: mysql> show slave status\G *************************** 1. row *************************** Slave_IO_State: Waiting for master to send eve

mysql主从不一致解决方法

方法一:忽略错误后,继续同步 该方法适用于主从库数据相差不大,或者要求数据可以不完全统一的情况,数据要求不严格的情况 stop slave; #表示跳过一步错误,后面的数字可变 set global sql_slave_skip_counter =1; start slave; 查看slave状态 mysql> show slave status; 方法二:从新做主从 解决步骤如下: 1.先进入主库,进行锁表,防止数据写入 使用命令: mysql> flush tables with read

企业案例 【故障修复】mysql主从故障解决过程

由于配置有zabbix监控,某日收到zabbix监控主从报警,,查看mysql状态, showslave status \G; slave复制状态有误,SLAVE_SQL_RUNNING为NO, 接着看下面的错误信息,提示有一个表插入数据,提示表不存在, 随后在从库上检查该库该表,发现都存储,就纳闷了. 再回头看报错有新发现,提示的表明是大写,我刚才检查的小写, ok,再次进入从数据库使用大写查询表,果然报错,看来是大小写问题引起的. 查资料发现mysql参数有忽略大小写的参数lower_cas

一种粗暴快速的解决mysql主从不同步错误的思路

mysql主从经常会出现主从数据不同步的问题,脏数据会造成主从同步中断, 出现大量ERROR,如1032,1062等错误.常规方法是逐条删除脏数据或者 重做库,由于数据量大操作麻烦,而且主库在线上运行不能有锁表操作, 各种不便特别费时间.笔者在生产环境遭遇了一次,情急之下用粗暴的方法 不到10分种解决问题.下面假设一种情况,主库正常,从库数据不一致, 解决思路步骤如下: 1 ,对故障定性,通过查看最近日志来找出蛛丝马迹.一般都用mysqlbinlog /var/lib/myql/mysqld-b

Mysql主从库同步错误:1062 Error 'Duplicate entry '1438019'

mysql主从库同步错误:1062 Error 'Duplicate entry '1438019' for key 'PRIMARY'' on query mysql主从库在同步时会发生1062 Last_SQL_Error: Error ‘Duplicate entry ‘的问题: 显然这个问题是因为插入重复主键导致从库不工作了,错误消息如下 mysql> show slave status\G; *************************** 1. row ************

解决MySQL主从不同步问题

解决mysql主从不同步 今天发现Mysql的主从数据库没有同步 先上Master库: mysql>show processlist;   查看下进程是否Sleep太多.发现很正常. show master status; 也正常. mysql> show master status; +-------------------+----------+--------------+-------------------------------+ | File              | Pos

MySQL主从ssl加密传输报错解决

案例:今天实施MySQL主从+SSL加密传输时候,master为slave签署证书有一个小小问题: failedto update database TXT_DBerror number 2 一开始没留意,最后导致在slave通过证书连接master时候报错证书错误.仔细检查才看到错误. 1.报错原因: This thing happens when certificates share common data. You cannot have two  certificates that lo

mysql 主从同步故障解决   Error 'Row size too large (> 8126).

错误日志:  Error 'Row size too large (> 8126). Changing some columns to TEXT or BLOB   or using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED may help. In current row   format, BLOB prefix of 768 bytes is stored inline.' on query. Default   database: 'XXXX