MySQL主从失败错误Gotfatalerror1236
内容导读
互联网集市收集整理的这篇技术教程文章主要介绍了MySQL主从失败错误Gotfatalerror1236,小编现在分享给大家,供广大互联网技能从业者学习和参考。文章包含5807字,纯文字阅读大概需要9分钟。
内容图文
![MySQL主从失败错误Gotfatalerror1236](/upload/InfoBanner/zyjiaocheng/547/33ce04d72df148019705ac7f00289fdf.jpg)
MySQL主从失败 错误Got fatal error 1236
同事给我打电话说MySQL团购数据库主从不同步了,尼玛,咋就这么苦逼呢,,好吧,速度开电脑拨VPN解决。
1、登录从库查看主从同步状态,确实是否不同步
mysql> show slave status\G
*************************** 1. row ***************************
Slave_IO_State:
Master_Host: 10.10.0.236
Master_User: slave
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: mysql-bin.001501
Read_Master_Log_Pos: 144001931
Relay_Log_File: mysql-relay-bin.000296
Relay_Log_Pos: 144002077
Relay_Master_Log_File: mysql-bin.001501
Slave_IO_Running: No
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Ignore_DB: mysql,information_schema,performance_schema,test
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: 144001931
Relay_Log_Space: 144002276
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: 'Client requested master to start replication from impossible position'
Last_SQL_Errno: 0
Last_SQL_Error:
Replicate_Ignore_Server_Ids:
Master_Server_Id: 2
1 row in set (0.00 sec)
看来尼玛确实出问题了,查看从库错误日志:
[root@tg_0_zjc tuan]# tail -n 30 logs/mysqld.log
130619 22:23:36 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.001343' at position 107, relay log './mysqld-relay-bin.000001' position: 4
130619 22:23:36 [Note] Slave I/O thread: connected to master 'slave@10.10.0.236:3306',replication started in log 'mysql-bin.001343' at position 107
130620 14:04:21 [Note] Slave: received end packet from server, apparent master shutdown:
130620 14:04:21 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.001343' at position 2544563
130620 14:04:21 [ERROR] Slave I/O: error reconnecting to master 'slave@10.10.0.236:3306' - retry-time: 60 retries: 86400, Error_code: 2003
130620 14:13:45 [Note] Slave: connected to master 'slave@10.10.0.236:3306',replication resumed in log 'mysql-bin.001343' at position 2544563
130623 22:04:17 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
130623 22:04:17 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.001402' at position 121870679
130623 22:04:20 [ERROR] Slave I/O: error reconnecting to master 'slave@10.10.0.236:3306' - retry-time: 60 retries: 86400, Error_code: 2003
130623 22:08:29 [Note] Slave: connected to master 'slave@10.10.0.236:3306',replication resumed in log 'mysql-bin.001402' at position 121870679
130623 22:08:29 [ERROR] Error reading packet from server: Client requested master to start replication from impossible position ( server_errno=1236)
130623 22:08:29 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position', Error_code: 1236
130623 22:08:29 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.001402', position 121870679
130623 22:26:29 [Note] Error reading relay log event: slave SQL thread was killed
130623 22:26:34 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='10.10.0.236', master_port='3306', master_log_file='mysql-bin.001402', master_log_pos='121870679'. New state master_host='10.10.0.236', master_port='3306', master_log_file='mysql-bin.001403', master_log_pos='107'.
130623 22:26:42 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.001403' at position 107, relay log './mysqld-relay-bin.000001' position: 4
130623 22:26:42 [Note] Slave I/O thread: connected to master 'slave@10.10.0.236:3306',replication started in log 'mysql-bin.001403' at position 107
130629 12:04:21 [ERROR] Error reading packet from server: Lost connection to MySQL server during query ( server_errno=2013)
130629 12:04:21 [Note] Slave I/O thread: Failed reading log event, reconnecting to retry, log 'mysql-bin.001501' at position 144001931
130629 12:04:24 [ERROR] Slave I/O: error reconnecting to master 'slave@10.10.0.236:3306' - retry-time: 60 retries: 86400, Error_code: 2003
130629 12:08:33 [Note] Slave: connected to master 'slave@10.10.0.236:3306',replication resumed in log 'mysql-bin.001501' at position 144001931
130629 12:08:33 [ERROR] Error reading packet from server: Client requested master to start replication from impossible position ( server_errno=1236)
130629 12:08:33 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position', Error_code: 1236
130629 12:08:33 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.001501', position 144001931
130629 22:10:08 [Note] Error reading relay log event: slave SQL thread was killed
130629 22:10:12 [Note] Slave SQL thread initialized, starting replication in log 'mysql-bin.001501' at position 144001931, relay log './mysqld-relay-bin.000296' position: 144002077
130629 22:10:12 [Note] Slave I/O thread: connected to master 'slave@10.10.0.236:3306',replication started in log 'mysql-bin.001501' at position 144001931
130629 22:10:12 [ERROR] Error reading packet from server: Client requested master to start replication from impossible position ( server_errno=1236)
130629 22:10:12 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position', Error_code: 1236
130629 22:10:12 [Note] Slave I/O thread exiting, read up to log 'mysql-bin.001501', position 144001931
内容总结
以上是互联网集市为您收集整理的MySQL主从失败错误Gotfatalerror1236全部内容,希望文章能够帮你解决MySQL主从失败错误Gotfatalerror1236所遇到的程序开发问题。 如果觉得互联网集市技术教程内容还不错,欢迎将互联网集市网站推荐给程序员好友。
内容备注
版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 gblab@vip.qq.com 举报,一经查实,本站将立刻删除。
内容手机端
扫描二维码推送至手机访问。