Sponsored Content
Special Forums UNIX and Linux Applications Infrastructure Monitoring (Nagios)printer error on verify...WHY?? Post 302997264 by rgouette on Wednesday 10th of May 2017 12:48:39 PM
Old 05-10-2017
Quote:
Originally Posted by Corona688
Please use code tags for code, that is the Image button.


better?

---------- Post updated at 12:48 PM ---------- Previous update was at 11:27 AM ----------

Disregard post: I found my problem.

I wasn't using the printer.cfg file, and I WAS for servers, which explains why
server group is fine, and printers weren't.

The hostgroup definitions were found in those config files, so now
printers have a valid hostgroup name reference.

cheers,
Rich
These 2 Users Gave Thanks to rgouette For This Post:
 

8 More Discussions You Might Find Interesting

1. Linux

Error While retriving Host details from Nagios

Whoops! Error: Could not read object configuration data! Here are some things you should check in order to resolve this error: 1. Verify configuration options using the -v command-line option to check for errors. 2. Check the Nagios log file for messages relating to startup or... (0 Replies)
Discussion started by: manian_balu
0 Replies

2. Infrastructure Monitoring

Nagios - NRPE configuration error

HI guyz, I have a nagios 3.0.6 server which is running on fedora 5. I had already added some windows clients and monitoring it. Now i want to add a unix client. Steps done till now : - 1.nagios-plugins-1.4.13 was installed and configured. 2.unzipped and untarred the NRPE 2.8 3.I gave a... (0 Replies)
Discussion started by: Renjesh
0 Replies

3. Infrastructure Monitoring

configure nrpe and nagios error

   (1)check the service of nrpe   # libexec/check_nrpe -H 59.26.240.63   NRPE v2.8.1    (2)check the resource of nrpe's host   # libexec/check_nrpe -H 59.26.240.63 -c check_df   DISK OK - free space: / 8241 MB (77% inode=98%); /var 5239 MB (95% inode=99%); /usr 11971 MB (86%... (0 Replies)
Discussion started by: zhengsenlin
0 Replies

4. UNIX and Linux Applications

NRPE check_disk error [nagios,solaris]

Good morning folks, I'm having a problem with check_disk with mounted 3TB volumes. It appears that the value being returned by stavfs is too large to be processed by the check_disk plugin. Does anyone know of an updated check_disk plugin? Solaris 10: # /usr/local/nagios/libexec/check_disk -w... (0 Replies)
Discussion started by: avronius
0 Replies

5. Infrastructure Monitoring

Nagios Error

Im new to monitoring so i was testing few monitoring tools and I've had this problem with nagios, i downloaded the Nagios XI VM and im using virtualbox to run it and when i reach the GRUB i get this Error 16 : inconsistent file system structure, i have tried troubleshooting the problem but i... (1 Reply)
Discussion started by: HashB
1 Replies

6. UNIX for Dummies Questions & Answers

SSL3_GET_SERVER_CERTIFICATE:certificate verify failed error

I was building my code base firing ./configure and it gave me error: configure: error: "audit system headers required (PKG: audit-devel)" I tried installing audit-devel # zypper in audit-devel It now gives me new error: Restoring system sources... Please insert media # 1 and type 'y'... (1 Reply)
Discussion started by: rupeshkp728
1 Replies

7. Infrastructure Monitoring

Nagios check dependent on second nagios server

We have a dual Nagios server setup. One is setup for internal server monitoring on our LAN, while the second Nagios server is hosted externally and is used for external checks only such as URL and ping checks form the WAN side. I was wondering if there is any way to setup cross dependencies... (1 Reply)
Discussion started by: eugenes18t
1 Replies

8. Infrastructure Monitoring

Nagios Availability report for all hosts giving internal error

Hi, I'n new to Nagios, however have installed Nagios Core and monitoring about 19000 switches. They are all grouped into 6 host groups. when i try to pull out a report of a particular hostgroup i get the report but when i try for all hostgroups, i get an error that says: Internal Server Error. ... (1 Reply)
Discussion started by: Nida
1 Replies
COLLECTD-NAGIOS(1)						     collectd							COLLECTD-NAGIOS(1)

NAME
collectd-nagios - Nagios plugin for querying collectd SYNOPSIS
collectd-nagios -s socket -n value_spec -H hostname [options] DESCRIPTION
This small program is the glue between collectd and nagios. collectd collects various performance statistics which it provides via the "unixsock plugin", see collectd-unixsock(5). This program is called by Nagios, connects to the UNIX socket and reads the values from collectd. It then returns OKAY, WARNING or CRITICAL depending on the values and the ranges provided by Nagios. ARGUMENTS AND OPTIONS
The following arguments and options are required and understood by collectd-nagios. The order of the arguments generally doesn't matter, as long as no argument is passed more than once. -s socket Path of the UNIX socket opened by collectd's "unixsock plugin". -n value_spec The value to read from collectd. The argument is in the form "plugin[-instance]/type[-instance]". -H hostname Hostname to query the values for. -d data_source Each value_spec may be made of multiple "data sources". With this option you can select one or more data sources. To select multiple data sources simply specify this option again. If multiple data sources are examined they are handled according to the consolidation function given with the -g option. -g none|average|sum When multiple data sources are selected from a value spec, they can be handled differently depending on this option. The values of the following meaning: none No consolidation if done and the warning and critical regions are applied to each value independently. average The warning and critical ranges are applied to the average of all values. sum The warning and critical ranges are applied to the sum of all values. percentage The warning and critical ranges are applied to the ratio (in percent) of the first value and the sum of all values. A warning is returned if the first value is not defined or if all values sum up to zero. -c range -w range Set the critical (-c) and warning (-w) ranges. These options mostly follow the normal syntax of Nagios plugins. The general format is "min:max". If a value is smaller than min or bigger than max, a warning or critical status is returned, otherwise the status is success. The tilde sign (~) can be used to explicitly specify infinity. If ~ is used as a min value, negative infinity is used. In case of max, it is interpreted as positive infinity. If the first character of the range is the at sign (@), the meaning of the range will be inverted. I. e. all values within the range will yield a warning or critical status, while all values outside the range will result in a success status. min (and the colon) may be omitted, min is then assumed to be zero. If max (but not the trailing colon) is omitted, max is assumed to be positive infinity. -m If this option is given, "Not a Number" (NaN) is treated as critical. By default, the none consolidation reports NaNs as warning. Other consolidations simply ignore NaN values. RETURN VALUE
As usual for Nagios plugins, this program writes a short, one line status message to STDOUT and signals success or failure with it's return value. It exits with a return value of 0 for success, 1 for warning and 2 for critical. If the values are not available or some other error occurred, it returns 3 for unknown. SEE ALSO
collectd(1), collectd.conf(5), collectd-unixsock(5), <http://nagios.org/> AUTHOR
Florian Forster <octo at verplant.org> 5.1.0 2012-04-02 COLLECTD-NAGIOS(1)
All times are GMT -4. The time now is 08:46 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy