Skip to main content
jbindra
Staff
jbindra
Staff
March 30, 2026

Technical Tip: Secondary device in HA environment consumes high percentage of one CPU core

  • March 30, 2026
  • 0 replies
  • 307 views
Description This article describes a situation where a hasync process in a secondary device can be seen utilizing high percentage of one CPU core. 
Scope FortiOS, FortiManager.
Solution

When FortiGates are configured in HA mode, there may be certain scenarios in which the hasync process on the secondary unit may consume a high percentage of a single CPU core.

 

This behavior is observed only when the FortiGates are managed through FortiManager, particularly in environments where scripts and config is pushed from FortiManager.

 

Verification:

 

To verify this behavior, access the CLI of the secondary device and execute the following commands multiple times:

 

diagnose debug cli 8

diagnose debug enable

 

Example:

 

FGT02 (global) # diagnose debug cli 8 Debug messages will be on for 30 minutes.  FGT02 (global) # diagnose debug enable -61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: ab ort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort FGT02 (global) # -61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort- 61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abo rt-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-6 1: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abor t-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: a bort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61 : abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort -61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: abort-61: ab

 

To stop the debugging, run the following:

 

diagnose debug disable 

 

If the problem is present, the output will display the message 'abort -61'.

 

Workaround:

  1. Restart the hasync process with the command 'fnsysctl killall hasync' or reboot the secondary device. 
  2. When pushing a script through FortiManager, add 'end' at the bottom.

 

This behavior will be fixed in version 8.0.0 of FortiOS.

 

Related document:

Technical Tip: Troubleshooting methodology of hasync process high 
    Terms & ConditionsAccessibility statement