Ad Widget

Collapse

Memory leak on zabbixw32 when monitoring MSSQL

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • art
    Junior Member
    • Oct 2006
    • 12

    #1

    Memory leak on zabbixw32 when monitoring MSSQL

    Hi!

    Running zabbix 1.1.6 on linux server and latest windows agents on monitored servers. Discovered that on some windows boxes zabbix agent's memory usage grows steadily over the time reaching over 200Mb -at this stage server becames pretty much unusable. After restarting of zabbix agent memory usage drops, but after couple of weeks zabbix agent is using hundreds Mb of memory again.

    Details:

    Server(s) - IBM x335 with 2Gb of RAM running Win2000 SP2 + MSSQL server 2000 standard edition SP3.

    This only happens on servers with MSSQL installed as any other windows boxes work without any problems.

    The only difference in zabbix configuration between MSSQL servers and other windows boxes is that MSSQL template contains the following items in addition to plain windows template:

    perf_counter[\SQLServer:Buffer Manager\Buffer cache hit ratio]
    perf_counter[\SQLServer:Memory Manager\Target Server Memory(KB)]
    perf_counter[\SQLServer:Memory Manager\Total Server Memory (KB)]

    Is it a known issue? If so are there any workarounds?
  • Alexei
    Founder, CEO
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Sep 2004
    • 5654

    #2
    I remember about similar problem discussed some time ago (year ago?) on ZABBIX Forums which turned to be a memory leak in one of Windows DLLs. I'm not sure if this is exactly the same case though.
    Alexei Vladishev
    Creator of Zabbix, Product manager
    New York | Tokyo | Riga
    My Twitter

    Comment

    • art
      Junior Member
      • Oct 2006
      • 12

      #3
      I believe this Microsoft DLL memory leak was reported for NT4.

      As a UNIX sysadmin I'm not quite familiar with Windows internals and development/debug tools... just wondering if it is possible to trace/debug this memory leak? Maybe there is kind of background debugger/monitor that would trace system calls and provide some clue as to what is actually happening?

      Or maybe it is possible to have zabbixw32 with more detailed logging?

      Comment

      Working...