Windows Server 2008 agent high memory

[bimind]

I have two Windows Server 2008 Standard Edition and both have the agent high memory. When I start the agent service that start with 10 Mb but after several days increases to 500 Mb.

I tested the agents versions 1.6.2 (32 / 64 bits) and 1.42 (32 / 64 bits).

Any ideas ???

Thanks,

Oriol

[Cray]

Hi,

I've actually been monitoring 2 windows 2008 server (one x86 and one x64), without any memory issue (3MB occupied on the x86, and 12MB occupied on the x64).

The servers have now been monitored for 5 days.

How long exactly is 'several days' in your case ?

[NOB]

I have two Windows Server 2008 Standard Edition and both have the agent high memory. When I start the agent service that start with 10 Mb but after several days increases to 500 Mb.

I tested the agents versions 1.6.2 (32 / 64 bits) and 1.42 (32 / 64 bits).

Any ideas ???

Thanks,

Oriol

Hi

as any commercial company will tell you: Update to the latest version
or don't use 1.4.2 any more.
There are several issues which have been fixed in 1.4.6.
So use the latest version.
We are running 1.4.5 and 1.4.6 agents on different Windows-OSs in 32-bit and
64-bit versions. No problem whatsoever with memory allocation.

We don't run the 1.6.2 agents, yet, so I can't comment on that version.
I'll try a pre-1.6.3 agent in the near future.
Most of our servers are running 1.4.6 and 1.4.7 (not released, but
we needed the SourceIP feature and modified it for inter-node comms).

Regards

Norbert.

[bimind]

Hi,

The memory up about 1 Mb every 30 minuts.

Thanks

[NOB]

Hi

so, what's in the logfile ?

If you used the windows installer package, the logging is effectively disabled by setting the DebugLevel in the configuration file to 0.
Add a LogFile in the agent configuration file and set the DebugLevel
to, at least, 3 (or 4).

Look at the logfile, there will be some useful information in there, I guess.

Usually, memory leaks which are noticed by a few people will happen in
case of errors and not freeing memory.

HTH,

Norbert.

[bimind]

Hi,

The result of the log is the next:

4660:20090324:112948 zabbix_agentd started. ZABBIX 1.6.2.
2944:20090324:112948 zabbix_agentd collector started
3308:20090324:112948 zabbix_agentd listener started
3492:20090324:112948 zabbix_agentd listener started
3356:20090324:112948 zabbix_agentd active check started [zabbix.bimind.local:10051]
3312:20090324:112948 zabbix_agentd listener started
3356:20090324:112949 Info from server: Processed 1 Failed 0 Total 1 Seconds spent 0.020000
3356:20090324:112949 OK
3356:20090324:113019 Info from server: Processed 1 Failed 0 Total 1 Seconds spent 0.060000
3356:20090324:113019 OK

[vnz]

Hi,

I have the very same problem on 2 Windows x64 Server 2008 Standard Edition using zabbix_agentd.exe 1.6.2. Restarted with loglevel=2, waiting for significant errors.

server A: 272Mo (running 96 days)
server B: 1,5Go (running 48 days...)

Both have 32Go total ram.

No problem with 1.6.2 on five Windows Server 2003, process is ~7Mo. Seems to only be a problem with 2008, items/triggers identical on both 2003 and 2008 servers.

[NOB]

Hi,

The result of the log is the next:

4660:20090324:112948 zabbix_agentd started. ZABBIX 1.6.2.
2944:20090324:112948 zabbix_agentd collector started
3308:20090324:112948 zabbix_agentd listener started
3492:20090324:112948 zabbix_agentd listener started
3356:20090324:112948 zabbix_agentd active check started [zabbix.bimind.local:10051]
3312:20090324:112948 zabbix_agentd listener started
3356:20090324:112949 Info from server: Processed 1 Failed 0 Total 1 Seconds spent 0.020000
3356:20090324:112949 OK
3356:20090324:113019 Info from server: Processed 1 Failed 0 Total 1 Seconds spent 0.060000
3356:20090324:113019 OK

It seems nothing interesting in there. I guess, real errors would have been
reported in this file.

But there is hope: this problem was registered in the list of bugs to inspect as ZBX-809.

Regards

Norbert.

[vnz]

But there is hope: this problem was registered in the list of bugs to inspect as ZBX-809.

Great thank you.

My actual log (lvl2) on server A:

2404:20090324:125520 zabbix_agentd started. ZABBIX 1.6.2.
4848:20090324:125520 zabbix_agentd collector started
2332:20090324:125520 zabbix_agentd listener started
4252:20090324:125520 zabbix_agentd listener started
1544:20090324:125520 zabbix_agentd listener started
3548:20090324:125520 zabbix_agentd active check started [10.20.30.40:10051]


2009/03/25 12:00 Zabbix_agentd.exe: 41Mo

[richlv]

for the record, it's already fixed in svn

[vnz]

I've tested zabbix_agentd.exe 1.6.4 on the same servers: same problems.

process is 55 Mo after 24h