100% CPU Usage

[Kess]

Hi guys, every 1 - 2 days it happens that my FG80C can' t manage anymore the WiFi Accesspoints because the process cw_acd takes the Whole CPU for him (100%). I can just reboot in order to fix the issue. Do you have a solution ? FW vers: 5.0.2 Thx, bye Kess. diag sys top:

Run Time:  1 days, 19 hours and 47 minutes
  
 63U, 36S, 1I; 1008T, 652F, 141KF
  
           cw_acd       92      R      99.0     1.3
  
           newcli      202      R       0.9     1.1
  
        ipsengine       62      S <     0.0     5.8
  
          pyfcgid       99      S       0.0     2.4
  
          pyfcgid       98      S       0.0     2.2
  
          pyfcgid       97      S       0.0     2.2
  
           httpsd      103      S       0.0     1.9
  
          pyfcgid       47      S       0.0     1.9
  
        scanunitd      183      S <     0.0     1.8
  
          cmdbsvr       33      S       0.0     1.7
  
           httpsd      104      S       0.0     1.7
  
           httpsd      187      S       0.0     1.6
  
           httpsd      185      S       0.0     1.6
  
        scanunitd      184      S <     0.0     1.6
  
           httpsd      186      S       0.0     1.6
  
           httpsd      199      S       0.0     1.6
  
           httpsd      196      S       0.0     1.6
  
          sslvpnd       75      S       0.0     1.5
  
          miglogd       40      S       0.0     1.5
  
      proxyworker       54      S       0.0     1.4
  
 

diag hard sysinfo cpu:

processor	: 0
  
 vendor_id	: GenuineIntel
  
 cpu family	: 6
  
 model		: 5
  
 model name	: Celeron (Covington)
  
 stepping	: 0
  
 cpu MHz		: 600.039
  
 cache size	: 64 KB
  
 fdiv_bug	: no
  
 hlt_bug		: no
  
 f00f_bug	: no
  
 coma_bug	: no
  
 fpu		: yes
  
 fpu_exception	: yes
  
 cpuid level	: 2
  
 wp		: yes
  
 flags		: fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe
  
 bogomips	: 1196.03
  
 

diag hard sysinfo memory:

total:    used:    free:  shared: buffers:  cached: shm:
  
 Mem:  1057845248 367656960 690188288        0 20307968 171405312 148180992
  
 Swap:        0        0        0
  
 MemTotal:      1033052 kB
  
 MemFree:        674012 kB
  
 MemShared:           0 kB
  
 Buffers:         19832 kB
  
 Cached:         167388 kB
  
 SwapCached:          0 kB
  
 Active:          87188 kB
  
 Inactive:       100108 kB
  
 HighTotal:      131072 kB
  
 HighFree:            4 kB
  
 LowTotal:       901980 kB
  
 LowFree:        674008 kB
  
 SwapTotal:           0 kB
  
 SwapFree:            0 kB
  
 

[pcraponi]

5.0 release are not so stable yet... You will solve 99% of your problems using 4.3.12 or newer releases... Regards, Paulo Raponi

[Kess]

Hello Paulo, thx for your reply. I know that 5.0 is not yot so stable as 4.3.x, but I' d like to use it for testing purposes also. It has been installed in a production environment in order to be tested, but not in a mission critical one, so I know (and the customer knows) that there could be some issues with this software versions. I' d like to help Fortinet in resolving such issues in order to push the 5.x version in a nearly " error free" version. Please let me know how I can debug this kind of error. Thnyk you, bye Kess.

[pcraponi]

Hi Kess, " cw_acd" process that using 99% of CPU are the Wireless Controller daemon. All Wireless funciton are managed by it. Can you post your cli wifi configuration here? What model of FortiAP are you using? On next May 15 patch3 will be released with a lot of bug fix and improvements... Like it' s a new firmware, are always the best choice you open a support case with Fortinet. TAC will help you better than me. Regards, Paulo Raponi

[deandb]

Hi, We' ve had a ticket open for this behavior in FortiOS 5.0.2, and they told us it was the rogue AP scanning feature, so we turned it off. We haven' t had the issue anymore since. Now today at another customer we have the same behavior, on the same release, with the rogue ap scanning turned off. But when i check their event logs, I find rogue ap detection messages, even though the GUI says it' s turned off. We' ll see what the ticket feedback gives. Greets, Dean.