Onderwerp: Zabbix

Hi,

Ik ben met een aantal servers van een klant bezig, de bedoeling is dat zabbix op één server 3 andere servers in de gaten houd (dus 1 master, 3 slaves). Op mijn eigen server draait ook zabbix en houd andere servers in de gaten, alleen hier krijg ik errors waar ik de oorzaak niet van kan vinden. Iemand enig idee? Dit is de config van alle agents: (alleen hostname is uiteraard steeds anders)

Code:

# 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=xxx.xxx.xxx.xxx

# Server port for sending active checks

#ServerPort=10051

# Unique hostname. Required for active checks.

Hostname=domainname.ext

# Listen port. Default is 10050

#ListenPort=10050

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

#ListenIP=

# 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
# 4 - information (default)
# 5 - for debugging (produces lots of information)

DebugLevel=3

# Name of PID file

PidFile=/var/tmp/zabbix_agentd.pid

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

LogFile=/tmp/zabbix_agentd.log

# Maximum size of log file in MB. Set to 0 to disable automatic log rotation.
#LogFileSize=1

# 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

In elke log staat:

Code:

19994:20071105:184439 zabbix_agentd started. ZABBIX 1.4.2.
 19995:20071105:184439 zabbix_agentd collector started
 19996:20071105:184439 zabbix_agentd listener started
 19997:20071105:184439 zabbix_agentd listener started
 19998:20071105:184439 zabbix_agentd listener started
 19999:20071105:184439 zabbix_agentd active check started [xxx.xxx.xxx.xxx:10051]

Pingbaar is ie, als ik naar de DNS ping krijg ik ip en andersom ook (niet bij alle 2 het geval maar wel bij 1, dus daar kan heb probleem niet liggen?)

Bedankt.

ALs je met nmap een poortscan uitvoert, zie je de daemon dan wel?

Op de server of op de clients?

clients. De server kan de daemon op de clients niet bereiken...

Code:

[root@startertjes ~]# nmap 85.12.15.19 -p 10050-10051

Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2007-11-05 21:15 CET
Interesting ports on 85.12.15.19.xentronix.nl (85.12.15.19):
PORT      STATE  SERVICE
10050/tcp open   unknown
10051/tcp closed unknown
MAC Address: 00:0C:DB:21:9B:20 (Foundry Networks)

Nmap run completed -- 1 IP address (1 host up) scanned in 0.282 seconds

Ik snap het niet, heb dit in iptables staan en toch word 10051 geblokkeerd? (Het is TCP)

Code:

-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 10050 -j ACCEPT
-A RH-Firewall-1-INPUT -m state --state NEW -m tcp -p tcp --dport 10051 -j ACCEPT

Iptables is herstart..

Anyone?