agents not listening

[ksmith]

I'm playing with one of the prebuilt Zabbix virtual machine appliances, but i can't get any agents to connect to the host. Ive tried 2 windows 2003 machines and 1 windows XP machine. Availability just stays on "unkown." I finally (using netstat -na) noticed that none of the agents are listening on port 10050, or any other port. I've tried stopping and restarting the zabbixw32 service several times. Ive tried ListenIP uncommented and commented. Here is one of my config files. What am I missing?

# This is config file for zabbix_agentd
# To get more information about ZABBIX, go http://www.zabbix.com

############ 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.1.11

# Server port for sending active checks
ServerPort=10051

# Unique hostname. Required for active checks.
Hostname=mom1

# Listen port. Default is 10050
ListenPort=10050

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

# 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)
# 3 - warnings (default)
# 4 - for debugging (produces lots of information)
DebugLevel=3

# Name of PID file
PidFile=/var/run/zabbix/zabbix_agentd.pid

# Name of log file.
# If not set, syslog will be used
LogFile=/var/log/zabbix/zabbix_agentd.log

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

####### USER-DEFINED MONITORED PARAMETERS #######
# Format: UserParameter=<key>,<shell command>
# Note that shell command must not return empty string or EOL only
#UserParameter=system.test,who|wc -l
### Set of parameter for monitoring MySQL server (v3.23.42 and later)
### Change -u<username> and add -p<password> if required
#UserParameter=mysql.ping,mysqladmin -uroot ping|grep alive|wc -l
#UserParameter=mysql.uptime,mysqladmin -uroot status|cut -f2 -d":"|cut -f1 -d"T"
#UserParameter=mysql.threads,mysqladmin -uroot status|cut -f3 -d":"|cut -f1 -d"Q"
#UserParameter=mysql.questions,mysqladmin -uroot status|cut -f4 -d":"|cut -f1 -d"S"
#UserParameter=mysql.slowqueries,mysqladmin -uroot status|cut -f5 -d":"|cut -f1 -d"O"
#UserParameter=mysql.qps,mysqladmin -uroot status|cut -f9 -d":"
#UserParameter=mysql.version,mysql -V

[ksmith]

Sorry. I just now saw that i think all the agents are stuck trying to start. On the 2003 machines, windows gives an error that the service didnt start in a timely fashion. Hope that helps.

[dantheman]

Try changing the line in the config file

LogFile=/var/log/zabbix/zabbix_agentd.log

to point the logfile to a Windows Friendly location,

eg

LogFile=C:\zabbix_agentd.log

I ran into some problems initially setting these up until I changed that.

[ksmith]

Thanks, they are now listening but the web interface still says unavailable. I've checked local firewalls on the agent computers and they're open for 10050 and 10051. I assume those ports are open on the pre-built Zabbix virtual machine im using as well. What can I check now?

[dantheman]

Sometimes I have had to "kick start" the system when I'm initially setting it up, try clicking on the word unavailable, it should change to unmonitored, click that to change it back to monitored. See if that gets you going.

The other thing to check would be that log file and see what information it tells you...

If the log file doesn't show anything, you may want to change the line to the config for the client, debuglevel, to 4 that will give you all the information as to what the agent is doing, useful for troubleshooting. But once you get it working I woudl suggest changing it back to 3 since you don't need to be logging everything it does.

You can also check the log file on the server side to see if it's trying to connect to the agent or not.. and the same thing about the debug level applies to the server as well.