Skip to main content
notrixx
New Member
March 23, 2022
Solved

Fortios 7.0.x memory leak?

  • March 23, 2022
  • 11 replies
  • 45836 views

After upgrading our Fortigate 600E (two firewalls in HA) first to FortiOS 7.0.4 then later 7.0.5 we are experiencing what I suspect is memory leak issues.

 

Over time the memory usage goes up gradually to the point where the firewall goes into "conserve mode" and traffic forwarding stops. After reboot (HA failover) the memory usage is back down and then after about three weeks it goes into conserve mode again.

 

Anyone else experiencing the same problems?

Do you think I should just roll back to 6.4.x or wait for the next patch?

 

FG600e_mem_usage.PNG

 

 

 

Best answer by notrixx

The memory usage issues we experienced after upgrading from 6.4.x to 7.0.x seems to have been resolved with upgrading to 7.2.0 so I consider this case closed.

11 replies

NoneEng
Explorer II
January 23, 2024

Well, I'm having the same issue with a 100F at v7.2.5.

WAD decides to consume all RAM, forward traffic dies.

BillH_FTNT
Staff
Staff
January 23, 2024

Hi NoneEng

Could you share more details about your WAD issue? How can it make your traffic issue? Did the memory increase to converse mode? If you already have a ticket, if you don't mind, please share. Do you optimize your memory following this : https://community.fortinet.com/t5/FortiGate/Technical-Tip-Steps-on-how-to-optimize-Memory-consumption/ta-p/192323

Regards

Bill

NoneEng
Explorer II
January 23, 2024

Hello!
Sure: memory was at ~30% most of the time, but in the last days WAD processes started to consume a lot more. Very similar to the graph notrixx (op) posted.

There were many, but 2 or 3 WAD processes were consuming the biggest chunks.

The system went to "converse mode" today, and the traffic halted. Packages were not being forwarded.

After reboot, traffic resumed and RAM sat at 30%, and stayed that way for some hours now.

 

I did not follow most of the tips to reduce Memory utilization, because as I said this gate utilizes ~30% RAM normally; this shouldn't be an issue.

 

edit: forgot to mention I didn't open a ticket for it yet.