Kaspersky Lab Forum > Linux File Server

Full Version: Linux File Server - High CPU

Kaspersky Lab Forum > English User Forum > Protection for Small and Medium Businesses

Kappa Tech

21.08.2008 22:31

I'm getting a consistent high CPU on kav4wk-kavmonit. As you can see below. Its 98%, it stays between 95% and 100% all the time.

CODE

Tasks: 191 total,   2 running, 189 sleeping,   0 stopped,   0 zombie
Cpu(s): 26.6%us, 29.7%sy,  0.0%ni, 43.2%id,  0.3%wa,  0.2%hi,  0.0%si,  0.0%st
Mem:   1034776k total,   948692k used,    86084k free,    27816k buffers
Swap:  2031608k total,   238400k used,  1793208k free,   215692k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
12126 root      20   0  9356 2900 1556 R   98  0.3  87:44.35 kav4ws-kavmonit
15434 root      20   0  142m 1548  832 S   20  0.1  42387:59 linuxagent
1924 root      20   0  508m 132m  15m S    7 13.1   2794:00 java
21904 root      20   0 50312  14m  10m S    2  1.4   6:19.07 klnagent
16241 root      20   0  2388 1064  796 R    1  0.1   0:00.12 top
2009 root      20   0  2604  576  396 S    0  0.1   0:33.68 mcstransd
8359 administ  20   0 42780  13m  12m S    0  1.3 136:30.50 /usr/bin/sealer
8371 administ  20   0 27400 8756 7992 S    0  0.8   1:17.44 clock-applet
    1 root      20   0  2136  592  548 S    0  0.1   2:46.13 init

Anyone know if this is a program bug or something on my end?

vee_zza

21.08.2008 22:56

The amount of kav4fs-kavmonitor process can vary from 5 to (CheckFilesLimit)+4. By default, CheckFilesLimit=20,

so amount of kav4fs-kavmonitor process will be from 5 to 24. It is normal behavior.

Memory and CPU usage depends on type of checked files. If there are a lot of containers (mailbases, multi-level archives and so on) to check, kavmonitor will get more memory. It releases memory then not needed.

Please check which file that kav is monitoring and check config in the .conf file.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.