Hello everyone,
I have been using zabbix for about a year now and I'm pretty satisifed with it, had some performance problems with the database at first but everything is fine now. (except a few things like UTF8 for exemple for collecting Windows counters on French based systems ^^)
Anyways back to the topic, I have an agent on one of my machines that stops returning system.cpu.util data. It actually doesn't really stop it just returns 0 for like 30min and then starts again to report correct values. All other keys are reporting fine (Rereading myself, i'm actually not quite sure about that one anymore but I know for sure i had this problem multiple times for this particular CPU key)
Here are the specs :
- Virtualised (on ESX 4) Debian Etch X86 system (fully updated, stock kernel)
- 2 processors
- 1G of RAM
- Enough disk space
- Zabbix server and frontend version : 1.6.5-1 (compiled from debian SID sources)
- Zabbix agent version : 1.6.1-2
- Agent uses active check (at least in the conf, how can you check if it's really working ?)
- StartAgents=10 (upped that just in case)
Telnet from and to the agent / server works and reports no error. There's nothing particular in the log, I am only at debug level3 for now as this happens randomly..
Did anyone experience this problem ? Did you fix it ?
I can't seem to isntall the newest version of the agent because it requires a newer version of libldap that I can't install (because still using debian etch) but at the same time I don't recall having any problems before.. I'm starting to wonder if it might be related to the fact that we are running this VM on ESX ?
Thanks !
edit : I have managed to install the newest version available for debian 1.6.5-1 even though my LDAP libraries are 2.3 and not 2.4
I have been using zabbix for about a year now and I'm pretty satisifed with it, had some performance problems with the database at first but everything is fine now. (except a few things like UTF8 for exemple for collecting Windows counters on French based systems ^^)
Anyways back to the topic, I have an agent on one of my machines that stops returning system.cpu.util data. It actually doesn't really stop it just returns 0 for like 30min and then starts again to report correct values. All other keys are reporting fine (Rereading myself, i'm actually not quite sure about that one anymore but I know for sure i had this problem multiple times for this particular CPU key)
Here are the specs :
- Virtualised (on ESX 4) Debian Etch X86 system (fully updated, stock kernel)
- 2 processors
- 1G of RAM
- Enough disk space
- Zabbix server and frontend version : 1.6.5-1 (compiled from debian SID sources)
- Zabbix agent version : 1.6.1-2
- Agent uses active check (at least in the conf, how can you check if it's really working ?)
- StartAgents=10 (upped that just in case)
Telnet from and to the agent / server works and reports no error. There's nothing particular in the log, I am only at debug level3 for now as this happens randomly..
Did anyone experience this problem ? Did you fix it ?
I can't seem to isntall the newest version of the agent because it requires a newer version of libldap that I can't install (because still using debian etch) but at the same time I don't recall having any problems before.. I'm starting to wonder if it might be related to the fact that we are running this VM on ESX ?
Thanks !
edit : I have managed to install the newest version available for debian 1.6.5-1 even though my LDAP libraries are 2.3 and not 2.4
Comment