Fortigate 40F stuck and had to reboot manually

[amitrohilla07]

Hello All,

There are many firewalls which we have upgraded to 7.4.6M from 7.4.5M

now issue reported that firewall stuck and production had to reboot the firewall manually.

we have checked the logs but nothing showed in Crash logs.

6737: 2025-03-06 18:06:34 msg="Kernel exits extreme low memory mode"
6738: 2025-03-06 18:06:34 service=kernel conserve=exit total="1918 MB" used="1555 MB" red="1687 MB"
6739: 2025-03-06 18:06:34 green="1572 MB" msg="Kernel exits memory conserve mode"
6740: 2025-03-07 14:20:18 the killed daemon is /bin/sflowd: status=0x0
6741: 2025-03-19 09:41:34 the killed daemon is /bin/dhcpd: status=0x0
6742: 2025-04-29 10:49:17 the killed daemon is /bin/sflowd: status=0x0
6743: 2025-05-26 19:19:11 the killed daemon is /bin/eap_proxy: status=0x0
6744: 2025-05-30 22:10:28 the killed daemon is /bin/sflowd: status=0x0
6745: 2025-05-30 22:10:37 the killed daemon is /bin/eap_proxy: status=0xd
6746: 2025-05-30 22:10:39 the killed daemon is /bin/eap_proxy: status=0x0
6747: 2025-06-24 09:37:57 the killed daemon is /bin/sflowd: status=0x0
Crash log interval is 3600 seconds
Max crash log line number: 16384

Firewall stuck and had to reboot it on 24th June and nothing there all looks good.

Please help on this.

Thanks

[BillH_FTNT]

Hi amitrohilla07,

The issue seems to be related to memory. Since the device only has 2GB of RAM, I recommend performing memory optimization. You could follow the link here : https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-How-to-optimize-memory-usage-specifi...

If the issue still occurs after that, please post here again — we’ll continue to support you. Thanks

Bill