Zabbix active checks

[spitfirekdv]

Hi all,

I have servers behind nat and I need clients to discover themselves
I have enabled discover on server, but no clients appeared via web-interface.

In logs:
Sending list of active checks to [ip] failed: host [hostname] not found

How can i do it?

[bashman]

Hi all,

I have servers behind nat and I need clients to discover themselves
I have enabled discover on server, but no clients appeared via web-interface.

In logs:
Sending list of active checks to [ip] failed: host [hostname] not found

How can i do it?

Have you specified the parameter "ServerIP" the nat IP on the servers behind nat zabbix_agentd.conf file?

[spitfirekdv]

Yes, of course

[walterheck]

As far as I can tell, that message means that discovery is not setup properly. That message is normally shown when a client connects to teh server with a hostname in it's zabbix_agentd.conf that is not found on the server. I don't use auto-discovery, so I can't really help you with this..

[acalvo]

Hi all,

I have servers behind nat and I need clients to discover themselves
I have enabled discover on server, but no clients appeared via web-interface.

In logs:
Sending list of active checks to [ip] failed: host [hostname] not found

How can i do it?

As walterheck said, it seems a misconfiguration either from the auto-discovery process (check the hostname that is given to auto-discovered machines) or because the agent configuration is not properly set up (check the Hostname parameter in zabbix_agentd.conf, must be the same that the Hostname defined in the zabbix server).

[Tractorboy]

I have the same issue and can confirm that the host names match.

My only concern is that I am using this using a clustered check so the host name itself isn't the actual server name, although it is correct at the dns level.

I need to cluster agent to be able to perform active checks, any suggestions?

[acalvo]

I have the same issue and can confirm that the host names match.

My only concern is that I am using this using a clustered check so the host name itself isn't the actual server name, although it is correct at the dns level.

I need to cluster agent to be able to perform active checks, any suggestions?

Can you post your agentd and server logs concerning this issue?

[Tractorboy]

7240:20101104:081644.930 No active checks on server: host [**SERVERNAME**] not found


0407:20101104:083646.364 Sending list of active checks to [**IP ADDRESS**] failed: host [GBEXE18AS112CN1] not found
10407:20101104:083646.364 Sending [{
"response":"failed",
"info":"host [**SERVERNAME**] not found"}]


The server does respond to the IP address being requested, but also on another.

[acalvo]

7240:20101104:081644.930 No active checks on server: host [**SERVERNAME**] not found


0407:20101104:083646.364 Sending list of active checks to [**IP ADDRESS**] failed: host [GBEXE18AS112CN1] not found
10407:20101104:083646.364 Sending [{
"response":"failed",
"info":"host [**SERVERNAME**] not found"}]


The server does respond to the IP address being requested, but also on another.

From my experience, that means a mismatch between host name defined in the server and in the agentd configuration file.
Could you post both?

[Tractorboy]

I can confirm that they are both the same and match in case.

I am suspecting multiple IP Addresses and multiple server names, to be the cause.

[acalvo]

I can confirm that they are both the same and match in case.

I am suspecting multiple IP Addresses and multiple server names, to be the cause.

How are you monitoring this host? By IP or DNS?

[Tractorboy]

I have set up one by IP and the other by DNS and both have problems. I will play around a little more but I seem to waste huge amounts of time of very minor things and frustration levels are building.