[__cmdb_bg_fork:670] fork( ) failed: 12(Cannot allocate memory)

Forum|Forum|9 years ago
April 18, 2017
18 replies
37464 views

I experience issues on several different FortiGate 60E firewalls with firmware 5.4.2 and 5.4.3.

After a period of uptime I experience that new changes (for example a new created policy) aren't working.

When doing troubleshooting in the cli I get the error "[__cmdb_bg_fork:670] fork( ) failed: 12(Cannot allocate memory)"

When checking memory usage at that time only 60% memory is used.

The firewalls are configured with a simple config. In basic only an allow out policy with some default AV,Application Control and SSL certificate inspection.

I have to reboot the unit to get it resolved for some time until the issues comes back.

Anyone experiencing the same issue or know if this is a know issue with the 5.4.2 and 5.4.3 releases and can confirm it is resolved in 5.4.4 or has a solution for this issue?

MBR

Alex_talmage

New Member

I've just come across this error and similar symptoms.

I'm running 5.4.2, and I've just set up a new interface running a dhcp server. Though the config appears to have stuck, it doesn't actually appear to have taken effect, I cannot ping the new interface, and the dhcp server doesn't appear to be functioning. When I ran diag debug enable, I'm seeing this exact message...

Alex_talmage

New Member

I've just worked around this:

diag sys top

Shows you the top processes. Hit M to sort by memory.

Process wad was consuming 2GB of memory. This runs cache, wan optimization.

Diag sys kill 11 <pid> killed the process. Error has stopped appearing in debug... I've got a ticket open with Fortinet so I will enquire as to why this was using so much resource and report back.