Обновление доступа

[Jimm]

Здравствуйте уважаемы форумчане, совсем недавно начал пользоваться данным По. Возник такой вопрос, при добавлении нового узла сети в пункте "Доступ" иконка zbx - горит серого цвета.
Почитав на форумах и в faq увидел, что нужно подождать пока произойдет обновление.

Сколько по времени нужно ждать и можно ли как-то вручную провести обновление?

[DmitryL]

Добрый день,

иконка станет красной или зелёной только после того как вы добавите шаблон в конкретный узел.

[Jimm]

Подробнее

Поподробнее

Имя узла: имя-пк.домен
Интерфейсы агента: прописываю через ДНС
Наблюдение через прокси: Ставлю необходимый прокси

Шаблон указываю: Zabbix agent
Остальное все стандартно.

Что заметил, пока ковырялся, пока модераторы одобряли мой пост.
Пробовал переключить интерфейс по IP - ничего.
Единственное, что дало результат, это:
Наблюдение через прокси -> (без прокси).
Через время иконка становится красной. Но данный вариант мне не подходит. т.к, необходимо использование прокси.

Стоит версия 3.0.2

Так же имеется проблема, в режиме конструктора "Карты сети", не отображаются имена иконок и их соединения, и в левом верхнем углу, что то вроде ошибки отображения изображения Susmap.

Возможно, что то залагало и возможно поможет релог сервера. Т.к полных прав и доступа в самом Zabbix не имею. То пробовать будем после праздников, когда админ будет на связи.

Пока думал может кто то сталкивался и поможете наперед советами и что где проверить заранее

[bboyshock]

на узле порт для zabbix открыт?

[Jimm]

Ответ

Если вы про FireWall то да. А вообще странная проблема.

Существует созданный, уже давно узел сети, настроен, работает корректно, меняю ему име с приставкой test, клонирую его, и все, клоновый узел так же встает в ступор.

[bboyshock]

А что в логе агента на узле?

[Jimm]

Так же скажу, по началу не правильно был настроен конфиг.
После обнаружения проблемы конечно изменили и host name и server






7808:20160429:170844.906 Starting Zabbix Agent [Windows host]. Zabbix 3.0.0 (revision 58455).
7808:20160429:170844.907 **** Enabled features ****
7808:20160429:170844.907 IPv6 support: YES
7808:20160429:170844.907 TLS support: NO
7808:20160429:170844.908 **************************
7808:20160429:170844.908 using configuration file: C:\zabbix_agentd\zabbix_agentd.win.conf
7808:20160429:170844.910 agent #0 started [main process]
6440:20160429:170844.911 agent #1 started [collector]
756:20160429:170844.911 agent #2 started[listener #1]
7872:20160429:170844.912 agent #3 started[listener #2]
7432:20160429:170844.912 agent #4 started[listener #3]
7424:20160429:170844.913 agent #5 started [active checks #1]
7424:20160429:170845.913 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: Connection refused.)
7836:20160429:172812.231 Zabbix Agent stopped. Zabbix 3.0.0 (revision 58455).
2364:20160504:095528.076 Starting Zabbix Agent [Windows host]. Zabbix 3.0.0 (revision 58455).
2364:20160504:095528.076 **** Enabled features ****
2364:20160504:095528.076 IPv6 support: YES
2364:20160504:095528.076 TLS support: NO
2364:20160504:095528.076 **************************
2364:20160504:095528.076 using configuration file: C:\zabbix_agentd\zabbix_agentd.win.conf
2364:20160504:095528.123 agent #0 started [main process]
2320:20160504:095528.123 agent #1 started [collector]
1516:20160504:095528.123 agent #2 started[listener #1]
2284:20160504:095528.123 agent #3 started[listener #2]
2440:20160504:095528.123 agent #4 started[listener #3]
2428:20160504:095528.123 agent #5 started [active checks #1]
2428:20160504:095529.152 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: Connection refused.)
2256:20160504:183200.968 Zabbix Agent stopped. Zabbix 3.0.0 (revision 58455).
2936:20160505:095433.253 Starting Zabbix Agent [Windows host]. Zabbix 3.0.0 (revision 58455).
2936:20160505:095433.253 **** Enabled features ****
2936:20160505:095433.253 IPv6 support: YES
2936:20160505:095433.253 TLS support: NO
2936:20160505:095433.253 **************************
2936:20160505:095433.253 using configuration file: C:\zabbix_agentd\zabbix_agentd.win.conf
2936:20160505:095433.285 agent #0 started [main process]
2948:20160505:095433.285 agent #1 started [collector]
2928:20160505:095433.285 agent #2 started[listener #1]
2932:20160505:095433.285 agent #3 started[listener #2]
2924:20160505:095433.285 agent #4 started[listener #3]
2916:20160505:095433.285 agent #5 started [active checks #1]
2916:20160505:095434.314 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: Connection refused.)
2920:20160505:182817.194 Zabbix Agent stopped. Zabbix 3.0.0 (revision 58455).
2840:20160506:101117.197 Starting Zabbix Agent [Windows host]. Zabbix 3.0.0 (revision 58455).
2840:20160506:101117.197 **** Enabled features ****
2840:20160506:101117.197 IPv6 support: YES
2840:20160506:101117.197 TLS support: NO
2840:20160506:101117.197 **************************
2840:20160506:101117.197 using configuration file: C:\zabbix_agentd\zabbix_agentd.win.conf
2840:20160506:101117.197 agent #0 started [main process]
2832:20160506:101117.197 agent #1 started [collector]
2880:20160506:101117.197 agent #3 started[listener #2]
2824:20160506:101117.197 agent #2 started[listener #1]
2904:20160506:101117.197 agent #5 started [active checks #1]
2308:20160506:101117.197 agent #4 started[listener #3]
2904:20160506:101118.242 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: Connection refused.)
2852:20160506:183516.248 Zabbix Agent stopped. Zabbix 3.0.0 (revision 58455).
8636:20160506:183743.222 Starting Zabbix Agent [pc-3052]. Zabbix 3.0.0 (revision 58455).
8636:20160506:183743.222 **** Enabled features ****
8636:20160506:183743.223 IPv6 support: YES
8636:20160506:183743.224 TLS support: NO
8636:20160506:183743.224 **************************
8636:20160506:183743.225 using configuration file: C:\zabbix_agentd\zabbix_agentd.win.conf
8636:20160506:183743.227 agent #0 started [main process]
7036:20160506:183743.228 agent #1 started [collector]
5680:20160506:183743.238 agent #3 started[listener #2]
1720:20160506:183743.239 agent #4 started[listener #3]
1100:20160506:183743.239 agent #2 started[listener #1]
3832:20160510:095525.113 Zabbix Agent stopped. Zabbix 3.0.0 (revision 58455).
2140:20160510:095718.038 Starting Zabbix Agent [pc-3052]. Zabbix 3.0.0 (revision 58455).
2140:20160510:095718.038 **** Enabled features ****
2140:20160510:095718.038 IPv6 support: YES
2140:20160510:095718.038 TLS support: NO
2140:20160510:095718.038 **************************
2140:20160510:095718.038 using configuration file: C:\zabbix_agentd\zabbix_agentd.win.conf
2140:20160510:095718.068 agent #0 started [main process]
2256:20160510:095718.068 agent #1 started [collector]
2264:20160510:095718.068 agent #2 started[listener #1]
2220:20160510:095718.068 agent #3 started[listener #2]
2248:20160510:095718.068 agent #4 started[listener #3]

[Jimm]

Новый узел

Только что создал новый узел для примера.
Установил на компьютере агент, после внес исключение в фаерволл и перезагрузил службу.

Логи

1460:20160510:123014.822 Starting Zabbix Agent [pc-3071]. Zabbix 3.0.0 (revision 58455).
1460:20160510:123014.822 **** Enabled features ****
1460:20160510:123014.822 IPv6 support: YES
1460:20160510:123014.822 TLS support: NO
1460:20160510:123014.822 **************************
1460:20160510:123014.822 using configuration file: C:\zabbix_agentd\zabbix_agentd.win.conf
1460:20160510:123014.869 agent #0 started [main process]
3292:20160510:123014.869 agent #1 started [collector]
3652:20160510:123014.869 agent #2 started[listener #1]
3668:20160510:123014.885 agent #3 started[listener #2]
3284:20160510:123014.885 agent #4 started[listener #3]
3528:20160510:123014.885 agent #5 started [active checks #1]
3528:20160510:123015.884 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: Connection refused.)
3332:20160510:124628.486 Zabbix Agent stopped. Zabbix 3.0.0 (revision 58455).
3764:20160510:124628.939 Starting Zabbix Agent [pc-3071]. Zabbix 3.0.0 (revision 58455).
3764:20160510:124628.939 **** Enabled features ****
3764:20160510:124628.939 IPv6 support: YES
3764:20160510:124628.939 TLS support: NO
3764:20160510:124628.939 **************************
3764:20160510:124628.939 using configuration file: C:\zabbix_agentd\zabbix_agentd.win.conf
3764:20160510:124628.955 agent #0 started [main process]
3856:20160510:124628.955 agent #1 started [collector]
3604:20160510:124628.955 agent #2 started[listener #1]
1016:20160510:124628.971 agent #3 started[listener #2]
3460:20160510:124628.971 agent #4 started[listener #3]
3476:20160510:124628.971 agent #5 started [active checks #1]
3476:20160510:124629.986 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: Connection refused.)


Конфиг файл

# This is a configuration file for Zabbix agent service (Windows)
# To get more information about Zabbix, visit http://www.zabbix.com

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

### Option: LogType
# Specifies where log messages are written to:
# system - Windows event log
# file - file specified with LogFile parameter
# console - standard output
#
# Mandatory: no
# Default:
# LogType=file

### Option: LogFile
# Log file name for LogType 'file' parameter.
#
# 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 - basic information about starting and stopping of Zabbix processes
# 1 - critical information
# 2 - error information
# 3 - warnings
# 4 - for debugging (produces lots of information)
# 5 - extended debugging (produces even more information)
#
# Mandatory: no
# Range: 0-5
# Default:
# DebugLevel=3

### Option: SourceIP
# Source IP address for outgoing connections.
#
# Mandatory: no
# Default:
# SourceIP=

### Option: EnableRemoteCommands
# Whether remote commands from Zabbix server are allowed.
# 0 - not allowed
# 1 - allowed
#
# Mandatory: no
# Default:
# EnableRemoteCommands=0

### Option: LogRemoteCommands
# Enable logging of executed shell commands as warnings.
# 0 - disabled
# 1 - enabled
#
# Mandatory: no
# Default:
# LogRemoteCommands=0

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

### 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=0.0.0.0

### 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 IPort (or hostnameort) 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=127.0.0.1

### 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=pc-3071

### Option: HostnameItem
# Item used for generating Hostname if it is undefined. Ignored if Hostname is defined.
# Does not support UserParameters or aliases.
#
# Mandatory: no
# Default:
# HostnameItem=system.hostname

### Option: HostMetadata
# Optional parameter that defines host metadata.
# Host metadata is used at host auto-registration process.
# An agent will issue an error and not start if the value is over limit of 255 characters.
# If not defined, value will be acquired from HostMetadataItem.
#
# Mandatory: no
# Range: 0-255 characters
# Default:
# HostMetadata=

### Option: HostMetadataItem
# Optional parameter that defines an item used for getting host metadata.
# Host metadata is used at host auto-registration process.
# During an auto-registration request an agent will log a warning message if
# the value returned by specified item is over limit of 255 characters.
# This option is only used when HostMetadata is not defined.
#
# Mandatory: no
# Default:
# HostMetadataItem=

### 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=20

############ ADVANCED PARAMETERS #################

### Option: Alias
# Sets an alias for an item key. It can be used to substitute long and complex item key with a smaller and simpler one.
# Multiple Alias parameters may be present. Multiple parameters with the same Alias key are not allowed.
# Different Alias keys may reference the same item key.
# For example, to retrieve paging file usage in percents from the server:
# Alias=pg_usageerf_counter[\Paging File(_Total)\% Usage]
# Now shorthand key pg_usage may be used to retrieve data.
# Aliases can be used in HostMetadataItem but not in HostnameItem or PerfCounter parameters.
#
# Mandatory: no
# Range:
# Default:

### Option: Timeout
# Spend no more than Timeout seconds on processing.
#
# Mandatory: no
# Range: 1-30
# Default:
# Timeout=3

### 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
# Include=c:\zabbix\zabbix_agentd.conf.d\
# Include=c:\zabbix\zabbix_agentd.conf.d\*.conf

####### USER-DEFINED MONITORED PARAMETERS #######

### Option: UnsafeUserParameters
# Allow all characters to be passed in arguments to user-defined parameters.
# The following characters are not allowed:
# \ ' " ` * ? [ ] { } ~ $ ! & ; ( ) < > | # @
# Additionally, newline characters are not allowed.
# 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=

####### TLS-RELATED PARAMETERS #######

### Option: TLSConnect
# How the agent should connect to server or proxy. Used for active checks.
# Only one value can be specified:
# unencrypted - connect without encryption
# psk - connect using TLS and a pre-shared key
# cert - connect using TLS and a certificate
#
# Mandatory: yes, if TLS certificate or PSK parameters are defined (even for 'unencrypted' connection)
# Default:
# TLSConnect=unencrypted

### Option: TLSAccept
# What incoming connections to accept.
# Multiple values can be specified, separated by comma:
# unencrypted - accept connections without encryption
# psk - accept connections secured with TLS and a pre-shared key
# cert - accept connections secured with TLS and a certificate
#
# Mandatory: yes, if TLS certificate or PSK parameters are defined (even for 'unencrypted' connection)
# Default:
# TLSAccept=unencrypted

### Option: TLSCAFile
# Full pathname of a file containing the top-level CA(s) certificates for
# peer certificate verification.
#
# Mandatory: no
# Default:
# TLSCAFile=

### Option: TLSCRLFile
# Full pathname of a file containing revoked certificates.
#
# Mandatory: no
# Default:
# TLSCRLFile=

### Option: TLSServerCertIssuer
# Allowed server certificate issuer.
#
# Mandatory: no
# Default:
# TLSServerCertIssuer=

### Option: TLSServerCertSubject
# Allowed server certificate subject.
#
# Mandatory: no
# Default:
# TLSServerCertSubject=

### Option: TLSCertFile
# Full pathname of a file containing the agent certificate or certificate chain.
#
# Mandatory: no
# Default:
# TLSCertFile=

### Option: TLSKeyFile
# Full pathname of a file containing the agent private key.
#
# Mandatory: no
# Default:
# TLSKeyFile=

### Option: TLSPSKIdentity
# Unique, case sensitive string used to identify the pre-shared key.
#
# Mandatory: no
# Default:
# TLSPSKIdentity=

### Option: TLSPSKFile
# Full pathname of a file containing the pre-shared key.
#
# Mandatory: no
# Default:
# TLSPSKFile=

[bboyshock]

со стороны клиента вроде все норм, значок на сервере поменял свой цвет?
Я еще указываю сервер active на всех своих клиентах.
upd

active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: Connection refused.)

измените ip в клиентском конфиге на ип заббикса

[Jimm]

Ответ

Добавил около десятка новых узлов.
Все висят так же. За праздники 2-3 дня, ничего не изменилось. Значек серого цвета
Там где active, так же указывается IP прокси?
Хотя у меня есть пачка давно созданных узлов, у них тот же конфиг, только с разным HostName - у них все работает. Горит Красным - узел отключен, зеленым когда включен.

[DmitryL]

ServerActive=127.0.0.1
Тут должен быть IP Zabbix сервера.

[Jimm]

измените ip в клиентском конфиге на ип заббикса

ServerActive=127.0.0.1?

log
[127.0.0.1:10051]

Почему порт 10051?

[Jimm]

Еще одна проблема

Один из узлов в забиксе загорелся красным.
При наводе на значок показал ошибку.

То есть видно, что имя узла pc-11.domen а ошибка заключается в том что он не может найти computer.domen хотя в настройках во всех указанно pc-11

computer.domen старое название узла в забиксе, был переименован в пару дней назад в pc-11