Active checks not working

[Bert ter Beest]

Hello Zabbix fanatics

I have a problem checking windows logfiles. If I check the server-logfile, it seems to have something to do with a dns lookup. Since my agents are all located outside our zabbix-server network, the dns lookup obviously fails.

Is there a way around this, I would really like to enable checks on the Windows Eventviewer.

Any help is welcome...

[Bert ter Beest]

Some information after a couple of days testing:

I cannot telnet on either port 10050 or 10051 form the agent to the server. However, I can connect from the server to the agent with telnet to port 10050 but not 10051.

Agent error is:

Get active checks error: Cannot connect to [172.25.1.114:10051] [Een verbindingspoging is mislukt omdat de verbonden party niet correct heeft geantwoord na een bepaalde tijd, of de gemaakte verbinding is mislukt omdat de verbonden host niet heeft geantwoord.]

(Dutch server sry, last message says: error because of timeout or no response from server)

On the server I see an error that even the checks on the server itself are not working:

24069:20090831:164958 Send list of active checks to [127.0.0.1] failed: host [srv01] not found

srv01 is added to the servers hosts file (obviously, Linux does that itself on install because the servers actual hostname is in fact srv01)

Can anyone help?

[Calimero]

Before testing log monitoring, you should make sure "basic" active checks (CPU usage, memory usage ...) work .

From the agent, can you "telnet 172.25.1.114 10051" ?
If not:
- make sure firewall rules are OK on both ends (agent,server) and in the middle
- make sure zabbix_server is running and listening on port 10051 and that it is bound at least on 172.25.1.114:10051

Regarding 'host [srv01] not found', what you set in zabbix_agentd.conf (Hostname key) must exactly match the host name given in the UI. DNS/hosts entries don't matter.

[Bert ter Beest]

Right, got a bit confused with the hostname setting, got it set now to the hosts parameter in the Zabbix UI.

My problem is now solved, it seems that I had forgotten a managed switch, which was blocking port 10051.

Tnx for your help!