Technical Tip: Confirm database replication success event when resuming control to primary FortiNAC server

Description

This article describes how to identify, through the event logs and debug output, whether the secondary FortiNAC server (v7.6.5) is generating 'DatabaseReplicationSuccessEvent' when resuming control to the Primary Server.

Scope

FortiNAC-OS.

Solution

When resuming control to Primary NAC from the Secondary unit's GUI, FortiNAC v7.6.5 in HA will generate 'DatabaseReplicationSuccessEvent succeeded' messages after several resync attempts. The FortiNAC-Sec output.processManager will show 'DatabaseReplicationSuccessEvent succeeded' once the database sync is successful.

fortinac-s:~$ cd /bsc/logs
fortinac-s:/bsc/logs$ grep "DatabaseReplicationSuccessEvent" output.processManager 
2026-02-25 11:00:02.907 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 0
2026-02-25 11:00:17.909 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 1
2026-02-25 11:00:32.911 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 2
2026-02-25 11:00:47.912 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 3
2026-02-25 11:01:02.914 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 4
2026-02-25 11:01:17.915 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 5
2026-02-25 11:01:32.917 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 6
2026-02-25 11:01:47.919 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 7
2026-02-25 11:02:02.923 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent failed, retry 8
2026-02-25 11:02:12.965 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent succeeded
2026-02-25 11:02:12.965 +0100 [ForkJoinPool.commonPool-worker-7] INFO c.b.g.f.s.ActiveActiveStandbyService - genDatabaseReplicationSuccessEvent finished with true>

When database replication has succeeded, the Primary NAC shows the event 'Database replication succeeded' in the GUI under Events & Alarms, as shown in the following screenshot:

Figure 1: Successful Event Generation after resuming control to Primary Server.