Serverscheck consumes 1,5Gb memory

Jos_H&RJos_H&R
edited June 2006 in Monitoring Software v12 and lower
On our server, serverscheck consumes 1.5 Gb internal memory, resulting in slowing down the server because it has only 2Gb available and for 2.4 Gb processes running. After rebooting the server the situation comes back within two days. What is happening? and how can this be avoided?

Comments

  • tdanseytdansey
    Juts a FYI: I have just upgraded from 256Mb to 1Gb - we were only using it as a file server so previously it didn't matter too much - and the change in performance is very noticable.



    The server has a 3.2Ghz Pentium running server 2003.

    It also appears to have got rid of some of the more spurious programme errors that we were experiencing.


  • AdministratorAdministrator
    Jos_H&R,



    can you detail what processes uses what amount of memory.



    Is your system a dedicated one?
  • Jos_H&RJos_H&R
    Quote: Originally posted by Administrator on 21 June 2006

    Jos_H&R,



    can you detail what processes uses what amount of memory.



    Is your system a dedicated one?

    It is a dedicated database and file windows 2003 server. Besides monitoring_manager and several monitoring_rules, only ntdbsmgr.exe ocupies a lot of memory(0.5Gb). the monitoring software about 1.5Gb.



    we defined about 50 rules varying from checks from 60 seconds to 900 seconds.



    When rebooting the server the monitoring software occupies about 0.4Gb of memory, but this seems to grow to 1.5Gb in several days.



    Sincerely,



    Jos


  • AdministratorAdministrator
    As requested in previous post, can you please detail per process how much memory is being used?



    monitoring_rule thread 1 X MB

    monitoring_rule thread 2 X MB

    monitoring_rule thread 3 X MB

    ...






  • Jos_H&RJos_H&R
    Quote: Originally posted by Administrator on 22 June 2006

    As requested in previous post, can you please detail per process how much memory is being used?



    monitoring_rule thread 1 X MB

    monitoring_rule thread 2 X MB

    monitoring_rule thread 3 X MB

    ...

    I have added an image.

    We have rebooted the server last night.



    Jos







    image
  • AdministratorAdministrator
    There seems to be an ackward issue with the monitoring_manager.exe



    Could you login into the helpdesk and send your serverscheck.conf file so that we can replicate your environment.



    The monitoring_manager component should not take more than around 20-40 MB of RAM instead of the almost 400 you have.
  • Jos_H&RJos_H&R
    Quote: Originally posted by Administrator on 22 June 2006

    There seems to be an ackward issue with the monitoring_manager.exe



    Could you login into the helpdesk and send your serverscheck.conf file so that we can replicate your environment.



    The monitoring_manager component should not take more than around 20-40 MB of RAM instead of the almost 400 you have.

    Done!



    I have send the conf file to the helpdesk.



    Jos
  • AdministratorAdministrator
    The helpdesk will now take over the lead from here. They will communicate with you directly.



    When the issue has been found / resolved then I will post an update in forum.
  • Jos_H&RJos_H&R
    Quote: Originally posted by Administrator on 22 June 2006

    There seems to be an ackward issue with the monitoring_manager.exe



    Could you login into the helpdesk and send your serverscheck.conf file so that we can replicate your environment.



    The monitoring_manager component should not take more than around 20-40 MB of RAM instead of the almost 400 you have.

    I have take a new snap from the taskmanager and you can see how the internal memory grows only in one day.



    Jos



    image
  • AdministratorAdministrator
    Something must be wrong on your machine because we have it now running for one day with your configuration and it is only 22.944 MB



    Can you install it on a Windows XP machine.


  • Jos_H&RJos_H&R
    Quote: Originally posted by Administrator on 23 June 2006

    Something must be wrong on your machine because we have it now running for one day with your configuration and it is only 22.944 MB



    Can you install it on a Windows XP machine.





    That is okay, but there is nothing wrong with that machine because it is managed by many processes and is a Compaq Proliant ML350 with two processes and 2Gb internal memory working for almost a year with no troubles. That is why we bought a MX 2 version of your software. Is that maybe the problem.



    It is easier to say that your software does not run on a dual CPU windows 2003 server.



    How can I transfer the serverscheck with its current configuration and databases to another server without typing a whole new list of checks



    Jos


  • AdministratorAdministrator
    Dear Sir,



    "It is easier to say that your software does not run on a dual CPU windows 2003 server."

    => that is a harsh statement to make. Our demo server with live screen shots runs on a Windows 2003 server.



    We have done benchmarking with Intel on 4 way CPU systems and they do not reporte the same issue.





    To move a configuration see knowledge base:

    http://kb.serverscheck.com/index.php?page=index_v2&id=11&c=5


  • AdministratorAdministrator
    We ran it on a 4 way W2K3 machine during the whole weekend with your config and the monitoring_manager.exe behaved like expected.



    As we could not replicate the issue, our development team has worked hard over the weekend to include a work-around in release 6.4.4 (released this morning).



    In the monitoring_watcher an additional controller is built-in that checks the memory state of the monitoring_manager.exe



    If it exceeds 120 MB then it is automatically restarted. This does not affect the monitoring.
This discussion has been closed.