Добрый день! Ситуация такая: необходимо мониторить виртуальную машину (OC Windows Server 2003), которая установлена на физ. хосте на Virtualbox (ОС CentOS 6). Zabbix-сервер установлен на другом физ хосте, имеет белый и внутренний IP. При подключении виртуалки к системе мониторинга в веб-интерфейсе напротив узла сети вижу данную ошибку. Привожу детали:
Виртуалка имеет 2 сетевых интерфейса - один имеет локальный адрес 10.1.1.35 и работает в режиме Bridged, второй - 10.0.3.15, работает в режиме NAT. В Virtualbox с интерфейса 10.0.3.15 проброшен наружу порт 10050:
Использую порт 10053, т.к. на порту 10050 физ. хост уже (успешно) мониторится Zabbix'ом. На фаерволе в CentOS порт 10053 открыт.
Конфиг агента:
Команда zabbix_get -s xx.xx.xx.xx -p 10053 -k agent.ping c любым допустимым значением ключа выводит пустую строку.
Помогите, пожалуйста, найти в чем проблема.
Виртуалка имеет 2 сетевых интерфейса - один имеет локальный адрес 10.1.1.35 и работает в режиме Bridged, второй - 10.0.3.15, работает в режиме NAT. В Virtualbox с интерфейса 10.0.3.15 проброшен наружу порт 10050:
Code:
Protocol Host IP Host Port Guest IP Guest Port TCP xx.xx.xx.xx 10053 10.0.3.15 10050 UDP xx.xx.xx.xx 10053 10.0.3.15 10050
Конфиг агента:
Code:
# This is a config file for Zabbix Agent (Windows) # To get more information about Zabbix, go to http://www.zabbix.com ############ GENERAL PARAMETERS ################# ### Option: LogFile # Name of log file. # If not set, Windows Event Log is used. # # Mandatory: no # Default: # LogFile= LogFile=c:\zabbix_agentd.log ### Option: LogFileSize # Maximum size of log file in MB. # 0 - disable automatic log rotation. # # Mandatory: no # Range: 0-1024 # Default: # LogFileSize=1 ### Option: DebugLevel # Specifies debug level # 0 - no debug # 1 - critical information # 2 - error information # 3 - warnings # 4 - for debugging (produces lots of information) # # Mandatory: no # Range: 0-4 # Default: # DebugLevel=3 ### Option: SourceIP # Source IP address for outgoing connections. # # Mandatory: no # Default: SourceIP=10.0.3.15 ### Option: EnableRemoteCommands # Whether remote commands from Zabbix server are allowed. # 0 - not allowed # 1 - allowed # # Mandatory: no # Default: EnableRemoteCommands=1 ### Option: LogRemoteCommands # Enable logging of executed shell commands as warnings. # 0 - disabled # 1 - enabled # # Mandatory: no # Default: LogRemoteCommands=1 ##### Passive checks related ### Option: Server # List of comma delimited IP addresses (or hostnames) of Zabbix servers. # Incoming connections will be accepted only from the hosts listed here. # No spaces allowed. # If IPv6 support is enabled then '127.0.0.1', '::127.0.0.1', '::ffff:127.0.0.1' are treated equally. # # Mandatory: no # Default: # Server= Server=zz.zz.zz.zz ### Option: ListenPort # Agent will listen on this port for connections from the server. # # Mandatory: no # Range: 1024-32767 # Default: ListenPort=10050 ### Option: ListenIP # List of comma delimited IP addresses that the agent should listen on. # First IP address is sent to Zabbix server if connecting to it to retrieve list of active checks. # # Mandatory: no # Default: ListenIP=10.0.3.15 ### Option: StartAgents # Number of pre-forked instances of zabbix_agentd that process passive checks. # If set to 0, disables passive checks and the agent will not listen on any TCP port. # # Mandatory: no # Range: 0-100 # Default: # StartAgents=3 ##### Active checks related ### Option: ServerActive # List of comma delimited IP:port (or hostname:port) pairs of Zabbix servers for active checks. # If port is not specified, default port is used. # IPv6 addresses must be enclosed in square brackets if port for that host is specified. # If port is not specified, square brackets for IPv6 addresses are optional. # If this parameter is not specified, active checks are disabled. # Example: ServerActive=127.0.0.1:20051,zabbix.domain,[::1]:30051,::1,[12fc::1] # # Mandatory: no # Default: # ServerActive= ServerActive=zz.zz.zz.zz:10051 ### Option: Hostname # Unique, case sensitive hostname. # Required for active checks and must match hostname as configured on the server. # Value is acquired from HostnameItem if undefined. # # Mandatory: no # Default: # Hostname= Hostname=AM_SMPP ### Option: HostnameItem # Item used for generating Hostname if it is undefined. # Ignored if Hostname is defined. # # Mandatory: no # Default: # HostnameItem=system.hostname ### Option: RefreshActiveChecks # How often list of active checks is refreshed, in seconds. # # Mandatory: no # Range: 60-3600 # Default: # RefreshActiveChecks=120 ### Option: BufferSend # Do not keep data longer than N seconds in buffer. # # Mandatory: no # Range: 1-3600 # Default: # BufferSend=5 ### Option: BufferSize # Maximum number of values in a memory buffer. The agent will send # all collected data to Zabbix server or Proxy if the buffer is full. # # Mandatory: no # Range: 2-65535 # Default: # BufferSize=100 ### Option: MaxLinesPerSecond # Maximum number of new lines the agent will send per second to Zabbix Server # or Proxy processing 'log', 'logrt' and 'eventlog' active checks. # The provided value will be overridden by the parameter 'maxlines', # provided in 'log', 'logrt' or 'eventlog' item keys. # # Mandatory: no # Range: 1-1000 # Default: # MaxLinesPerSecond=100 ############ ADVANCED PARAMETERS ################# ### Option: Alias # Sets an alias for parameter. It can be useful to substitute long and complex parameter name with a smaller and simpler one. # For example, if you wish to retrieve paging file usage in percents from the server, # you may use parameter "perf_counter[\Paging File(_Total)\% Usage]", or you may define an alias by adding the following line to configuration file # Alias = pg_usage:perf_counter[\Paging File(_Total)\% Usage] # After that you can use parameter name "pg_usage" to retrieve the same information. # You can specify as many "Alias" records as you wish. # Aliases cannot be used for parameters defined in "PerfCounter" configuration file records. # # Mandatory: no # Range: # Default: ### Option: Timeout # Spend no more than Timeout seconds on processing # # Mandatory: no # Range: 1-30 # Default: Timeout=30 ### Option: PerfCounter # Syntax: <parameter_name>,"<perf_counter_path>",<period> # Defines new parameter <parameter_name> which is an average value for system performance counter <perf_counter_path> for the specified time period <period> (in seconds). # For example, if you wish to receive average number of processor interrupts per second for last minute, you can define new parameter "interrupts" as following: # PerfCounter = interrupts,"\Processor(0)\Interrupts/sec",60 # Please note double quotes around performance counter path. # Samples for calculating average value will be taken every second. # You may run "typeperf -qx" to get list of all performance counters available in Windows. # # Mandatory: no # Range: # Default: ### Option: Include # You may include individual files in the configuration file. # # Mandatory: no # Default: # Include= # Include=c:\zabbix\zabbix_agentd.userparams.conf ####### USER-DEFINED MONITORED PARAMETERS ####### ### Option: UnsafeUserParameters # Allow all characters to be passed in arguments to user-defined parameters. # 0 - do not allow # 1 - allow # # Mandatory: no # Range: 0-1 # Default: # UnsafeUserParameters=0 ### Option: UserParameter # User-defined parameter to monitor. There can be several user-defined parameters. # Format: UserParameter=<key>,<shell command> # # Mandatory: no # Default: # UserParameter=
Помогите, пожалуйста, найти в чем проблема.
Comment