Error message after upgrade 1.6.1 to 1.6.2 in Agent

[jroberson]

Man speak about meaningless error messages. I have a user 'jason' and I have been trying everything to find out why it was giving me errors!!!

[Alexei]

Man speak about meaningless error messages. I have a user 'jason' and I have been trying everything to find out why it was giving me errors!!!

Make sure you do not have users 'warning', 'error', etc.

[gullevek]

Just to make it clear for all who have this problem

The Hostname variable in the zabbix_agend.conf file needs to be exactly the same name as the Name variable in the Hosts confirugraion in the Admin interface. Do not add any quote characters like " or ' around the name in the zabbix_agentd.conf.

If those two names match, the active check errors will disappear.

For example if you call one host:

Database Server Rose A

then the zabbix_agentd.conf line must be:

Hostname=Database Server Rose A

This way it will work.

[js1]

We're seeing this error as well. And, in most cases, it was a matter of getting the Hostname and GUI Name to match as described.

However, I'm also seeing this error on proxies that shouldn't even be monitoring the host. That is, I have a host configured to be monitored by one of two proxies. But, I get the error on the other proxy:

 31207:20090807:133734 Send list of active checks to [192.168.57.77] failed: host [myhost] not found

The only other possibility I can think of is the Server directive on the agent config. It's suppose to be a comma separated list of proxies and servers IP address that are allowed to talk to the agent. Does the order here matter? BTW, proxies are running 1.6.4 and agents are either 1.6.4 or 1.6.5.

[richlv]

...
The only other possibility I can think of is the Server directive on the agent config. It's suppose to be a comma separated list of proxies and servers IP address that are allowed to talk to the agent. Does the order here matter? BTW, proxies are running 1.6.4 and agents are either 1.6.4 or 1.6.5.

just chiming in on your question. yes, order matters - first, and only the first, host in agentd server directive will be used for sending in active checks (well, and also for querying them)

[xibbaz]

Well I'm getting those errors, but on dicovery. This mean, the host is not defined in the zabbix server nor GUI nor nothing. Since the dicoveries were not taking place, I took a look at the server's log and saw a bunch of those.