Zabbix Win32 Agent cannot connect?

[zombiehunter]

Any ideas? I cannot get any windows box to talk to my zabbix server even though the zabbix server had showed the windows server (2003) as available! (it does not now)

this is from my zabbix_agentd.log


[12-Jun-2007 14:24:36] *************** Log file opened ****************
[12-Jun-2007 14:24:37] Collector thread initialized successfully
[12-Jun-2007 14:24:37] Zabbix Win32 Agent started
[12-Jun-2007 14:24:37] Information: 3156 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 3664 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 1052 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 3144 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 3628 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 172 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 2572 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 3020 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 2880 : Listen thread is Started.
[12-Jun-2007 14:24:37] Information: 2184 : Listen thread is Started.
[12-Jun-2007 14:24:58] Active checks [Cannot connect to [192.168.5.9:10051] [No error]]
[12-Jun-2007 14:26:19] Active checks [Cannot connect to [192.168.5.9:10051] [No error]]
[12-Jun-2007 14:27:40] Active checks [Cannot connect to [192.168.5.9:10051] [No error]]
[12-Jun-2007 14:29:01] Active checks [Cannot connect to [192.168.5.9:10051] [No error]]
[12-Jun-2007 14:30:22] Active checks [Cannot connect to [192.168.5.9:10051] [No error]]
[12-Jun-2007 14:33:29] Active checks [Connection reset by peer.]


don't know if it helps but this is my zabbix_agentd.conf -


############ GENERAL PARAMETERS #################

# List of comma delimited IP addresses (or hostnames) of ZABBIX servers.
# No spaces allowed. First entry is used for sending active checks.
# Note that hostnames must resolve hostname->IP address and
# IP address->hostname.

Server=192.168.5.9

# Server port for sending active checks

ServerPort=10051

# Unique hostname. Required for active checks.

Hostname=netprobe.XXXXXXX.com

# Listen port. Default is 10050

ListenPort=10050

# IP address to bind agent
# If missing, bind to all available IPs

#ListenIP=127.0.0.1

# Number of pre-forked instances of zabbix_agentd.
# Default value is 5
# This parameter must be between 1 and 16

StartAgents=5

# How often refresh list of active checks. 2 minutes by default.

#RefreshActiveChecks=120

# Disable active checks. The agent will work in passive mode listening server.

#DisableActive=1

# Enable remote commands for ZABBIX agent. By default remote commands disabled.

EnableRemoteCommands=1

# Specifies debug level
# 0 - debug is not created
# 1 - critical information
# 2 - error information
# 3 - warnings (default)
# 4 - for debugging (produces lots of information)

DebugLevel=2

# Name of PID file

#PidFile=C:\Program Files\Zabbix Agent/Zabbix_agentd.pid

# Name of log file.
# If not set, syslog will be used

LogFile=C:\Program Files\Zabbix Agent/Zabbix_agentd.log

# Spend no more than Timeout seconds on processing
# Must be between 1 and 30

Timeout=5

[bill.unger]

What happens if you change the hostname to "localhost"?

[zombiehunter]

tried it- no good.

I also tried using the server's hostname (forget now where I read it but i tried it) and also the clients hostname too.

In looking at the discovery configuration settings, I noticed that I have one I setup for zabbix agent (Does this refer to zabbix_agent or zabbix_agentd? I believe what is running on my clients is zabbix_agentd as the config file is called zabbix_agentd.conf) I dont see a second choice of zabbix agentd under disc config however- Are both covered? Does it matter?
Also- there is a field for a key- what key? community name? the agents as far as I can tell dont have a key configured in the config file.

[JonB]

Ok lets start at basics.

Can you telnet from the Server 2003 to the zabbix server on port 10051?

telnet 192.168.5.9 10051

If the connection is refused then you have a firewall issue and will need to open/forward port 10051 to localhost on the zabbix server or maybe you have ISA installed on the Server 2003 and that is blocking outgoing traffic on 10051.

You will also need to be able to telnet from the zabbix server to the Windows server on port 10050

telnet xxx.xxx.xxx.xxx 10050

Once again if the session is refused then you have a firewall issue on the windows server blocking port 10050.

The zabbix_agentd operates in two modes. Both modes are operational by default. Basically

Active - zabbix_agentd contacts the zabbix server at a regular interval to check if there are any 'active items' to be updated. For this to work the agent needs access to the zabbix server on port 10051.

Passive - The zabbix server initiates communication with the zabbix_agentd and tells the agent what items need updating. The zabbix server needs to talk to the agent on port 10050 in your case.

When you set up the Host in Zabbix start off using IP addresses. If you set up the host using the standard Template_Windows then all checks are 'passive' i.e the zabbix server contacts the agent on port 10050 or the port that you specified in the config file and specified when you set up the host in Zabbix. Note: they must be the same.

If you plan to use 'active' mode then you need make the 'items' active. I do this with laptops, copy the template 'Template_Windows' to 'Template_Windows_Active' and use the mass update option to change all items to Zabbix Agent (active).

Now you need to ensure that

1/ the Hostname you specify in zabbix_agentd.conf is exactly the same as the name you gave the host in Zabbix frontend. It will fail otherwise.
2/ the agent on the windows host can access the server on port 10051.

Hope this helps

Jon