Troubleshooting Tip: Solve database or replication issues in the secondary node

[ebilcari]

Description	This article describes how to solve database replication issues in the secondary node of an HA cluster.
Scope	FortiNAC (FortiNAC-OS) version 7.2.6 and above.
	Check the status of the database replication in the Process Manager logs from the CLI of the secondary node: diagnose tail -F output.processManager :: #1 :: Database replication starting :: #1 :: Database replication finished: FAIL :: #1 :: Error occurred while checking replication status. exit value = 1 :: #1 :: replica is inactive :: #1 :: Generate database replication event :: #1 :: Database replication starting The logs show that the replication is failing. To clear the condition, initialize the FortiNAC database on the secondary node. IMPORTANT: This step should only be executed on the secondary node. All data written to the database will be erased. From the CLI of the secondary node, run the following command: execute sql initialize The progress and the result can be checked using the same log file: diagnose tail -F output.processManager :: #1 :: Database replication starting :: #1 :: Database replication finished: SUCCES ... :: #1 :: fnacf-sec(Secondary) Primary In Control Idle(false) Max Memory (KBytes) 699,392 Free Memory (KBytes) 680,084 Threads: 3 Up Time: 1 Day 22 Hours 59 Minutes 22 Seconds Time Zone: EDT (UTC-0400) :: #1 :: sendPacket() 10.1.2.81 verb Ping retval = Running - In Control :: #1 :: replication status: Slave_IO_Running: Yes :: #1 :: replication status: Slave_SQL_Running: Yes :: #1 :: replica is active