ESET File Security Server for Linux - memory problem

Discussion in 'Other ESET Home Products' started by markopolo1, Jan 26, 2011.

Thread Status:
Not open for further replies.
  1. markopolo1

    markopolo1 Registered Member

    Joined:
    Jan 21, 2011
    Posts:
    5
    Hello,

    I have installed ESET File Security Server 3.0.21 for Linux (RedHat Ready) on Redhat 5 Enterprice.

    I have a problem. ESET is using all physical memory and use SWAP during on-demand scanning. I have 8GB memory in the server.

    It seams like memory leaking or something like that?

    Do you have any idea?
     
  2. markopolo1

    markopolo1 Registered Member

    Joined:
    Jan 21, 2011
    Posts:
    5
    top command show me this information:

    top - 10:25:06 up 3:27, 3 users, load average: 1.17, 0.61, 0.52
    Tasks: 335 total, 2 running, 333 sleeping, 0 stopped, 0 zombie
    Cpu(s): 5.5%us, 0.6%sy, 0.0%ni, 93.8%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st
    Mem: 8037024k total, 7895724k used, 141300k free, 32052k buffers
    Swap: 18490804k total, 248k used, 18490556k free, 7205844k cached

    PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
    8132 esets 25 0 49472 45m 2416 R 99.1 0.6 2:07.90 esets_scan
    1 root 15 0 10356 696 584 S 0.0 0.0 0:02.10 init
    2 root RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/0
    3 root 34 19 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/0
    4 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/0
    5 root RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/1
    6 root 34 19 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/1
    7 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/1
    8 root RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/2
    9 root 34 19 0 0 0 S 0.0 0.0 0:00.00 ksoftirqd/2
    10 root RT -5 0 0 0 S 0.0 0.0 0:00.00 watchdog/2
    11 root RT -5 0 0 0 S 0.0 0.0 0:00.00 migration/3


    You may see using memory above (bolded).
     
    Last edited: Jan 27, 2011
  3. agoretsky

    agoretsky Eset Staff Account

    Joined:
    Apr 4, 2006
    Posts:
    4,032
    Location:
    California
    Hello,

    ESET File Security v3.0.22 was just released, as mentioned here.

    Although the issue you are experiencing is not listed as being fixed in the changelog, could you please try upgrading to this newer version? It could be that the underlying cause is the same.

    Regards,

    Aryeh Goretsky
     
Thread Status:
Not open for further replies.