Ad Widget

**janssenreis** · 03-09-2015, 19:23

Você está substituindo o nome do host com a macro {HOST.NAME}. Possivelmente o nome do seu host não é o nome da zona que você está querendo testar. Correto?

Bem, sobre a chave net.dns.record, você só consegue utilizar com Zabbix Agent. Sendo assim, não será possível você fazer esse monitoramento na infra do seu cliente. Mas, você pode cadastrar esse item em qualquer host, por exemplo, no seu próprio Zabbix Server.

Experimente executar:

Code:

zabbix_get -s localhost -k "net.dns.record[8.8.8.8,zabbix.com,A,2,1]"

Ele tem que te retornar:

Code:

zabbix.com     A     87.110.183.172

Obs.: não precisa cadastrar a chave. É só executar no shell.

Att,

Janssen dos Reis Lima

http://blog.janssenlima.com

http://www.conectsys.com.br

**[email protected]** · 03-09-2015, 19:46

Obrigado pelo contato Janssen .

Kara, o {HOST.NAME} é o mesmo sim cadastrado.
Mesmo eu alterando a macro par ao HOST explicitamente, o erro retornado é o mesmo.

A sintaxe inserida:
net.dns.record[8.8.8.8,cavalomarinho.com.br,A,2,1]

O erro ccompleto é:
<html>
<head><title>400 Bad Request</title></head>
<body bgcolor="white">
<center><h1>400 Bad Request</h1></center>
<hr><center>nginx/1.2.1</center>
</body>
</html>

Lembrando que não tenho agente nenhum instalado na ponta do cavalomarinho.com.br

Via Bash...tb não estou conseguindo.
Acredito eu estar no caminho errado ( sou newby no zabbix ).

Consegue dar uma força?

Supondo que tenha sucesso via Bash como colocar este cara para monitorar os registros dentro do Zabbix?

Obrigado pelo contato.

Grande Abraço

**[email protected]** · 03-09-2015, 20:35

Janssen.

Veja o erro retornado agora ( nao havia isntalado o zabbix-get )

root@d1-support-zabbix:/usr/bin# zabbix_get -s localhost -k "net.dns.record[8.8.8.8,zabbix.com,A,2,]"

Retornou:

zabbix_get [27494]: Get value error: ZBX_TCP_READ() failed: [104] Connection reset by peer

**janssenreis** · 04-09-2015, 19:00

Você está executando isso do Zabbix Server. Se sim, o próprio Zabbix Agent está recusando a comunicação com o Zabbix Server.

Att,

Janssen dos Reis Lima

http://blog.janssenlima.com

http://www.conectsys.com.br

**[email protected]** · 04-09-2015, 19:40

É isto mesmo +Janssen .

Tenho 1 só server Debian 7.5, instalado o server e tb o Agent.
O que voce me recomendaria neste caso? Há uma forma de fazer estas pesquisas de DNS a partir somente do Server+Agente em uma única isntancia?

**janssenreis** · 09-09-2015, 22:13

Executa:

Code:

# zabbix_get -s localhost -k "agent.ping"

Qual a resposta?

Att,

Janssen dos Reis Lima

http://blog.janssenlima.com

http://www.conectsys.com.br

**[email protected]** · 10-09-2015, 15:00

Obrigado pela ajuda, porém toda chamada feita com zabbix_get, retorna o mesmo erro

root@d1-support-zabbix:/home/aryel# zabbix_get -s localhost -k "agent.ping"
zabbix_get [29952]: Get value error: ZBX_TCP_READ() failed: [104] Connection reset by peer

Porém, utilizando a sintaxe abaixo, obtive suceso

root@d1-support-zabbix:/home/aryel# zabbix_agentd localhost -t "net.dns.record[8.8.8.8,uol.com.br,A,2,1]"
net.dns.record[8.8.8.8,uol.com.br,A,2,1] [t|uol.com.br A 200.147.67.142
uol.com.br A 200.221.2.45]

O problema, é que me parece que o zabbix-server não está se comunicando com o zabbix-agent, ambos instalados no mesmo server.
Necessito que esta chamada que fiz via BASH seja feita por um item monitorado.

Tem uma luz?

**janssenreis** · 10-09-2015, 15:08

Tem algum firewall rodando aí no teu server?

Qual a versão do Zabbix que você está rodando?
Qual é a distribuição Linux?

Att,

Janssen dos Reis Lima

http://blog.janssenlima.com

http://www.conectsys.com.br

**[email protected]** · 10-09-2015, 15:11

Bom dia!

Esta máquina está no Google Compute Engine, firewall próprio da plataforma, porém está tudo liberado.

Estou utilizando Debain 7.8 weezy

**janssenreis** · 10-09-2015, 15:15

Copia aqui a configuração do zabbix_agentd.conf

Att,

Janssen dos Reis Lima

http://blog.janssenlima.com

http://www.conectsys.com.br

**[email protected]** · 10-09-2015, 15:22

Segue:
Code:
# This is a config file for the Zabbix agent daemon (Unix)
# To get more information about Zabbix, visit http://www.zabbix.com

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

### Option: PidFile
# Name of PID file.
#
# Mandatory: no
# Default:
# PidFile=/tmp/zabbix_agentd.pid

PidFile=/var/run/zabbix/zabbix_agentd.pid

### Option: LogFile
# Name of log file.
# If not set, syslog is used.
#
# Mandatory: no
# Default:
# LogFile=

LogFile=/var/log/zabbix/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

LogFileSize=0

### 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)
#
# Mandatory: no
# Range: 0-4
# Default:
# DebugLevel=3

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

### 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=127.0.0.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=127.0.0.1

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

ort (or hostname

ort) 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=Zabbix server

Hostname=zabbix

### 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' and 'logrt' active checks.
# The provided value will be overridden by the parameter 'maxlines',
# provided in 'log' or 'logrt' item keys.
#
# Mandatory: no
# Range: 1-1000
# Default:
# MaxLinesPerSecond=100

############ 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 the ID of user 'zabbix':
# Alias=zabbix.userid:vfs.file.regexp[/etc/passwd,^zabbix:.

[0-9]+),,,,\1]
# Now shorthand key zabbix.userid may be used to retrieve data.
# Aliases can be used in HostMetadataItem but not in HostnameItem parameters.
#
# Mandatory: no
# Range:
# Default:

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

### Option: AllowRoot
# Allow the agent to run as 'root'. If disabled and the agent is started by 'root', the agent
# will try to switch to the user specified by the User configuration option instead.
# Has no effect if started under a regular user.
# 0 - do not allow
# 1 - allow
#
# Mandatory: no
# Default:
# AllowRoot=0

### Option: User
# Drop privileges to a specific, existing user on the system.
# Only has effect if run as 'root' and AllowRoot is disabled.
#
# Mandatory: no
# Default:
# User=zabbix

### Option: Include
# You may include individual files or all files in a directory in the configuration file.
# Installing Zabbix will create include directory in /usr/local/etc, unless modified during the compile time.
#
# Mandatory: no
# Default:
# Include=

Include=/etc/zabbix/zabbix_agentd.d/

# Include=/usr/local/etc/zabbix_agentd.userparams.conf
# Include=/usr/local/etc/zabbix_agentd.conf.d/
# Include=/usr/local/etc/zabbix_agentd.conf.d/*.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>
# See 'zabbix_agentd' directory for examples.
#
# Mandatory: no
# Default:
# UserParameter=

####### LOADABLE MODULES #######

### Option: LoadModulePath
# Full path to location of agent modules.
# Default depends on compilation options.
#
# Mandatory: no
# Default:
# LoadModulePath=${libdir}/modules

### Option: LoadModule
# Module to load at agent startup. Modules are used to extend functionality of the agent.
# Format: LoadModule=<module.so>
# The modules must be located in directory specified by LoadModulePath.
# It is allowed to include multiple LoadModule parameters.
#
# Mandatory: no
# Default:
# LoadModule=

**janssenreis** · 10-09-2015, 15:48

Comenta as linhas dos parâmetros:

SourceIP
ListenIP

Reinicia o serviço do agent e faz o teste com o zabbix_get.

O teu server está resolvendo 'localhost'?

Att,

Janssen dos Reis Lima

http://blog.janssenlima.com

http://www.conectsys.com.br

Ad Widget

Problemas para Monitorar Registros de DNS

Problemas para Monitorar Registros de DNS

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment