No data in graphs

[Freaky]

hello,

Im new to this forum and this is my first post. Im an intern at a small IT company in the Netherlands. This company is thinking of using zabbix and it is my task to test zabbix in VM workstation.

I installed the pre configured vmx zabbix server, one debian client and one windows 7 client for testing.

The problem is that when i look at graphs for my windows machine it says no data everytime. I tried some things but nothing seems to help. The graphs for the zabbix server itself are working fine.

The server and windows machine are in the same, correct timezone and the time is running exactly the same. I assigned 2 cpu cores and 2gb of ram to the server in VMworkstation. I turned off the windows firewall.

It is possible for me to see the windows client in the frontend and its running without problems and all triggers are green. I added a windows baseline template to see some graphs and none of them is working.

Im kinda out of options.. Any help would be greatly apreciated!

Greetings,

[tchjts1]

When you go to Monitoring --> Latest Data and select your host, do you see any text values there for the items that are monitored?

[Freaky]

No, what does this mean?

[tchjts1]

Is your Windows host set to "Enabled" in the Zabbix frontend to be monitored?

Did you configure zabbix_agentd.conf correctly on your Windows host and is the Zabbix agent service up and running?

What does it say on your Windows host in zabbix_agentd.log?

How about on your Zabbix server in zabbix_server.log?

Those are a few basic checkpoints.

[Freaky]

Yes host is set to enabled. Zabbix service is running and i think the conf is correctly configured. This is what agent log says:

3288:20140918:154738.889 Starting Zabbix Agent [Windows box]. Zabbix 2.2.5 (revision 47406).
3288:20140918:154738.889 using configuration file: c:/zabbix/zabbix_agentd.win.conf
1668:20140918:154739.201 agent #0 started [collector]
3700:20140918:154739.217 agent #1 started[listener #1]
1864:20140918:154739.217 agent #2 started[listener #2]
3300:20140918:154739.217 agent #3 started[listener #3]
3236:20140918:154739.217 agent #4 started [active checks #1]
3236:20140918:154740.277 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: [0x0000274D]
1128:20140918:154745.176 Got signal. Exiting ...
3236:20140918:154745.363 zabbix_agentd active check stopped
1668:20140918:154745.815 zabbix_agentd collector stopped
1128:20140918:154746.190 Zabbix Agent stopped. Zabbix 2.2.5 (revision 47406).

So it stops. Why? is it supposed to try and connect to 127.0.0.1?

The server log seems normal(as far as i can tell) only this line isnt(last line):

zabbix_server [2454]: Is this process already running? Could not lock PID file [/var/run/zabbix/zabbix_server.pid]: [11] Resource temporarily unavaible

Thnx for the help so far!!

[tchjts1]

3288:20140918:154738.889 Starting Zabbix Agent [Windows box]. Zabbix 2.2.5 (revision 47406).
3236:20140918:154740.277 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: [0x0000274D]

You are telling your Windows server to report to itself by using 127.0.0.1
You need to edit your zabbix_agentd.conf file on your Windows server and make Server= and ServerActive= both have the IP address of your Zabbix server. Restart your Zabbix agent service after you make changes.

The server log seems normal(as far as i can tell) only this line isnt(last line):

zabbix_server [2454]: Is this process already running? Could not lock PID file [/var/run/zabbix/zabbix_server.pid]: [11] Resource temporarily unavaible

On the Dashboard page of Zabbix GUI under System Status widget, does it show "Zabbix Server is running"?

If so, maybe that error message is old and has been resolved.
If not, SSH into your Zabbix server and change to user zabbix, or whatever account you run Zabbix as. Can you access /var/run/zabbix/zabbix_server.pid? If not, may be a permissions issue.

[Freaky]

I changed server and server active to the correct address and seems to not change anything.

The frontend does tell me zabbix server is running and i can also access the pid file. It only contains: 2153

Anything else i can try?

[Freaky]

I feel like there is something wrong in my conf file because my log file keeps saying this: 2732:20141007:161932.039 active check configuration update from [192.168.244.131:10051] started to fail (cannot connect to [[192.168.244.131]:10051]: [0x0000274C]

My complete configuration file. I tried allot of different things with it but i think this is the way it is supposed to be:

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

LogFile=c:\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

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

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

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

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

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

[Freaky]

So i checked if port 10050 is open with a port checking tool(advanced port scanner) and it was not. So i googled for opening ports on zabbix server and found this:

By default, only two ports are open - 22 (SSH) and 80 (HTTP). To open additional ports - for example, Zabbix server and agent ports - modify iptables rules with SuSEfirewall2 utility:

SuSEfirewall2 open EXT TCP zabbix-trapper zabbix-agent

Then reload the firewall rules:

SuSEfirewall2 stop
SuSEfirewall2 start

So thats what i did and it seemed to work. My zabbix_agendt.log now doesnt show any errors anymore:

616:20141009:132203.293 Starting Zabbix Agent [WIN-FUOUUCL9QHN]. Zabbix 2.4.0 (revision 48940).
616:20141009:132203.293 using configuration file: C:\Program Files\Zabbix Agent\zabbix_agentd.conf
616:20141009:132203.293 agent #0 started [main process]
1796:20141009:132203.293 agent #1 started [collector]
3104:20141009:132203.340 agent #2 started[listener #1]
2284:20141009:132203.340 agent #3 started[listener #2]
320:20141009:132203.340 agent #4 started[listener #3]
2812:20141009:132203.340 agent #5 started [active checks #1]

When i run the port checking tool again it still says only 22 and 80 are open. The graphs also dont work yet. What did this command change? and why is port 10050 closed by default? Seems very illogical to me since the agent needs it to be open to communicate.

Also my debian agent worked from the start, doesnt it use the same port as the windows agent?

[tchjts1]

Not sure, but maybe try opening the ports by the port number.

SuSEfirewall2 open EXT TCP 10050
SuSEfirewall2 open EXT TCP 10051
SuSEfirewall2 start

Maybe also try going with the 2.2.5 agent on your Windows server instead of 2.4.0. See if that makes a difference.

[Freaky]

Thanks! i got it working finally. The commands to open the firewall ports did the trick!

[Freaky]

We are planning to use zabbix for our company. How well will zabbix function over WAN? We need to install a lot of agents on other company networks. I understand this can be done by using active agents. Does this give us the same functionality as passive agents?