View Full Version : Getting "unknown host:" in server log
bkowalewski
02-12-2009, 18:46
Help..
We are running 1.6.6 on Solaris 10 with MySQL. In the ZABBIX server log, we're getting a huge amount of these type of errors:
unknown host: samplehost
The hostnames it is displaying have been monitored successfully for some time. In 3 hours, we have gotten around 200 of these errors; we have around 1800 hosts monitored.
HELP!!!!!!!!! Has anyone seen this...?? This is crippling our monitoring....
Try increasing the debug level in your zabbix_server.conf.
Also helpful is to cut and paste the actual error.
MrKen
bkowalewski
03-12-2009, 14:11
Thanks for the reply, but what I have in my original message is actually the entire line from the log, of course with a different hostname in the message.
Also, decreasing the debug level is like putting my head in the sand. The error will not go away because the error message is not displayed.
Nobody has ever seen this error message??
Hi bkowalewski
Thanks for the reply, but what I have in my original message is actually the entire line from the log, of course with a different hostname in the message.
Also, decreasing the debug level is like putting my head in the sand. The error will not go away because the error message is not displayed.
Nobody has ever seen this error message??
Sure. We had that happen after upgrading from 1.4.6 to 1.6.6.
Now the hostnames are suddenly case-sensitive, even with MySQL
database.
So, if you have the hostnames in your zabbix GUI in all lower-case
and the hostnames in the agent configuration file(s) are in upper-case (or v.v.) this might
show up.
You'll have to correct the spelling and everything will be fine.
You can proof whether this is the case by looking at the "Latest data"
for these hosts and the values for the "active" checks.
They should not get updated. If you have current data entries
this might be a different problem.
HTH,
Norbert.
bkowalewski
07-12-2009, 17:49
Thanks for the reply.
I found it. It was an error in an action script I use to resolve hostnames before sending a trap to NNM.