setup slave from backup i got 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'

MASTER

MariaDB [(none)]> SHOW BINLOG EVENTS IN 'mysqld-bin.140180' FROM 101070557 LIMIT 4;
+-------------------+-----------+----------------+-----------+-------------+---------------------------------------+
| Log_name          | Pos       | Event_type     | Server_id | End_log_pos | Info                                  |
+-------------------+-----------+----------------+-----------+-------------+---------------------------------------+
| mysqld-bin.140180 | 101070557 | Gtid           |         7 |   101070595 | BEGIN GTID 0-7-8640143404             |
| mysqld-bin.140180 | 101070595 | Table_map      |         7 |   101070647 | table_id: 4446293 (dating.users_hits) |
| mysqld-bin.140180 | 101070647 | Update_rows_v1 |         7 |   101070695 | table_id: 4446293 flags: STMT_END_F   |
| mysqld-bin.140180 | 101070695 | Query          |         7 |   101070778 | COMMIT                                |
+-------------------+-----------+----------------+-----------+-------------+---------------------------------------+
4 rows in set (0.00 sec)
MariaDB [(none)]> show binary logs ;
+-------------------+------------+
| Log_name          | File_size  |
+-------------------+------------+
| mysqld-bin.140100 |  134219175 |
...
| mysqld-bin.140180 |  134217853 |
| mysqld-bin.140181 |  134232575 |
| mysqld-bin.140182 |  134229889 |
...
| mysqld-bin.140570 |   46141034 |
+-------------------+------------+
547 rows in set (0.00 sec)
#>for f in $(cat mysqld-bin.index); do test -f $f || echo "Not found $f" ; done;
<no output>
 
#>head mysqld-bin.index
./mysqld-bin.140100
./mysqld-bin.140101
./mysqld-bin.140102
./mysqld-bin.140103
./mysqld-bin.140104
./mysqld-bin.140105
./mysqld-bin.140106
./mysqld-bin.140107
./mysqld-bin.140108
./mysqld-bin.140109

SLAVE

MariaDB [(none)]> change master to master_host='10.8.2.31', master_user='replica', master_password='', master_log_file='mysqld-bin.140180 ', master_log_pos=101070557;
Query OK, 0 rows affected (0.00 sec)
 
MariaDB [(none)]> start slave IO_THREAD;
Query OK, 0 rows affected (0.00 sec)
MariaDB [(none)]> show slave status\G
*************************** 1. row ***************************
               Slave_IO_State: 
                  Master_Host: 10.8.2.31
                  Master_User: replica
                  Master_Port: 3306
                Connect_Retry: 60
              Master_Log_File: mysqld-bin.140180 
          Read_Master_Log_Pos: 101070557
               Relay_Log_File: relay-bin.000001
                Relay_Log_Pos: 4
        Relay_Master_Log_File: mysqld-bin.140180 
             Slave_IO_Running: No
            Slave_SQL_Running: No
...
          Exec_Master_Log_Pos: 101070557
...
                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'
160330 15:18:42 [Note] Slave SQL thread initialized, starting replication in log 'mysqld-bin.140180 ' at position 101070557, relay log './relay-bin.000001' position: 4
160330 15:18:42 [Note] Slave I/O thread: connected to master 'replica@10.8.2.31:3306',replication started in log 'mysqld-bin.140180 ' at position 101070557
160330 15:18:42 [ERROR] Error reading packet from server: Could not find first log file name in binary log index file ( server_errno=1236)
160330 15:18:42 [ERROR] Slave I/O: Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file', Internal MariaDB error code: 1236
160330 15:18:42 [Note] Slave I/O thread exiting, read up to log 'mysqld-bin.140180 ', position 10

Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'的更多相关文章

  1. 【MySQL】MySQL同步报错-> Last_IO_Error: Got fatal error 1236 from master when reading data from binary log

    这个报错网上搜索了一下,大部分是由于MySQL意外关闭或强制重启造成的binlog文件事务点读取异常造成的主从同步报错 Last_IO_Error: Got fatal error 1236 from ...

  2. mysql 主从 Got fatal error 1236 from master when reading data from binary log: 'Could not find first 错误

    本地MySQL环境,是两台MySQL做M-M复制.今天发现错误信息: mysql 5.5.28-log> show slave status\G ************************ ...

  3. Last_IO_Errno: 1236 Last_IO_Error: Got fatal error 1236 from master when reading data from binary lo

    mysql> show slave status\G *************************** 1. row ***************************         ...

  4. Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'系列一:

    从库报这个错误:Got fatal error 1236 from master when reading data from binary log: 'Could not find first lo ...

  5. Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'系列三:重置主从同步

    1:停止slave服务器的主从同步 stop slave; 2:对Master数据库加锁 flush tables with read lock; 3:备份Master上的数据 mysqldump - ...

  6. MySQL案例09:Last_IO_Error: Got fatal error 1236 from master when reading data from binary log

    刚处理完“挖矿”事件,在做最后一个MySQL NBU备份的时候,发现从库有问题,好奇的是怎么主从状态异常没有告警呢?先不管这么多了,处理了这个问题再完善告警内容. 一.错误信息 从库show slav ...

  7. mysql从库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'报错处理

    年后回来查看mysql运行状况与备份情况,登录mysql从库查看主从同步状态 mysql> show slave status\G; *************************** . ...

  8. Got fatal error 1236 from master when reading data from binary log: 'Client requested master to start replication from impossible position

    在source那边,执行: flush logs;show master status; 记下File, Position. 在target端,执行: CHANGE MASTER TO MASTER_ ...

  9. Got fatal error 1236 from master when reading data from binary log: 'Could not find first log file name in binary log index file'系列二:reset slave

    reset slave会清除从库的所有复制信息.一般应用场景:如切换为不同的Master, 主从重做等: 1. 命令在slave上执行,执行前一定要stop slave. 2. 执行reset sla ...

随机推荐

  1. debian禁止或者允许指定ip访问远程mysql、ssh、rsynccat /etc/xinetd.conf

    如果没有安装xinetd,安装xinetd apt-get install xinetd 然后创建配置文件 vi /etc/xinetd.d/mysqld service login { socket ...

  2. mySql---logback日志写入数据库(mysql)配置

    如题  建议将日志级别设置为ERROR.这样可以避免存储过多的数据到数据中. 1  logback 配置文件(如下) <?xml version="1.0" encoding ...

  3. MySQL导数据工具对比

    最近遇到非常多的导数据的需求(主要是CSV的需求),专门对mysqldump.pt-archive.mydumper做了一下对别,粗浅研究,以备将来使用.   msqldump pt-archive ...

  4. Spring+JDBC实例

    1. Customer 表 在这个例子中,我们使用的是MySQL数据库. CREATE TABLE `customer` ( `CUST_ID` int(10) unsigned NOT NULL A ...

  5. zookeeper集群,每个服务器上的数据是相同的,每一个服务器均可以对外提供读和写的服务,这点和redis是相同的,即对客户端来讲每个服务器都是平等的。

    zookeeper集群,每个服务器上的数据是相同的,每一个服务器均可以对外提供读和写的服务,这点和redis是相同的,即对客户端来讲每个服务器都是平等的.

  6. linux下的springboot项目启动文件

    启动springboot项目的脚本文件,启动时./startup.sh即可,会先关闭原进程,再启一个新进程. 创建startup.sh 写入内容 #!/bin/bash clear echo &quo ...

  7. win7 64位的 svchost.exe 占用内存过大的问题

    svchost.exe 是用来启动系统服务的,所以某个 svchost.exe 占用内存过大,可能就是它启动的那个服务占用内存过大,所以只要停止并禁用那个服务就行了. 一般来说占用内存最大的服务是 S ...

  8. go语言基础之函数类型

    1.函数类型 示例: package main import "fmt" func Add(a, b int) int { return a + b } func main() { ...

  9. TypeEvaluator 估值器 抛物线

    TypeEvaluator简介 Android提供了以下几个简单的Evalutor实现类: IntEvaluator:属性的值类型为int FloatEvaluator:属性的值类型为float Ar ...

  10. java中 HashMap和Hashtable,list、set和map 的区别

    摘自: http://blog.chinaunix.net/uid-7374279-id-2057584.html HashMap是Hashtable的轻量级实现(非线程安全的实现),他们都完成了Ma ...