Skip to main content
Jackie_T
Staff & Editor
Staff & Editor
April 7, 2026

Troubleshooting Tip: HA Synchronization Errors on FortiPAM nodes

  • April 7, 2026
  • 0 replies
  • 126 views
Description

This article describes the steps to troubleshoot HA synchronization errors on FortiPAM nodes. The user may experience intermittent sync issues, and the cluster may lose sync from time to time due to these errors.

Scope FortiPAM.
Solution

On FortiPAM, when running debug for HA:

 

diagnose debug reset

diagnose debug application hasync -1

diagnose debug application hatalk -1

diagnose debug enable

execute ha sync start

 

The following error is seen from the debug output:

 

pam # <hasync> installUpdObjRest[717]-Failed to backup orig file /data2/uwdb to /tmp/update.backup

[_ha_slave_receive_return_msg:1634] Synchronize file /data2/uwdb failed!

<hasync> upd_cfg_extract_av_db_version[376]-Failed av db version, obj 31

<hatalk> vcluster_0: ha_prio=1(secondary), state/chg_time/now=3(standby)/1756123656/1756376436

<hasync> installUpdObjRest[713]-Step 5:Backup /data2/avai->/tmp/update.backup

<hasync> installUpdObjRest[717]-Failed to backup orig file /data2/avai to /tmp/update.backup

[_ha_slave_receive_return_msg:1634] Synchronize file /data2/avai failed!

<hasync> installUpdObjRest[713]-Step 5:Backup /data2/ffdb_pkg.tar->/tmp/update.backup

<hatalk> vcluster_0: ha_prio=1(secondary), state/chg_time/now=3(standby)/1756123656/1756376446

<hasync> installUpdObjRest[717]-Failed to backup orig file /data2/ffdb_pkg.tar to /tmp/update.backup

[_ha_slave_receive_return_msg:1634] Synchronize file /data2/ffdb_pkg.tar failed!

<hasync> installUpdObjRest[713]-Step 5:Backup /data2/uwdb->/tmp/update.backup

pam # <hasync> installUpdObjRest[717]-Failed to backup orig file /data2/uwdb to /tmp/update.backup

pam # [_ha_slave_receive_return_msg:1634] Synchronize file /data2/uwdb failed!

 

To troubleshoot the above error, follow these steps:

  1. Ensure both FortiPAM nodes are running on the same virtualization environment. The FortiPAM nodes should be deployed on the same virtualization platform; cross-platform is not supported. For example, if node 1 is deployed on VMware and node 2 is deployed on Hyper-V, it will not work and will give the above error or unexpected behaviour.
  2. Verify that both nodes have the same UTM contracts.