Zabbix Agent 1.4.4 memory leak on Windows 2000?

[Menocu]

I have a few servers on a remote network which I monitor with Zabbix over a VPN. I have observed the zabbix_agentd.e process using an increasing amount of memory, to the point where I have to restart the zabbix service every few days. At one time they got up to about 500MB of memory.

I use only passive checks since these servers cannot source connections to my zabbix server. The servers in question all run Windows 2000.

Are there any known issues with 1.4.4 and Windows 2000? Has anyone else experienced this issue?

[vinny]

Hi,
I have a lot of zabbix agents installed, from 1.4.2 to 1.4.5, but I never saw this behaviour on Win 2k.

did u try the 1.4.5 version of the agent ?
did u try to increase the log level and then restarting the agent, to see if there is any error message ?

[Menocu]

Hi,
I have a lot of zabbix agents installed, from 1.4.2 to 1.4.5, but I never saw this behaviour on Win 2k.

did u try the 1.4.5 version of the agent ?
did u try to increase the log level and then restarting the agent, to see if there is any error message ?

I have not tried 1.4.5. I did change the logging to go to a file instead of the system log, but I haven't upped the log level. I will try that. The only thing different about these servers vs. the other servers I'm monitoring are that they remote and accessed over VPN, don't have the ability to source a connection back to the Zabbix server, are IBM x series servers instead of our standard HP servers, and run Windows 2000. I see an occasional error about getting active checks but I'm assuming that's harmless and caused by the agents trying to check for active checks they may need to do.

What is the normal memory footprint of the Zabbix agent? On one server, it's 2.4MB and on another of my remote servers it's at 177MB. I am guessing 177MB is not normal.

[vinny]

177 mb is not normal
can u give us the configuration of ur agent ?

vinny

[Alexei]

I remember that there was a memory leak in one of Windows DDLs. This was nothing related to the agent itself. The issue has already been discussed on the Forums.