Skip to main content
qqh452821000
qqh452821000
New Member
November 1, 2019
Solved

high memory of fortigate 300D

  • November 1, 2019
  • 1 reply
  • 2905 views

Hi everyone,

 

We have a Memory Usage problem（89%） here . Our Fortigate 300D which version is 5.4.5.

 

Here are the disa sys top-summary output:

 

PID RSS ^CPU% MEM% FDS TIME+ NAME * 10368 522M 6.6 6.5 263 43:58.40 ipsmonitor [x5] 10395 18M 5.5 0.2 12 00:00.36 sshd [x4] 10385 104M 1.9 1.3 1772 01:31.78 wad [x5] 10386 35M 0.9 0.4 45 19:10.95 scanunitd [x4] 10388 57M 0.9 0.7 15 55:53.17 updated 10371 7M 0.0 0.1 12 01:38.19 fclicense 10372 28M 0.0 0.4 23 58:50.98 forticron 10373 10M 0.0 0.1 15 00:14.76 forticldd 10374 9M 0.0 0.1 42 00:23.81 authd [x3] 10369 7M 0.0 0.1 11 19:52.96 merged_daemons 10376 7M 0.0 0.1 9 00:00.00 httpclid 10377 7M 0.0 0.1 11 00:41.45 radius-das 10378 3G 0.0 [style="background-color: #ff0000;"]43.7[/style] 22 39:10.30 reportd 10379 20M 0.0 0.3 38 55:52.49 sslvpnd [x4] 10380 7M 0.0 0.1 11 01:40.00 info_sslvpnd 10370 9M 0.0 0.1 13 00:31.30 fnbamd 10382 780K 0.0 0.0 4 00:00.00 smbcd 10383 22M 0.0 0.3 122 42:22.91 proxyd [x3] 10384 11M 0.0 0.1 46 06:24.40 voipd 10387 9M 0.0 0.1 42 12:25.70 iked CPU [|||| ] 11.7% Mem [||||||||||||||||||||||||||||||||||| ] 89.0% 7175M/7997M Processes: 20 (running=1 sleeping=137)

 

What we can see is the the  reported process is occupy 43.7%,  however I have already disable local reports..

 

Can anybody please tell how to fix this problem??

Best answer by ede_pfau

hi,

 

I hate to write this but you should consider upgrading. This will be the first thing Support will ask you to do anyways, and they're right. Patch 5 was in no way 'mature' and there are more recent patches available.

And FOS v5.4 is running out of support soon (or is it already?). There are 3 major versions currently supported, v5.6, v6.0 and v6.2, so you can choose.

 

Of course, a reboot will fix the problem for the moment, but how fast will it rise again? As you stated that you don't have local reports enabled I wonder how reportd got started in the first place. Local logging, to memory? I'd avoid that as well.

1 reply

ede_pfau
SuperUser
ede_pfauAnswer
SuperUser
November 1, 2019

hi,

 

I hate to write this but you should consider upgrading. This will be the first thing Support will ask you to do anyways, and they're right. Patch 5 was in no way 'mature' and there are more recent patches available.

And FOS v5.4 is running out of support soon (or is it already?). There are 3 major versions currently supported, v5.6, v6.0 and v6.2, so you can choose.

 

Of course, a reboot will fix the problem for the moment, but how fast will it rise again? As you stated that you don't have local reports enabled I wonder how reportd got started in the first place. Local logging, to memory? I'd avoid that as well.

Terms & ConditionsAccessibility statement