1st Time Zabbix User

[HeinZbx]

I recently downloaded and installed Zabbix 4.2 on Ubuntu 18.04 LTS.

The interface is very clean and it looks like a very handy tool, though at the moment I am having one simple problem.

For some reason when I try to add a host it does not seem to show up.
Going to the dashboard it shows up as Number of Hosts (enable/disabled/templates) 2 / 0 /83.

I installed the agent on the server I want to administer.

This is the configuration I have on the server.

LogFile=c:\zabbix_agentd.log
#to just get some traffic going
DebugLevel=5
#Internal IP of Zabbix
Server=192.168.56.49
#Internal IP of the Windows Server
ListenIP=192.168.56.15
ServerActive=192.168.56.49
Hostname=TestServer
HostnameItem=TestServer

The server is Windows 2016 Server that I want to track memory, CPU and HDD usage.

Am I missing something? My logs are telling me it is connecting, but it does not seem to be sending any entries.

16120:20190812:123417.258 In send_buffer() host:'192.168.56.49' port:10051 entries:0/100
16120:20190812:123417.258 End of send_buffer():SUCCEED
17108:20190812:123417.712 In collect_perfstat()
17108:20190812:123417.715 End of collect_perfstat()
16120:20190812:123418.274 In send_buffer() host:'192.168.56.49' port:10051 entries:0/100
16120:20190812:123418.275 End of send_buffer():SUCCEED

I stopped my Zabbix agent and restarted it to get to the boot logs.

12620:20190812:124036.389 Starting Zabbix Agent [TestServer]. Zabbix 4.2.4 (revision 059af02).
12620:20190812:124036.390 **** Enabled features ****
12620:20190812:124036.390 IPv6 support: YES
12620:20190812:124036.391 TLS support: NO
12620:20190812:124036.392 **************************
12620:20190812:124036.393 using configuration file: C:\Zabbix\zabbix_agentd.conf
12620:20190812:124036.394 In init_collector_data()
12620:20190812:124036.394 End of init_collector_data()
12620:20190812:124036.395 In init_perf_collector()
12620:20190812:124036.399 End of init_perf_collector():SUCCEED
12620:20190812:124036.399 agent #0 started [main process]
13536:20190812:124036.400 agent #1 started [collector]
12736:20190812:124036.401 agent #2 started[listener #1]
13588:20190812:124036.401 agent #5 started [active checks #1]
14544:20190812:124036.402 agent #3 started[listener #2]
9648:20190812:124036.403 agent #4 started[listener #3]
13536:20190812:124036.403 In init_cpu_collector()
13588:20190812:124036.404 In init_active_metrics()
13536:20190812:124036.404 In get_counter_name() pdhIndex:238
13588:20190812:124036.405 buffer: first allocation for 100 elements
13588:20190812:124036.405 End of init_active_metrics()
13588:20190812:124036.406 In send_buffer() host:'192.168.56.49' port:10051 entries:0/100
13588:20190812:124036.406 End of send_buffer():SUCCEED
13588:20190812:124036.407 In refresh_active_checks() host:'192.168.56.49' port:10051
13588:20190812:124036.408 sending [{"request":"active checks","host":"TestServer","ip":"192.168.56.15"}]

Under the Zabbix web frontend, I go to Inventory => Hosts and that list just seems to stay empty.

[alientm]

maybe a stupid question, but did you add a host to monitor in Zabbix frontend (Configuration - Hosts - Add hosts)?

[HeinZbx]

Hi, apologies for the late reply, I have reinstalled the server and it seems to be giving me the same issue.

Under the availability, nothing is highlighted, even though the ports are open.
I am seeing traffic from VDC-PSI-QLIK (192.168.56.32) to my Zabbix server (192.168.56.49).
tcpdump is showing a bit of traffic every now and then, yet I don't see anything.

The zabbix_agentd.log is saying everything is apparently started:

1440:20190912:103712.838 Starting Zabbix Agent [VDC-PSI-QLIK]. Zabbix 4.2.6 (revision d3bb18bbc4).
1440:20190912:103712.839 **** Enabled features ****
1440:20190912:103712.841 IPv6 support: YES
1440:20190912:103712.841 TLS support: YES
1440:20190912:103712.842 **************************
1440:20190912:103712.843 using configuration file: C:\Program Files\Zabbix Agent\zabbix_agentd.conf
1440:20190912:103712.845 agent #0 started [main process]
7240:20190912:103712.847 agent #1 started [collector]
3836:20190912:103712.848 agent #3 started[listener #2]
7252:20190912:103712.854 agent #5 started [active checks #1]
3644:20190912:103712.854 agent #2 started[listener #1]
1220:20190912:103712.855 agent #4 started[listener #3]
852:20190912:104130.935 Zabbix Agent stopped. Zabbix 4.2.6 (revision d3bb18bbc4).
7452:20190912:104142.594 Starting Zabbix Agent [VDC-PSI-QLIK]. Zabbix 4.2.6 (revision d3bb18bbc4).
7452:20190912:104142.595 **** Enabled features ****
7452:20190912:104142.596 IPv6 support: YES
7452:20190912:104142.596 TLS support: YES
7452:20190912:104142.597 **************************
7452:20190912:104142.597 using configuration file: C:\Program Files\Zabbix Agent\zabbix_agentd.conf
7452:20190912:104142.600 agent #0 started [main process]
6064:20190912:104142.601 agent #1 started [collector]
4416:20190912:104142.602 agent #2 started[listener #1]
8124:20190912:104142.604 agent #4 started[listener #3]
6728:20190912:104142.605 agent #3 started[listener #2]
2124:20190912:104142.606 agent #5 started [active checks #1]

I have zabbix_agentd.conf on VDC-PSI-QLIK configured as such:

# 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:\Program Files\Zabbix Agent\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, optionally in CIDR notation, or DNS names of Zabbix servers and Zabbix proxies.
# 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 and '::/0' will allow any IPv4 or IPv6 address.
# '0.0.0.0/0' can be used to allow any IPv4 address.
# Example: Server=127.0.0.1,192.168.1.0/24,::1,2001:db8::/32,zabbix.domain
#
# Mandatory: yes, if StartAgents is not explicitly set to 0
# Default:
Server=192.168.56.49

Server=192.168.56.49

### 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
ListenIP=192.168.56.32

### 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 DNS nameort) pairs of Zabbix servers and Zabbix proxies 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=192.168.56.49

### 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=VDC-PSI-QLIK

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

Include=C:\Program Files\Zabbix Agent\zabbix_agentd.conf.d\

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

[HeinZbx]

Are the forums this quiet that almost 3 weeks there is no response? As much as I love to support open-source the lack of feedback can get you quite despondent.

[Atsushi]

If you want to monitor the server, you need to add monitoring settings. In addition to registering the host, monitoring will not start unless you link the template or create an item. If you want to monitor a Windows server, try linking a Windows template(ex. Template OS Windows).

https://www.zabbix.com/documentation/4.2/manual/config/hosts/host