Discovery not added to new hosts

[siili]

I have recently installed 2.0.8 server, proxy and agents. Previously I was running 1.8. I noticed some Windows servers were grayed out in the Availability icons and some were not. On closer examination I found the ones that were grayed out had 33 items versus 43 for the ones that had green icons. I further noticed the grayed out ones had "Discovery rules (0)" and the others had "Discovery rules (2)". How did some host configurations get discovery rules and some not? How do I add them to the ones that do not have them?

Regards,
David Koski
[email protected]

[steveboyson]

Discovery is supported with Zabbix agents 2.0 only. If you still have 1.8 agents then these items will be missing.

SNMP discovery however works also with 1.8 agents.

[siili]

Thank you, but I have 2.0.8 installed on all agents and the proxy communicating with this 2.0.8 Zabbix server.

Regards,
David Koski
[email protected]

[steveboyson]

Well, then I would suggest a

zabbix_agentd -p

on the affected systems. Please make sure you run it as the user under which zabbix_agentd is running.

Then check what the discovery is returning (key: vfs.fs.discovery)

Hope that helps ...

[siili]

zabbix_agentd was running as SYSTEM and I ran "zabbix_agentd -p" as administrator. I then ran zabbix_agentd as administrator and ran the command again. vfs.fs.discovery is listed.

Update: I ran "zabbix_agentd -t vfs.fs.discovery and got:

vfs.fs.discovery                              [s|{
        "data":[
                {
                        "{#FSNAME}":"C:",
                        "{#FSTYPE}":"NTFS"},
                {
                        "{#FSNAME}":"D:",
                        "{#FSTYPE}":"UNKNOWN"},
                {
                        "{#FSNAME}":"E:",
                        "{#FSTYPE}":"NTFS"}]}]

Update2: I also ran:

>zabbix_get -s 127.0.0.1 -k vfs.fs.size[/,free]
zabbix_get [5032]: Get value error: ZBX_TCP_READ() failed: [0x00002746] An existing connection was forcibly closed by the remote host.

Regards,
David Koski
[email protected]

[steveboyson]

Hmmm. That looks wierd.

You shoud test the local zabbix_agentd by connecting to the LAN interface rather than using 127.0.0.1 since your Zabbix server will also use that LAN interface.

Could it be that some Windows firewall rules restrict access to tcp/10050 on your LAN interface?

You might want to check that via nmap or "telnet <your_lan_ip> 10050".

Also, for a test, you might end the service and start the zabbix_agentd.exe in a command window (with your current user id) and then test from a second command window what it responds.

Additionally, assign a user id to the service instead of running it under SYSTEM, restart the service and test again.

Sorry, no more clues right now :-(

[steveboyson]

Oh, one more. Maybe you want to try an older client (2.0.7) and test that one.

[siili]

I installed 2.0.8 agent on the Windows server with the same results. Telnet works from every angle as it did before. However, the zabbix_command succeeds when executed from the Zabbix server. Previously I had tried from the Windows host and it failed.

I deleted and created the failing host in Zabbix server. Still, there is "Discovery (0)" in the Discovery column. I did not add discovery to any other host but the ones that work correctly have had them automatically created and I can see no way to manually create them except for completely defining them, not in some pick list.

Regards,
David Koski
[email protected]

[steveboyson]

Maybe the interval for the discovery rule was not yet reached?

You could increase the debug levels to the max, both on zabbix agent as well as on zabbix server side and see what happens.

Your eventlogs on the windows boxes look good so far? Just to confirm that this is not a windows related issue.

Sorry, I'm really out of ideas now.

[siili]

I turned up logging on the agent and server and found nothing useful. On closer look, I found that my template "Template OS Windows Active" has no "Discovery rules" but "Template OS Windows Active" does. I am using Windows logging so I have to have the active template.

Edit: There was nothing interesting in the Windows logs.

Edit2: How to add discovery to the template? Why is it not there? Should it be?

Edit3: Looks like I need to find a better template file?

Regards,
David Koski
[email protected]

[steveboyson]

... I found that my template "Template OS Windows Active" has no "Discovery rules" but "Template OS Windows Active" does. ...

Huh? Didn't understand that.

Discovery rules can not be copied between Templates or hosts unlike other items. Best would be either to manually rebuild it on your new template or clone the working template, delete everything except the discovery rule and export that template.
Then manually edit the XML file and change the template name to the name of your template into which you would like to import that discovery rule.
Then import the XML and select "Update existing discovery rules".

Then you're done.

[siili]

[solved]

In 1.8 I had a separate template for active checks for windows. If my memory serves me, it was needed to get Windows logging working. I did find such a template in 2.0 so I migrated it from 1.8 but obviously it was not correct. On the ones that worked, it was because I had added the Windows template that came with Zabbix 2.0 before unlinking it and adding the 1.8 template, without using "Unlink and clear". To clean it all up and get it working I did a "Unlink and clear" on all the 1.8 templates, then added the 2.0 template for Windows.

Regards,
David Koski
[email protected]