FortiGate
FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
Pedro_FTNT
Staff
Staff
Article Id 337909
Description This article describes how to solve the FortiGate connectivity issue to FortiAnalyzer when debugging shows the message: 'Failed to allocate memory for log queue'.
Scope FortiGate all versions.
Solution

In some situations, the Firewall stops sending logs to the FortiAnalyzer, or the connectivity status changes from connected to disconnected randomly.

 

The article Troubleshooting Tip: FortiGate to FortiAnalyzer connectivity describes how to do a complete troubleshooting.

 

FortiGate fgtlog or miglogd debug process:

 

diag debug app fgtlog 255
diag debug app miglogd 255
diag debug enable

 

If it shows a similar message:

 

_enqueue_lz4()-684: Failed to allocate memory for log queue.
_append_log_text()-741: Failed to allocate memory for log queue.
_enqueue_lz4()-684: Failed to allocate memory for log queue.
_append_log_text()-741: Failed to allocate memory for log queue

 

It is possible to change the miglogd-children configuration:

 

config system global
    set miglogd-children 0 ------> Default value.
end

 

Change it to:

 

config system global
    set miglogd-children 15 <--
end

 

Complete the procedure by restarting fgtlog and miglogd processes:

 

fnsysctl killall miglogd
fnsysctl killall fgtlogd

 

Contact Fortinet TAC Support to do a complete troubleshooting and revision.

 

Related articles: 

Troubleshooting Tip: FortiGate to FortiAnalyzer connectivity

Troubleshooting Tip: FortiGate Logging debugs