Description
This article describes how to refresh database replication in case this error message in the GUI Events appears 'Database Replication Error' or 'slave is inactive' when executing hsIsSlaveActive on the Secondary Server.
Scope
FortiNAC.
Solution
- Login to secondary (not the virtual IP) FortiNAC with SSH client using 'root' account.
- Type in the following command:
# reboot
- Wait for the secondary server to come back online and all services are started, it can take up to 10 minutes, depending on the size of a database.
- Check if database replication is active with the following command (executed on the secondary node):
# hsIsSlaveActive
Expected output:
Host fortinac
SQL version 5.6.39,
slave is active ← This indicates that database replication is active.
- Verify the logs to confirm that database replication started and finished successfully:
# cd /bsc/logs
Open 'output.processManager' with the favorite text editor or use 'less' for example:
# less output.processManager
Search for strings 'Database replication starting' and 'Database replication finished: SUCCESS'.
If Database replication continues to fail:
- Gather logs from both the Primary and Secondary Servers using the grab-log-snapshot script. For instructions see KB article 190755.
- Open a support ticket and provide the following:
- Logs from step 1.
- Output of hsIsSlaveActive command from the Secondary Server.
Related documents:
FortiNAC 8.8 High Availability
FortiNAC 9.2.0 High Availability
FortiNAC 9.4.0 High Availability
FortiNAC-F High Availability
Related articles:
Troubleshooting Tip: Database replication fails due to full disk on secondary appliance.
Technical Note: System will not start up, GUI shows Processes are Down after a power failure or rebo...
