Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.2.11
-
None
-
FreeBSD 11.1
Description
After upgrading from 10.2.10 to 10.2.11, replication failed after the binary logs were cycled at 0000 in the morning. The slave processes show an error indicating that the master can not locate the new binary logs.
show slave status\G
|
...
|
Master_Log_File: mysql-bin.000611
|
Read_Master_Log_Pos: 4
|
Slave_IO_Running: No |
Slave_SQL_Running: Yes
|
Last_IO_Errno: 1236
|
Last_IO_Error: Got fatal error 1236 from master when reading data from binary log: 'could not find next log; the first event 'mysql-bin.000609' at 73278354, the last event read from 'mysql-bin.000610' at 67998964, the last byte read from 'mysql-bin.000610' at 67999011.' |
Slave_SQL_Running_State: Slave has read all relay log; waiting for the slave I/O thread to update it |
On the master server, a SHOW BINARY LOGS command only shows binary logs created before the upgrade...
+------------------+-----------+
|
| Log_name | File_size |
|
+------------------+-----------+
|
| mysql-bin.000596 | 77618783 |
|
| mysql-bin.000597 | 62336068 |
|
| mysql-bin.000598 | 140566167 |
|
| mysql-bin.000599 | 141528752 |
|
| mysql-bin.000600 | 139638075 |
|
| mysql-bin.000601 | 139803271 |
|
| mysql-bin.000602 | 141700844 |
|
| mysql-bin.000603 | 140429994 |
|
| mysql-bin.000604 | 142377738 |
|
| mysql-bin.000605 | 140429224 |
|
| mysql-bin.000606 | 140052010 |
|
| mysql-bin.000607 | 140098989 |
|
| mysql-bin.000608 | 139437164 |
|
| mysql-bin.000609 | 73278377 |
|
| mysql-bin.000610 | 67999011 |
|
+------------------+-----------+
|
...but the file system shows all binary logs.
-rw-rw---- 1 mysql mysql 77618783 Nov 29 13:09 mysql-bin.000596
|
-rw-rw---- 1 mysql mysql 62336068 Nov 30 00:00 mysql-bin.000597
|
-rw-rw---- 1 mysql mysql 140566167 Dec 1 00:00 mysql-bin.000598
|
-rw-rw---- 1 mysql mysql 141528752 Dec 2 00:00 mysql-bin.000599
|
-rw-rw---- 1 mysql mysql 139638075 Dec 3 00:00 mysql-bin.000600
|
-rw-rw---- 1 mysql mysql 139803271 Dec 4 00:00 mysql-bin.000601
|
-rw-rw---- 1 mysql mysql 141700844 Dec 5 00:00 mysql-bin.000602
|
-rw-rw---- 1 mysql mysql 140429994 Dec 6 00:00 mysql-bin.000603
|
-rw-rw---- 1 mysql mysql 142377738 Dec 7 00:00 mysql-bin.000604
|
-rw-rw---- 1 mysql mysql 140429224 Dec 8 00:00 mysql-bin.000605
|
-rw-rw---- 1 mysql mysql 140052010 Dec 9 00:00 mysql-bin.000606
|
-rw-rw---- 1 mysql mysql 140098989 Dec 10 00:00 mysql-bin.000607
|
-rw-rw---- 1 mysql mysql 139437164 Dec 11 00:00 mysql-bin.000608
|
-rw-rw---- 1 mysql mysql 73278377 Dec 11 12:09 mysql-bin.000609
|
-rw-rw---- 1 mysql mysql 67999011 Dec 12 00:00 mysql-bin.000610
|
-rw-rw---- 1 mysql mysql 139787598 Dec 13 00:00 mysql-bin.000611
|
-rw-rw---- 1 mysql mysql 72954545 Dec 13 12:25 mysql-bin.000612
|
-rw-rw---- 1 mysql mysql 765112 Dec 13 12:33 mysql-bin.000613
|
-rw-rw---- 1 mysql mysql 81910 Dec 13 12:34 mysql-bin.000614
|
-rw-rw---- 1 mysql mysql 358 Dec 13 12:34 mysql-bin.000615
|
-rw-rw---- 1 mysql mysql 2953 Dec 13 12:34 mysql-bin.index
|
In addition, running tail on the mysql-bin.index file only shows some of the binary logs created by 10.2.11 but not all of them and not any of the logs created by 10.2.10.
...
|
Next activation : never
|
./mysql-bin.000612
|
./mysql-bin.000613
|
./mysql-bin.000614
|
./mysql-bin.000615
|
Running a SHOW MASTER STATUS command on the master server does show the current log and the position is updated.
show master status;
|
+------------------+----------+--------------+------------------+ |
| File | Position | Binlog_Do_DB | Binlog_Ignore_DB |
|
+------------------+----------+--------------+------------------+ |
| mysql-bin.000615 | 1816938 | | |
|
+------------------+----------+--------------+------------------+ |
It seems to me that parts of the system on the master are no longer tracking the binary logs properly.
Attachments
Issue Links
- duplicates
-
-
- Closed
-
-
-
- Closed
-
-
-
- Closed
-