Skip to main content
bstefanovski
Staff
Staff
February 16, 2026

Technical Tip: High Memory Utilization on FortiGate by 'zebos_launcher'

  • February 16, 2026
  • 0 replies
  • 312 views
Description

This article describes a solution to high memory utilization on FortiGate devices by the zebos_launcher process.

Scope

FortiGate.

Solution

To resolve high memory utilization on FortiGate, follow these steps:

  1. Run the 'get system status' command to check the current system status.
  2. Run the command diagnose system top-mem 10 to check the top 10 memory-using processes, or diagnose system top 5 40 (Press 'm' to sort by memory, 'p' to sort by CPU, and 'q' to quit - let it run for 10-15 seconds).
  3. Identify the process causing high memory utilization. In this case, the zebos_launcher process was using excessive memory.
  4. Run the command fnsysctl killall zebos_launcher to kill the process. 
  5. If the device is part of an HA cluster, reboot the device and put it back in the cluster during a downtime window. It is recommended to kill the process during a downtime window during situations where the whole network is likely to be affected by killing the process.

 

zebos_launcher: Launcher daemon for the ZebOS routing software (handles routing tables on the FortiGate). 

 

It manages dynamic routing protocols, such as:

  • BGP.

  • OSPF.

  • RIP.

  • IS-IS.

 

For example:

 

newcli 23959 R 0.4 0.4 2
zebos_launcher 196 S 0.0 20.6 6
hasync 252 S < 0.0 2.6 4

 

Note: If the steps above did not help, open a ticket with Fortinet TAC.

 

For a list of processes, see Technical Tip: Short list of processes on the FortiGate.