Conserve Mode Problem

[Mohamed_Khalaf]

Dears;

we need an urgent help, we are suffering from "Conserve mode" problem;

The memory and CPU most of the times over 70% which cause this problem but we didn't solve it yet although we did most of the troubleshooting steps which on the fortinet website.

Model: FortiGate 80C

Your quick response will be highly appreciated.

Regards;

Mohamed Khalaf IT Engineer

[ITGuy11]

MikePruett wrote:

ITGuy11 wrote:

I also have a 60E at a branch office that was constantly going into conserve mode.  Working with support for months the only thing that seems to prevent the issue from occurring is to disable logging to memory, which is ridiculous.  There are at most 10 users at this site with a 100/20Mb internet connection and the device can't handle it without going into conserve mode utilizing the default UTM settings.  Very disappointing...

Are you logging every transaction for every policy?

I am only logging security events on a few policies.

[Philippe_ASTIER]

So I'm still exchanging with support, just sent the debug logs this morning.

For now, I disabled AV and use flow-mode so the FTG does not go to conserve anymore.

I'm also logging security events only. Keep in mind the traffic goes over a 4 Mb/s SDSL, with approx. 30 IP devices, all inclusive, so the traffic is very low compared to what this beast should handle. I'm puzzled.

Looking at the logs, it went to Conserve after going through 9 emails, or scanning less than 15 URLs in web filter. It nearly sounds as a joke !!

[ITGuy11]

I have a feeling that there is an underlying hardware issue with the 60/61E that is causing the conserve mode issues.  Several users on Reddit are experiencing the same thing.

[Toshi_Esumi]

My guess is some particular conditions based on the new hardware were not considered properly and causing those seemingly random problems unless it's simple bugs. If that's the case, only fix would come with a new maintenance release. Have you tried 5.4.4 yet?

[FGTuser]

Conserve mode on 60/61E & UTM is known bug of 5.4.3.

Try 5.4.4, should be fixed.