search cancel

MySQL:DB replication is not happening on Intranet Gateway server

book

Article ID: 189162

calendar_today

Updated On:

Products

CA API Gateway API SECURITY CA API Gateway Precision API Monitoring Module for API Gateway (Layer 7) CA API Gateway Enterprise Service Manager (Layer 7) STARTER PACK-7 CA Microgateway

Issue/Introduction

This error - Error 1373 (HY000) at line 1: Target log not found in binlog index" comes from when there is a mismatch between the logs and the database place holder as depicted in the screenshot below:

Environment

Release : 9.2

Component : API GATEWAY

Resolution

This error - Error 1373 (HY000) at line 1: Target log not found in binlog index" comes from when there is a mismatch between the logs and the database place holder.

To resolve the issue with the mismatched ssgbin-log files, please follow the instructions below during your maintenance window on both nodes.

These steps will purge all of the logs and reset the indexes.

Also, please take a snapshot of both gateways AND/OR backup both databases

# service mysql stop
# service ssg stop
# find /var/lib/mysql -type f -regextype posix-extended -regex ".*[0-9]{6}" -exec rm -i {} \;
# cat /dev/null > /var/lib/mysql/ssgbin-log.index
# cat /dev/null > /var/lib/mysql/ssgrelay-bin.index
# cat /dev/null > /var/lib/mysql/ssgrelay-bin.info
# service mysql start
# service ssg start

Check and verify your replication is working. If not, you may need to run the restart_replication.sh script (on the primary node).

In the meantime, to free up space in the /var/lib/mysql directory, you can remove older bin logs.

Attachments