ServersCheck Memory

JennaJenna
edited March 2010 in Monitoring Software v12 and lower
Our serverscheck applaince keeps going down because the memory goes down to 3%. The only application we have installed is Trend Micro to protect against viruses. Any suggestions on what else I can do to bring it back up?



Thanks,



Jenna

Comments

  • AdministratorAdministrator
    As per license agreement, AV software isn't supported and voids warranty (just as recent as last week we have an AV software generating false positives causing software and OS fail).



    Can you detail per process memory usage? (in the Windows command prompt type following:

    tasklist > list.txt



    This will store it in the list.txt file
  • JennaJenna
    We removed the AV software and here is what I got in my txt file





    Image Name PID Session Name Session# Mem Usage

    ========================= ====== ================ ======== ============

    System Idle Process 0 RDP-Tcp#2 0 16 K

    System 4 RDP-Tcp#2 0 224 K

    smss.exe 472 RDP-Tcp#2 0 400 K

    csrss.exe 528 RDP-Tcp#2 0 4,044 K

    winlogon.exe 556 RDP-Tcp#2 0 4,072 K

    services.exe 600 RDP-Tcp#2 0 3,544 K

    lsass.exe 612 RDP-Tcp#2 0 4,280 K

    svchost.exe 760 RDP-Tcp#2 0 5,404 K

    svchost.exe 808 RDP-Tcp#2 0 4,860 K

    svchost.exe 900 RDP-Tcp#2 0 19,468 K

    svchost.exe 1028 RDP-Tcp#2 0 3,560 K

    svchost.exe 1084 RDP-Tcp#2 0 3,228 K

    spoolsv.exe 1252 RDP-Tcp#2 0 6,564 K

    svchost.exe 1400 RDP-Tcp#2 0 4,160 K

    msdtc.exe 1452 RDP-Tcp#2 0 4,984 K

    svchost.exe 1572 RDP-Tcp#2 0 6,868 K

    ChgService.exe 1592 RDP-Tcp#2 0 1,936 K

    DUAgent.exe 1632 RDP-Tcp#2 0 1,172 K

    scardsvr.exe 1748 RDP-Tcp#2 0 2,592 K

    snmp.exe 1856 RDP-Tcp#2 0 3,356 K

    tsvc.exe 1904 RDP-Tcp#2 0 1,796 K

    mqsvc.exe 1964 RDP-Tcp#2 0 7,028 K

    alg.exe 112 RDP-Tcp#2 0 3,568 K

    csrss.exe 1180 Console 3 2,192 K

    winlogon.exe 1324 Console 3 5,904 K

    rdpclip.exe 1980 RDP-Tcp#2 0 3,900 K

    explorer.exe 160 RDP-Tcp#2 0 17,212 K

    VTTimer.exe 960 RDP-Tcp#2 0 1,700 K

    server-service.exe 2180 RDP-Tcp#2 0 3,904 K

    s-server.exe 2196 RDP-Tcp#2 0 73,112 K

    wmiprvse.exe 2320 RDP-Tcp#2 0 7,000 K

    s-service.exe 2380 RDP-Tcp#2 0 4,064 K

    s-alerts.exe 2396 RDP-Tcp#2 0 37,304 K

    s-graphs.exe 2404 RDP-Tcp#2 0 7,616 K

    monitoring_snmptrap.exe 2416 RDP-Tcp#2 0 32,480 K

    monitoring_manager.exe 2424 RDP-Tcp#2 0 20,936 K

    monitoring_watcher.exe 2436 RDP-Tcp#2 0 6,544 K

    monitoring_thread2.exe 2540 RDP-Tcp#2 0 259,172 K

    monitoring_security.exe 2548 RDP-Tcp#2 0 18,572 K

    iexplore.exe 3204 RDP-Tcp#2 0 49,012 K

    s-scan.exe 3632 RDP-Tcp#2 0 205,636 K

    monitoring_rule.exe 120 RDP-Tcp#2 0 52,008 K

    cmd.exe 1668 RDP-Tcp#2 0 2,824 K

    tasklist.exe 1284 RDP-Tcp#2 0 4,444 K





    THANKS!
  • AdministratorAdministrator
    Browser shouldn't be used on the appliance unless configuring (iexplore.exe process). Kill the s-scan.exe process
  • JennaJenna
    Well that did it! I shouldn't have to kill that process a lot correct?
  • JennaJenna
    I am having the same issue again but the s-scan.exe process is not running. Here is a detailed memory usage





    Image Name PID Session Name Session# Mem Usage

    ========================= ====== ================ ======== ============

    System Idle Process 0 RDP-Tcp#31 0 16 K

    System 4 RDP-Tcp#31 0 48 K

    smss.exe 472 RDP-Tcp#31 0 216 K

    csrss.exe 528 RDP-Tcp#31 0 2,480 K

    winlogon.exe 552 RDP-Tcp#31 0 5,304 K

    services.exe 596 RDP-Tcp#31 0 3,660 K

    lsass.exe 608 RDP-Tcp#31 0 4,756 K

    svchost.exe 756 RDP-Tcp#31 0 2,012 K

    svchost.exe 804 RDP-Tcp#31 0 2,288 K

    svchost.exe 900 RDP-Tcp#31 0 17,700 K

    svchost.exe 1012 RDP-Tcp#31 0 1,220 K

    svchost.exe 1052 RDP-Tcp#31 0 764 K

    spoolsv.exe 1240 RDP-Tcp#31 0 4,080 K

    svchost.exe 1400 RDP-Tcp#31 0 1,488 K

    msdtc.exe 1452 RDP-Tcp#31 0 704 K

    svchost.exe 1580 RDP-Tcp#31 0 5,380 K

    ChgService.exe 1596 RDP-Tcp#31 0 856 K

    DUAgent.exe 1628 RDP-Tcp#31 0 376 K

    scardsvr.exe 1716 RDP-Tcp#31 0 344 K

    s-service.exe 1800 RDP-Tcp#31 0 1,600 K

    s-alerts.exe 1872 RDP-Tcp#31 0 6,020 K

    server-service.exe 1880 RDP-Tcp#31 0 1,004 K

    s-graphs.exe 1884 RDP-Tcp#31 0 2,456 K

    monitoring_snmptrap.exe 1900 RDP-Tcp#31 0 4,864 K

    monitoring_manager.exe 1908 RDP-Tcp#31 0 10,188 K

    monitoring_watcher.exe 1920 RDP-Tcp#31 0 4,176 K

    s-server.exe 1936 RDP-Tcp#31 0 20,220 K

    snmp.exe 1940 RDP-Tcp#31 0 664 K

    tsvc.exe 1980 RDP-Tcp#31 0 280 K

    mqsvc.exe 2044 RDP-Tcp#31 0 1,324 K

    alg.exe 1144 RDP-Tcp#31 0 392 K

    monitoring_thread2.exe 1512 RDP-Tcp#31 0 215,260 K

    monitoring_security.exe 1528 RDP-Tcp#31 0 1,520 K

    csrss.exe 4060 Console 3 200 K

    winlogon.exe 2356 Console 3 1,024 K

    wmiprvse.exe 408 RDP-Tcp#31 0 5,832 K

    rdpclip.exe 2584 RDP-Tcp#31 0 3,740 K

    explorer.exe 2188 RDP-Tcp#31 0 12,248 K

    VTTimer.exe 3080 RDP-Tcp#31 0 1,488 K

    iexplore.exe 2028 RDP-Tcp#31 0 36,804 K

    wuauclt.exe 2400 RDP-Tcp#31 0 3,884 K

    cmd.exe 3476 RDP-Tcp#31 0 2,844 K

    sensor_check.exe 480 RDP-Tcp#31 0 8,096 K

    tasklist.exe 2680 RDP-Tcp#31 0 4,276 K
  • AdministratorAdministrator
    Memory usage is roughly around 512MB which is ok.
This discussion has been closed.