Page 1 of 3

Nagiosgraph dont collect data from passive checked hosts

Posted: Mon Mar 24, 2014 6:46 am
by mkot
Hi, a few days ago I configured active checking for linux hosts via check_nrpe plugin. After this nagios graph stopped collecting data from passive checked hosts. It collects data only from active checked hosts.
I configured nagiosgraph via this procedure:
http://www.linuxfunda.com/2013/04/02/st ... gios-core/

My command.cfg file

Code: Select all

# Dodane 2014-03-06 - mkot
# 'check_nrpe' command definition
define command{
        command_name    check_nrpe
        command_line    /usr/bin/perl $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ -t 20
        }

# Monitorowanie obciążenia CPU
define command{
        command_name    check_cpu
        command_line    /usr/bin/perl $USER1$/check_nrpe -$HOSTADDRESS$ -s passwd -p 5667 -c $ARG1$
        }


# Monitorowanie obciążenia HDD
define command{
        command_name    check_disk
        command_line    /usr/bin/perl $USER1$/check_nrpe -$HOSTADDRESS$ -s passwd -p 5667 -c $ARG1$
        }


# Monitorowanie obciążenia RAM
define command{
        command_name    check_mem
        command_line    /usr/bin/perl $USER1$/check_nrpe -$HOSTADDRESS$ -s passwd -p 5667 -c $ARG1$
        }
# KONIEC - 2014-03-06 - mkot

And some active and passive services definitions:
act:

Code: Select all


# CPU Load - aktywne monitorowanie
define service{
        use                     generic-service,nagiosgraph
        hostgroup_name          Serwery Windows WA
        service_description     CPU Load
        check_command           check_nt!CPULOAD!-l 5,80,85
        notification_interval   60
        notification_options    w,c
        notification_period     24x7
        flap_detection_enabled  0
        active_checks_enabled   1
        passive_checks_enabled  0
        }
pass:

Code: Select all


define service{
        use                     generic-service,nagiosgraph
        hostgroup_name          TAIWA
        service_description     CPU Load
        check_command           check_nrpe!CPU Load
        notification_options    w,c
        flap_detection_enabled  0
        active_checks_enabled   0
        passive_checks_enabled  1
        }


EDIT:
And host nsclient.ini (pass):

Code: Select all

[/settings/external scripts/alias]

; alias_cpu - Alias for alias_cpu. To configure this item add a section called: /settings/external scripts/alias/alias_cpu
alias_cpu = checkCPU warn=50 crit=80 time=5m time=1m time=30s

; alias_disk - Alias for alias_disk. To configure this item add a section called: /settings/external scripts/alias/alias_disk
alias_disk_c = CheckDriveSize MinWarn=2% MinCrit=1% Drive=C FilterType=FIXED

; alias_mem - Alias for alias_mem. To configure this item add a section called: /settings/external scripts/alias/alias_mem
alias_mem = checkMem MaxWarn=85% MaxCrit=90% ShowAll=long type=physical

[/settings/scheduler/schedules]
CPU Load tmp=alias_cpu
MEM Load=alias_mem
DISK Load C=alias_disk_c

EDIT2:
I think I know why Nagios graph don't collect data - hosts can't send notifications, sample of log from one host:

Code: Select all

2014-03-24 13:09:45: e:..\..\..\..\trunk\modules\NSCAClient\NSCAClient.cpp:435: Error: Retry failed
2014-03-24 13:12:39: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:12:39: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:12:39: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:12:39: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:12:39: e:..\..\..\..\trunk\modules\NSCAClient\NSCAClient.cpp:435: Error: Retry failed
2014-03-24 13:17:32: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:17:32: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:17:32: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:17:32: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:17:32: e:..\..\..\..\trunk\modules\NSCAClient\NSCAClient.cpp:435: Error: Retry failed
2014-03-24 13:19:45: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:19:45: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:19:45: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:19:45: e:D:\source\nscp\trunk\include\socket/client.hpp:149: Failed to read data: End of file
2014-03-24 13:19:45: e:..\..\..\..\trunk\modules\NSCAClient\NSCAClient.cpp:435: Error: Retry failed
I think it all started when I installed check_nrpe plugin at my Nagios Serwer and configured active monitoring for linux hosts :( Can anyone help me with this issue?

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Mon Mar 24, 2014 3:52 pm
by lmiltchev
Do you have the following line in the "nsclient.ini"?

Code: Select all

NSClientServer = 1

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Tue Mar 25, 2014 1:11 am
by mkot
Yes, I have. I think that I messed up with setting nsca and nrpe at Nagios serwer. I configured nsca for passive checks at Windows hosts and nrpe for active checks for Linux hosts. And when I did it, nsca was 'disabled' - I didn't get informations wrom Windows hosts. I need to figure out how can I configure nsca (passive checks) at Linux (Ubuntu, CentOS, FreeBSD) hosts. I know there is manual for this http://nagios.sourceforge.net/download/ ... _Setup.pdf but I cant figure out how configure services for checking amount of HDD (/, /home, /mnt/backup, etc), MEM and CPU Usage.

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Tue Mar 25, 2014 2:43 pm
by slansing
You should be able to use additional plugins, you just need to add them into your nsca.cfg file to be ran when cron hits it, that should be outlined in the nsca.cfg examples in that document.

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Wed Mar 26, 2014 4:05 pm
by mkot
Hi, I think you may close this thread. Nagiosgraph's collecting data. I need to focus at another thing - configure nrpe for active monitoring Linux hosts: http://support.nagios.com/forum/viewtop ... 423#p93423.

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Tue Apr 01, 2014 2:54 pm
by slansing
mkot will be posting an update here as he is still experiencing issues, re-opening thread.

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Tue Apr 01, 2014 3:26 pm
by mkot
Hi, I still get errors from Nagiosgraph. I don't know what can I do for resolve these issues:

Code: Select all

Tue Apr  1 22:23:50 2014 insert.pl error RRDs::update ERR /usr/local/nagiosgraph/var/rrd/BACKUP-TAI/D%3A%5C%20Drive%20Space___d%3A%5C%20Used%20Space.rrd: conversion of '1825,75' to float not complete: tail ',75'
Tue Apr  1 22:23:50 2014 insert.pl error ds = [
  '/usr/local/nagiosgraph/var/rrd/BACKUP-TAI/D%3A%5C%20Drive%20Space___d%3A%5C%20Used%20Space.rrd',
  '1396383826:893:1825,75:1844,38:0.00:1863,01'
];
Tue Apr  1 22:24:00 2014 insert.pl error RRDs::update ERR /usr/local/nagiosgraph/var/rrd/CALLCENTER/C%3A%5C%20Drive%20Space___c%3A%5C%20Used%20Space.rrd: conversion of '19,14' to float not complete: tail ',14'
Tue Apr  1 22:24:00 2014 insert.pl error ds = [
  '/usr/local/nagiosgraph/var/rrd/CALLCENTER/C%3A%5C%20Drive%20Space___c%3A%5C%20Used%20Space.rrd',
  '1396383834:12:19,14:19,34:0.00:19,53'
];
Tue Apr  1 22:24:00 2014 insert.pl error RRDs::update ERR /usr/local/nagiosgraph/var/rrd/BACKUP-TAI/C%3A%5C%20Drive%20Space___c%3A%5C%20Used%20Space.rrd: conversion of '38,28' to float not complete: tail ',28'
Tue Apr  1 22:24:00 2014 insert.pl error ds = [
  '/usr/local/nagiosgraph/var/rrd/BACKUP-TAI/C%3A%5C%20Drive%20Space___c%3A%5C%20Used%20Space.rrd',
  '1396383835:25:38,28:38,67:0.00:39,06'
1. I know that Nagiosgraph (rrd) don't get values with ",". It need to be ".", but how can I hange it? I'm from Poland and we separate decimals by commas (","), not by dot ("."). Is there a method to force Nagios graph collecting data with commas? Or make it cut all after comma?

2. What is "error ds" mean? Is it linked with "error RRDs::update ERR"?

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Tue Apr 01, 2014 4:36 pm
by abrist
mkot wrote:1. I know that Nagiosgraph (rrd) don't get values with ",". It need to be ".", but how can I hange it? I'm from Poland and we separate decimals by commas (","), not by dot ("."). Is there a method to force Nagios graph collecting data with commas?
Changing the locale for the server, or at least the nagios and apache users may do it. Other wise you will need to edit insert.pl and replace commas with decimal dots.
mkot wrote: Or make it cut all after comma?
That is a possibility as well, but you will lose precision.
mkot wrote:2. What is "error ds" mean? Is it linked with "error RRDs::update ERR"?
"ds" is an abbreviation for "DATASOURCE" - essentially one of the data tracks in an rrd.

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Tue Apr 01, 2014 11:35 pm
by mkot
1. You mean I should change locale for Nagios Server or monitored host?

2. My /usr/local/nagiosgraph/bin/insert.pl is:

Code: Select all

#!/usr/bin/perl
# $Id$
# License: OSI Artistic License
#          http://www.opensource.org/licenses/artistic-license.php
# Author:  (c) Soren Dossing, 2005
# Author:  (c) Alan Brenner, Ithaka Harbors, 2008
# Author:  (c) Matthew Wall, 2010
#
# NAME
# insert.pl - Store performance data returned by Nagios plugins using rrdtool.
#
# USAGE
# There are two standard processing configurations: batch and immediate.
#
# Batch Mode
# Nagios periodically invokes insert.pl.  Data are extracted from the Nagios
# perflog file.
#
# Immediate Mode
# Nagios invokes insert.pl on each service check.  Data are extracted from the
# command line.
#
# CONFIGURATION
# The nagiosgraph.conf file controls the behavior of this script.
#
# DIAGNOSTICS
# Use the debug_insert setting in nagiosgraph.conf to control the amount of
# logging information that will be emitted by this script.  Output will go
# to the nagiosgraph log file.


# The configuration file and ngshared.pm must be in this directory:
use lib '/usr/local/nagiosgraph/etc';

use ngshared;
use strict;
use warnings;

use constant MINPOLL => 30;    ## no critic (ProhibitConstantPragma)

use vars qw($VERSION);
$VERSION = '2.0.2';

my $errmsg = readconfig('insert');
if ( $errmsg ne q() ) { croak $errmsg; }
debug( DBDEB, 'insert.pl processing started' );
$errmsg = checkrrddir('write');
if ( $errmsg ne q() ) { croak $errmsg; }

# Read the map file and define a subroutine that parses performance data
$errmsg = getrules( $Config{mapfile} );
if ( $errmsg ne q() ) { croak $errmsg; }

if ( $ARGV[0] ) {
    processdata( $ARGV[0] );
}
elsif ( defined $Config{perfloop} && $Config{perfloop} > 0 ) {
    my $poll = ( $Config{perfloop} < MINPOLL ) ? MINPOLL : $Config{perfloop};
    debug( DBINF, 'insert.pl using poll interval of ' . $poll . ' seconds' );
    while (1) {
        my @perfdata = readperfdata( $Config{perflog} );
        if (@perfdata) { processdata(@perfdata); }
        debug( DBDEB, 'insert.pl waiting for input' );
        sleep $poll;
    }
}
else {
    my @perfdata = readperfdata( $Config{perflog} );
    if (@perfdata) { processdata(@perfdata); }
}

debug( DBDEB, 'insert.pl processing complete' );
And my /usr/local/nagiosgraph/etc/nagiosgraph.conf is:

Code: Select all

# nagiosgraph configuration file
#
# $Id: nagiosgraph.conf 492 2011-01-15 06:26:55Z mwall $
# License: OSI Artistic License
#          http://www.opensource.org/licenses/artistic-license.php
# Author:  (c) 2005 Soren Dossing
# Author:  (c) 2008 Alan Brenner, Ithaka Harbors
# Author:  (c) 2010 Matthew Wall

# Location of output from nagiosgraph data processing
logfile = /usr/local/nagiosgraph/var/nagiosgraph.log

# Location of output from nagiosgraph CGI scripts
cgilogfile = /usr/local/nagiosgraph/var/nagiosgraph-cgi.log

# Location of nagios performance data log file.
perflog = /tmp/perfdata.log

# Directory in which to store RRD files
rrddir = /usr/local/nagiosgraph/var/rrd

# File containing regular expressions to identify service and perf data
mapfile = /usr/local/nagiosgraph/etc/map

# Nagiosgraph CGI URL.
nagiosgraphcgiurl = /nagiosgraph/cgi-bin

# Nagios CGI URL.  If the Nagiosgraph CGI scripts are in a directory other
# than the Nagios CGI directory, then specify the Nagios CGI URL here.
nagioscgiurl = /nagios/cgi-bin

# JavaScript: URL to the nagiosgraph javascript file.
javascript = /nagiosgraph/nagiosgraph.js

# Stylesheet: URL to the nagiosgraph stylesheet.
stylesheet = /nagiosgraph/nagiosgraph.css

# File containing labels for services and data (optional)
labelfile = /usr/local/nagiosgraph/etc/labels.conf

# Location of showhost control file (optional)
#hostdb = /etc/nagiosgraph/hostdb.conf

# Location of showservice control file (optional)
#servdb = /etc/nagiosgraph/servdb.conf

# Location of showgroup control file (required for showgroup.cgi)
groupdb = /usr/local/nagiosgraph/etc/groupdb.conf

# File containing data sets that should be selected in queries (optional)
datasetdb = /usr/local/nagiosgraph/etc/datasetdb.conf

# Access control configuration (optional)
# The authorization method can be one of nagios3 or nagiosgraph.  If no
# method is defined, access will be granted to all hosts and services.

# For access control via nagios, specify the nagios configuration files.
# Nagios3 defaults to use authentication.  nagiosgraph looks for the
# use_authentication variable to determine whether authentication is enabled.
# If authentication is enabled, nagiosgraph looks for the
# authorized_for_all_hosts, authorized_for_all_services, and default_user_name
# variables to determine permissions.
#authzmethod = nagios3
#authzfile = /etc/nagios/cgi.cfg

# For access control via nagiosgraph, specify a single access control file.
# See the sample access control file for syntax and examples.
#authzmethod = nagiosgraph
#authzfile = /etc/nagiosgraph/access.conf


# Logging can be enabled for a specific CGI script and/or specific hosts or
# services.  When level is set to 5, the logs will see a lot of extra output,
# so be sure to reset the level when you have finished debugging.

# Log Levels
# 0 = None
# 1 = Critical
# 2 = Error
# 3 = Warn
# 4 = Info
# 5 = Debug
debug = 2

### log level for specific scripts
# log level for insert.pl
#debug_insert = 5
# if this is set to a hostname, then only log for this host
#debug_insert_host = host1
# if this is set to a service, then only log for this service
#debug_insert_service = PLW
# *_host and *_service together for a specific service on a specific host.
# log level for show.cgi
#debug_show = 5
#debug_show_host = host1
#debug_show_service = ping
# log level for showhost.cgi
#debug_showhost = 5
#debug_showhost_host = host1
#debug_showhost_service = ping
# log level for showservice.cgi
#debug_showservice = 5
#debug_showservice_host = host1
#debug_showservice_service = ping
# log level for showgroup.cgi
#debug_showgroup = 5
#debug_showgroup_host = host1
#debug_showgroup_service = ping
# log level for showgraph.cgi
#debug_showgraph = 5
#debug_showgraph_host = host1
#debug_showgraph_service = ping
# log level for testcolor.cgi
#debug_testcolor = 5
# graph sizes
geometries = 650x50,800x100,1000x200,2000x100

# default graph size (optional)
#default_geometry = 600x100

# Color scheme for graphs.  There are 8 pre-defined schemes (1-8) and one
# custom scheme (9).  The pre-defined schemes use a color based on the
# characters in the name of each data source.  The custom scheme uses each
# color, in order.  Use testcolor.cgi to see what the color schemes
# look like and how they apply to specific service and data set names.
colorscheme = 9

# Custom color scheme is defined by a comma-separated list of RGB hex colors.
# rainbow: reddish, orange, yellow, green, light blue, dark blue, purple, grey
#colors = D05050,D08050,D0D050,50D050,50D0D0,5050D0,D050D0,505050
# light/dark pairs: blue, green, purple, orange
colors = 90d080,30a030,90c0e0,304090,ffc0ff,a050a0,ffc060,c07020
# green from light to dark
#colors = 80d080,50a050,308030

# Colors for the maximum and minimum values, applied to the data for services
# in withmaximums and withminimums
#colormax = 888888
#colormin = BBBBBB

# Default line style (LINE1, LINE2, LINE3, AREA, TICK); see rrdgraph_graph
plotas = LINE2

# Line styles for specific data sources.
#
# Each style is a list of qualified data source names separated by semicolons.
# A single qualified data source must end with a semicolon.
#   [[[host,]service,]database,]datasource;[[[h2,]s2,]db2,]ds2
# The old-style specification is deprecated:
#   datasource1[,datasource2[,datasource3[,...]]]
#
# For example, this uses LINE3 for all PING sources called 'data' from acme.com
#   plotasLINE3 = .*.acme.com,PING,.*,data;
plotasLINE1 = load5,data;load15,data
plotasLINE2 =
plotasLINE3 =
plotasAREA = idle,data;system,data;user,data;nice,data
plotasTICK =

# Data sources that should be stacked.
#
# This is a list of qualified data source names separated by semicolons.
# A single qualified data source must end with a semicolon.
stack = system,data;user,data;nice,data

# Data sources whose value should be negated.
#
# This is a list of qualified data source names separated by semicolons.
# A single qualified data source must end with a semicolon.
#negate = byte-received;drop-received;error-received;multi-received;packet-received
# Specify line formats per data source.  This is a semicolon-separated list of
# line format specifications.  Each format specification contains:
#   [[[host,]service,]database,]ds-name=linestyle[,color][,STACK]
# The old-style specification is deprecated:
#   ds-name,linestyle[,color][,STACK]
#
# For example, this plots every data source called 'crit' as a thin red line:
#lineformat = crit=LINE1,D05050
# This stacks system, nice, and idle onto whatever sources come before them:
#lineformat = system=AREA,FFAAAA;nice=AREA,AAAAFF,STACK;idle,AREA,AAFFAA,STACK
# If the data sources have the same name but different database files, qualify
# them by leading with the database (and service and host, if necessary).
#lineformat = nice,data=AREA,AAAAFF,STACK;idle,data=AREA,AAFFAA,STACK
lineformat = warn=LINE1,D0D050;crit=LINE1,D05050

# Graphs to show in host-service page (day, week, month, quarter, year)
timeall = day,week,month,year
# Graphs to show in host page
timehost = day,week,month
# Graphs to show in service page
timeservice = day,week,month
# Graphs to show in group page
timegroup = day,week,month

# Time periods that should default to expanded state.  If not specified here,
# the period will default to a collapsed state.
expand_timeall = day,week,month,year
expand_timehost = week
expand_timeservice = week
expand_timegroup = day

# Formats for time and date.
timeformat_now = %H:%M:%S %d %b %Y %Z
timeformat_day = %H:%M %e %b
timeformat_week = %e %b
timeformat_month = Week %U
timeformat_quarter = Week %U
timeformat_year = %b %Y

# Set this to automatically refresh the web page.  Value is number of seconds.
#refresh = 300

# Set this to hide the nagiosgraph title (useful when nagiosgraph is
# embedded in the nagios frame).
#hidengtitle = true

# Set this to show in the footer the time spent generating the page.
#showprocessingtime = true

# Set this to display a title for each graph in html.  When appropriate, the
# title also includes links to other views of each host and/or service.
showtitle = true

# Set this to display a description for each graph in html.
#showdesc = true
# Set this to put a title in each graph.
#showgraphtitle = true

# Set this to hide the legend in each graph.
#hidelegend = true

# Set this to display only the graph data - no axes, grid, or legend.
#graphonly = true

# For services listed here, graphs that contain averages (e.g. weekly, monthly)
# will include maximum/minimum values as well.  This is useful for services
# such as ping or http transfer rates so that you see not only the average
# values, but also the maximum and minimum values over time.  Each is a list
# of services separated by commas.
# These are not related to the RRA maximum, minimum, or last (defined below).
withmaximums = PING,HTTP
withminimums = PING,HTTP

# Scaling parameters, see the rrdgraph documentation for use
# Separate multiple services to add the -A option to by commas
#altautoscale = service1,service2
# Separate multiple services to add the -J option to by semicolons, and use a
# command to separate the service name from the desired value
#altautoscalemin = service1,min1;service2,min2
# Separate multiple services to add the -M option to by semicolons, and use a
# command to separate the service name from the desired value
#altautoscalemax = service1,max1;service2,max2
# Separate multiple services to add the -N option to by commas
#nogridfit = service1,service2
# Separate multiple services to add the -o option to by commas
#logarithmic = service1,service2

# Specify rrd graph options that apply to all graphs
#rrdopts=--border 0 --color BACK#ffffff

# Optional - define rrdopts override file, this enables you to specify
# particular rrdgraph options against each service.
#rrdoptsfile=/etc/nagiosgraph/rrdopts.conf

# If perfloop is set, insert.pl will loop waiting for input data.  The value
# is the polling interval, in seconds.  Set this only if you intend to run
# insert.pl independently of Nagios.
#perfloop = 30

# The heartbeat, stepsize, and resolution are rrdtool parameters.  They are
# used when RRD files are created.  Changes to these values have no effect
# on existing RRD files.  See the rrdtool documentation for details.
# These values must be coordinated with nagios service check settings and
# the nagiosgraph data processing interval.

# RRD heartbeat, in seconds.  This defines the maximum length of an interval
# with no data update before rrd considers the data unknown.  Typically twice
# the size of servicecheck interval.  600 is the rrdtool default.
#heartbeat = 600
# Specify a heartbeat for specific hosts and services.
#heartbeats = HOST,SERVICE,DATABASE=1200;HOST,SERVICE,.*=1800;.*,.*,.*=600

# RRD step size, in seconds.  This defines how often the data will be updated.
# Typically the size of the servicecheck interval.  300 is the rrdtool default.
#stepsize = 300
# Specify a step size for specific hosts and services.
#stepsizes = HOST,SERVICE,DATABASE=600;HOST,SERVICE,.*=1200;.*,.*,.*=300

# RRD parameters.  These numbers control the number of stored data values
# and thus RRD file size.  They are used when creating RRD files.
# Each RRD file is created with 4 lines of RRA arguments:
#   RRA:(AVERAGE|MIN|MAX|LAST):xff:step1:row1
#   RRA:(AVERAGE|MIN|MAX|LAST):xff:step2:row2
#   RRA:(AVERAGE|MIN|MAX|LAST):xff:step3:row3
#   RRA:(AVERAGE|MIN|MAX|LAST):xff:step4:row4
#
# Using default values, the RRAs are as follows:
#   RRA:AVERAGE:0.5:1:600
#   RRA:AVERAGE:0.5:6:700
#   RRA:AVERAGE:0.5:24:775
#   RRA:AVERAGE:0.5:288:797
#
# The rows are defined by the four resolution values.
# The default results in RRD files that are 20K to 75K in size:
#resolution = 600 700 775 797
# These values keep many more data points, but result in much larger files:
#resolution = 17280 17520 32850 1095
# Specify resolution for specific hosts and services.
#resolutions = HOST,SERVICE,.*=17280 17520 32850 1095;.*,.*,.*=600 700 775 797
#
# The steps are defined by the four step values.
# The default results in consolidated data points for day, week, month, year
#step = 1 6 24 288
# Specify step for specific hosts and services.
#steps = HOST,SERVICE,.*=1 12 48 596;.*,.*,.*=1 6 24 288
#
# The xff (xfiles factor) defines what part of a consolidation interval may be
# made up from UNKNOWN data while the consolidated value is still regarded as
# known.  It is given as the ratio of allowed UNKNOWN PDPs to the number of
# PDPs in the interval.  It ranges from 0 to 1, exclusive.
#xff = 0.5
# Specify xff for specific hosts and services.
#xffs = HOST,SERVICE,.*=0.9;.*,.*,.*=0.5

# By default, each RRD records average values.  To record maximum, minimum, or
# last value instead of the average value, specify the service and database
# names here, optionally qualified by hostname.
#   [host,]service,database;[[host,]service2,database][;...]
# The old-style specification is deprecated:
#   service1[,service2[,service3[,...]]]
#maximums = .*.acme.com,service1,.*;
#maximums = host1,service1,database;service2,database2;.*.acme.com,service3,.*
maximums = Current Load,.*;Current Users,.*;Total Processes,.*;PLW,.*
minimums =
lasts =
# This lists data that need to go into separate rrd files.  This is used
# when creating new rrd files when a change to the map is not possible.  Use
# this to segregate a value from other returned values for a specific host.
# Each entry consists of a comma separated set of host,service,value.  Separate
# each set with a semicolon.
#hostservvar = server1,service1,val1;server2,service2,val2
#hostservvar = host2,PLW,smtp_error

# Organization of RRD files.  There are two ways to organize the RRD files:
# flat : all in a single directory (the old way):
#   rrddir/HOST_SERVICE_DATABASE.rrd
# subdir : organized by host (the new way):
#   rrddir/HOST/SERVICE___DATABASE.rrd
dbseparator = subdir

# Optionally force the language.  If no language is specified, the language
# is determined from the browser environment or explicit cgi argument.  The
# possible values are standard language/country codes such as es, fr, de,
# en_US, en_UK, ...  If there is no corresponding language file, the language
# reverts to english.
#language = es

# JavaScript must be enabled for full functionality.  But if you need to
# disable it and you do not want the warnings, this lets you hide them.
#hidejswarnings = 1


so what should be changed?


EDIT:
and my Nagios Server i]locale[/i]:

Code: Select all

tai@nagios:~$ locale
LANG=pl_PL.UTF-8
LANGUAGE=
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME="en_US.UTF-8"
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT="en_US.UTF-8"
LC_IDENTIFICATION="en_US.UTF-8"
LC_ALL=en_US.UTF-8

Re: Nagiosgraph dont collect data from passive checked hosts

Posted: Wed Apr 02, 2014 4:51 pm
by abrist
mkot wrote:1. You mean I should change locale for Nagios Server or monitored host?
Depends. Before we start change locales on your systems, could you run one of the check_nt checks from the cli? I want to see if the remote system is returning the commas, or if the rrd perl scripts are changing it.
Run one of the check_nt commands from your nagios server against one of your windows hosts and post the output.