[autodiscovery] Wrong OS recognized through agent

[elgoretto]

Hi,

I began deploying 1.4.2 Zabbix agent on 1/4 of my hosts, but I'm facing a weird problem: hosts with a 1.4.2 Zabbix agent installed are correctly discovered... all but one Windows host which is recognized as a RedHat one by my 1.4.2 Zabbix Server:

Actions:
Windows Conditions:
Service type = "ZABBIX agent"
Discovery status = "Up"
Received value like "Windows"

RedHat Conditions:
Service type = "ZABBIX agent"
Discovery status = "Up"
Received value like "Linux"
Received value like "ELsmp"

And "Host Information" returned by the Zabbix Agent on the "Latest Data" screen is correct:
Windows <HOSTNAME> 5.2.3790 Windows Server 2003 Service Pack 1 Intel IA-32

And it seems to me that there is no ambiguous behaviour to be expected regarding my autodiscovery actions...

I tried to delete, or unlink and manually link the host to the right template and group, but still this host goes to the wrong template/group when autodiscovery starts. No particular message in server logs, except plenty of "XXX is not supported by agent on host <HOSTNAME>" beginning from date of discovery of this host.

Seems.... a bug. Already corrected in pre 1.4.3?

[elgoretto]

I upgraded my zabbix server and the windows host agent version to 1.4.3, and the host OS is still being wrongly recognized. (and I'm pretty sure 1.4.4 won't change anything to my problem, regarding the 2 bugs addressed by this version).

[elgoretto]

Up: I've a new "case" of wrong reported OS. A gentoo box with a 1.4.4 zabbix agent is reported as a FreeBSD one...

In this example, discovery rules aren't supposed to let this confusion happen:

 Auto discovery. BSD servers.	Service type = "ZABBIX agent"
Discovery status = "Up"
Received value like "FreeBSD"

Auto discovery. gentoo servers	Service type = "ZABBIX agent"
Discovery status = "Up"
Received value like "gentoo"

And uname -a on the gentoo box returns:

Linux virtual03 2.6.20-gentoo-r8 #2 SMP Wed Oct 3 10:12:02 CEST 2007 i686 Intel(R) Xeon(TM) MP CPU 2.00GHz GenuineIntel GNU/Linux

I removed the Received value like "Linux" from the gentoo rule as the rule didn't seem to work... And that's still the case.
Agent OS identification fails too often to deploy zabbix agent on each hosts of my infrastructure

[elgoretto]

I have some "news" about this problem (server updated to 1.4.5), with more precise details about where it could came from.

It seems the server is confusing hosts...
Let me explain:
I have 2 FreeBSD zabbix agents in my network, and several Gentoo linux machines (and plenty other Win or Linux servers).

Zabbix server is almost right by detecting exactly 2 FreeBSD boxes trought agent autodiscovery: one is correct but the other supposed FreeBSD has (in zabbix server) the hostname and IP address of a Gentoo linux host. And the real missing FreeBSD hosts (ie the entry in Zabbix server with the right name and @IP) is not detected as a Zabbix agent enabled host.


So, the bug seems not to be a detection problem, but an problem in some sort of index in Zabbix code.
I hope this will help dev team.

--
edit: for testing purpose, I deleted all hosts from zabbix server, but same mistake about the same host during the following autodiscovery phase.

[Alexei]

I believe there are some fixes related to auto-discovery in 1.4.5 and (or) in the very latest pre 1.4.6 code. Please try 1.4.5 for now.

[elgoretto]

Hi Alexei.

Thanks for taking time answering me.

As of writing my last post, my server was already running Zabbix 1.4.5.
So waiting 1.4.6 to see if it's solved.