Description | This article describes how to automatically WAD workers using the built-in mechanism. |
Scope | FortiGate v7.2.4 and onward. |
Solution |
FortiOS version 7.2.4 has introduced a new feature that gives the possibility to configure auto-restart of wad worker.
That option can be configured under 'config system global'.
A restart of a WAD worker can be configured based on the following parameters:
The memory leak detection algorithm works like this:
When 'set wad-restart-mode time' is applied and time reaches the time window defined by wad-restart-start-time and wad-restart-end-time, WAD will gracefully restart;
The default option is 'wad-restart-mode none' which means that there is no automatic WAD restart.
Syntax:
set wad-restart-mode none <- Disable restart of WAD workers. time <- Enable daily restart of WAD workers. memory <- Enable restart of WAD workers based on memory usage.
Restart the WAD in a specific time frame:
config system global set wad-restart-end-time 04:00 set wad-restart-mode time set wad-restart-start-time 01:00 end
Restart the WAD based on memory usage:
config system global set wad-restart-mode memory end
Note: TImportant: This feature is specifically designed for WAD workers. If the issue persists with WAD processes and the solution above does not resolve it, consider using Automation Stitches as an alternative method to restart the processes.
Related documents: Technical Tip: Overview of WAD process structure Technical Tip: Restart WAD or IPS when conserve mode hits (Automation Stitch) Technical Tip: FortiGate Resource Lists
|
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.