Overload CPU

[hbouddine]

Hello,

We have a major issue regarding the Fortigate 100D CPU exceeding 60% and impact the internet usage, people can’t browse as they did before the 27th of March, we looked all over the place to find a solution with no luck, however, we’ve disabled the web filtering and CPU load went back to 4% or 7% at most, so webfiltering is slowing surcharghing the CPU and impacting the internet browsing, in fact, after re-enabling webfilters, internet slows donw gradually until it’s all down. Please not that we’ve not made no changes on our side.

Best regards,

Hicham.

[hbouddine]

For complement, The upgrading to 2.5.7 does not resolved this issue. We are obliged to disable / enable filtering web 3 times per hour to avoid Slow internet accessibility caused by CPU overloa.

[Ralph1973]

what process(es) are consuming your cpu?

diag sys top

[hbouddine]

Hi,

thank you for your reply.

It's the Proxyworker, Here is the result for the command :

FG100D3G14829532 # diag sys top

46U, 0N, 4S, 50I; 3953T, 1673F, 200KF proxyworker 86 R 99.9 2.0 proxyworker 89 R 99.9 2.0 scanunitd 20246 S < 0.9 0.4 scanunitd 20236 S < 0.4 0.4 miglogd 113 S 0.4 0.4 miglogd 2887 S 0.4 0.3 proxyacceptor 85 S 0.4 0.0 sqldb 81 S 0.0 3.5 httpsd 14275 S 0.0 2.8 httpsd 14274 S 0.0 2.5 urlfilter 99 S 0.0 2.5 reportd 82 S 0.0 2.1 updated 90 S 0.0 1.5 pyfcgid 20259 S 0.0 0.7 pyfcgid 20260 S 0.0 0.7 pyfcgid 20261 S 0.0 0.7 pyfcgid 20258 S 0.0 0.7 cmdbsvr 42 S 0.0 0.6 miglogd 64 S 0.0 0.6 ipshelper 3042 S < 0.0 0.5

Thanx :)

[Mikael_A]

Fun thing, had the same thing happen to me a couple of weeks ago with a 60D. Just web filter that is, proxyworker showed up being the cpu thief.

No change in config or user behavior. Just plain slow when we did web filtering.

Though running 5.4 and now 5.4.1 (same problem). Disabled the web filter to avoid problem. Worrysome that it just went bad.