Canal reports Could not find first log file name in binary log index file

Check /home/admin/canal-server/logs/example/example.log for the following errors:

2022-07-20 00:00:08.473 [destination = example , address = mall-mysql/192.168.38.131:3306 , EventParser] ERROR com.alibaba.otter.canal.common.alarm.LogAlarmHandler - destination:example[java.io.IOException: Received error packet: errno = 1236, sqlstate = HY000 errmsg = Could not find first log file name in binary log index fileat com.alibaba.otter.canal.parse.inbound.mysql.dbsync.DirectLogFetcher.fetch(DirectLogFetcher.java:102)at com.alibaba.otter.canal.parse.inbound.mysql.MysqlConnection.dump(MysqlConnection.java:238)at com.alibaba.otter.canal.parse.inbound.AbstractEventParser$1.run(AbstractEventParser.java:262)at java.lang.Thread.run(Thread.java:748) 

Reason:

The binlog file set in the configuration file was not found

Solution:

Because the instance.properties configuration file in this example is packaged into the docker image, it can only be modified in the instance

Check the binlog log file name and position in the database first

Query in this example mall-mysql database:

mysql> show master status;

Output File: mysql-binlog.000233, Position: 652645

Enter the instance:

kubectl exec -ti mall-canal-84f6f7d7cc-xbghn bash -n nsNamexxx> vi /home/admin/canal-server/conf/example/instance.properties

Modify the position info section:

canal.instance.master.address=mall-mysql:3306canal.instance.master.journal.name=mysql-binlog.000233canal.instance.master.position=652645canal.instance.master.timestamp=canal.instance.master.gtid=

Restart the service:

xxx> cd /home/admin/canal-serverxxx> ./restart.sh

Check the log after restarting, the fault is eliminated