Problems Importing Nagios Comments.dat

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Infrastructure Monitoring Problems Importing Nagios Comments.dat
# 1  
Old 01-22-2011
Problems Importing Nagios Comments.dat

So i upgraded from Nagios version 2.6 to the latest version of nagios currently available.

but the problem is, i can't get the comments that were on my old version of nagios to show up on my new version of nagios.

has anyone else run into this issue?

the comments are extremely important.

thank you
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to use 'ls' command to list files like *.dat, not *.*.dat?

How to use 'ls' command to list files like *.dat, not *.*.dat (5 Replies)
Discussion started by: pmcginni777
5 Replies

2. 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

3. Shell Programming and Scripting

importing variables from 1 file to another

hi i want to retrieve talespace, datafile's path , size and another size in following querry in shell Create Tablespace 'A' Datafile 'Some Path' Size '10G' extent management Local uniform size '64M'; from another file say 'A.txt' where i ll dumb data in sequence separated by commas... (2 Replies)
Discussion started by: Gl@)!aTor
2 Replies

4. Shell Programming and Scripting

Importing Autosys Calendar.

Hi All, I'm try to import a Calendar in Autosys using below command, autocal_asc -I TKY_Test Utility to Add/Delete or Print entries in Calendar. Calendar Name: But it not allowing me to import the calendar, it asks for the calendar which is similair if we try to manually add calender... (1 Reply)
Discussion started by: arvindcgi
1 Replies

5. Shell Programming and Scripting

Sed script, changing all C-comments to C++-comments

I must write a script to change all C++ like comments: // this is a comment to this one /* this is a comment */ How to do it by sed? With file: #include <cstdio> using namespace std; //one // two int main() { printf("Example"); // three }//four the result should be: (2 Replies)
Discussion started by: black_hawk
2 Replies

6. Infrastructure Monitoring

problems with Net-snmp to use with Nagios Check_hpjd

In order to get the Check_hpjd plugin for nagios to work, i have to get net-snmp (+utils) installed. If i look in the yast Control center, iwe installed everything that should have something to do with snmp. This is my first time with linux, so im abit of a noob. how do i get the plugin... (0 Replies)
Discussion started by: Nikos
0 Replies

7. HP-UX

Problems restoring Ignite make_recovery DAT backups

Can anyone help with an HP Ignite problem please !! We currently have 2 servers running HP-UX B.11.00 connected together and using a high availability cluster (serviceguard) running one package. Each of the servers have 2 mirrored local disks. (also installed HP OpenviewDM B.05.03, Oracle 8.0.5,... (7 Replies)
Discussion started by: clivethegadget
7 Replies

8. Shell Programming and Scripting

Importing dump file

Hi, I am trying to import 22 .dmp files but facing the problem with the last table file it never ends the import command, only the table is created but the rows of the table don't get imported. This is the problem with only ine table rest 21 tables are being imported properly. Thanks in... (2 Replies)
Discussion started by: anushilrai
2 Replies

9. Linux

HP DAT Drive C1533A on RH9 Problems

HELP!! I am having some major problems at present with a HP dat drive under RH9. The drive worked fine previously under RH8, but now does not work. I am using kernel 2.4.20-30.9 on a i686 athlon intel box. My messages log shows the below: Apr 23 11:39:24 devsys kernel: ahc_pci:1:6:0:... (0 Replies)
Discussion started by: dkimber6
0 Replies
Login or Register to Ask a Question
Nagios::Plugin::Functions(3pm)				User Contributed Perl Documentation			    Nagios::Plugin::Functions(3pm)

NAME
Nagios::Plugin::Functions - functions to simplify the creation of Nagios plugins SYNOPSIS
# Constants OK, WARNING, CRITICAL, and UNKNOWN exported by default use Nagios::Plugin::Functions; # nagios_exit( CODE, $message ) - exit with error code CODE, # and message "PLUGIN CODE - $message" nagios_exit( CRITICAL, $critical_error ) if $critical_error; nagios_exit( WARNING, $warning_error ) if $warning_error; nagios_exit( OK, $result ); # nagios_die( $message, [$CODE] ) - just like nagios_exit(), # but CODE is optional, defaulting to UNKNOWN do_something() or nagios_die("do_something() failed horribly"); do_something_critical() or nagios_die("do_something_critical() failed", CRITICAL); # check_messages - check a set of message arrays, returning a # CODE and/or a result message $code = check_messages(critical => @crit, warning => @warn); ($code, $message) = check_messages( critical => @crit, warning => @warn, ok => @ok ); # get_shortname - return the default short name for this plugin # (as used by nagios_exit/die; not exported by default) $shortname = get_shortname(); DESCRIPTION
This module is part of the Nagios::Plugin family, a set of modules for simplifying the creation of Nagios plugins. This module exports convenience functions for the class methods provided by Nagios::Plugin. It is intended for those who prefer a simpler functional interface, and who do not need the additional functionality of Nagios::Plugin. EXPORTS Nagios status code constants are exported by default: OK WARNING CRITICAL UNKNOWN DEPENDENT as are the following functions: nagios_exit nagios_die check_messages The following variables and functions are exported only on request: %ERRORS %STATUS_TEXT get_shortname max_state max_state_alt FUNCTIONS The following functions are supported: nagios_exit( <CODE>, $message ) Exit with return code CODE, and a standard nagios message of the form "PLUGIN CODE - $message". nagios_die( $message, [CODE] ) Same as nagios_exit(), except that CODE is optional, defaulting to UNKNOWN. NOTE: exceptions are not raised by default to calling code. Set $_use_die flag if this functionality is required (see test code). check_messages( critical => @crit, warning => @warn ) Convenience function to check a set of message arrays and return an appropriate nagios return code and/or a result message. Returns only a return code in scalar context; returns a return code and an error message in list context i.e. # Scalar context $code = check_messages(critical => @crit, warning => @warn); # List context ($code, $msg) = check_messages(critical => @crit, warning => @warn); check_messages() accepts the following named arguments: critical => ARRAYREF An arrayref of critical error messages - check_messages() returns CRITICAL if this arrayref is non-empty. Mandatory. warning => ARRAYREF An arrayref of warning error messages - check_messages() returns WARNING if this arrayref is non-empty ('critical' is checked first). Mandatory. ok => ARRAYREF | SCALAR An arrayref of informational messages (or a single scalar message), used in list context if both the 'critical' and 'warning' arrayrefs are empty. Optional. join => SCALAR A string used to join the relevant array to generate the message string returned in list context i.e. if the 'critical' array @crit is non-empty, check_messages would return: join( $join, @crit ) as the result message. Optional; default: ' ' (space). join_all => SCALAR By default, only one set of messages are joined and returned in the result message i.e. if the result is CRITICAL, only the 'critical' messages are included in the result; if WARNING, only the 'warning' messages are included; if OK, the 'ok' messages are included (if supplied) i.e. the default is to return an 'errors-only' type message. If join_all is supplied, however, it will be used as a string to join the resultant critical, warning, and ok messages together i.e. all messages are joined and returned. get_shortname Return the default shortname used for this plugin i.e. the first token reported by nagios_exit/nagios_die. The default is basically uc basename( $ENV{NAGIOS_PLUGIN} || $0 ) with any leading 'CHECK_' and trailing file suffixes removed. get_shortname is not exported by default, so must be explicitly imported. max_state(@a) Returns the worst state in the array. Order is: CRITICAL, WARNING, OK, UNKNOWN, DEPENDENT The typical usage of max_state is to initialise the state as UNKNOWN and use it on the result of various test. If no test were performed successfully the state will still be UNKNOWN. max_state_alt(@a) Returns the worst state in the array. Order is: CRITICAL, WARNING, UNKNOWN, DEPENDENT, OK This is a true definition of a max state (OK last) and should be used if the internal tests performed can return UNKNOWN. SEE ALSO
Nagios::Plugin; the nagios plugin developer guidelines at http://nagiosplug.sourceforge.net/developer-guidelines.html. AUTHORS
This code is maintained by the Nagios Plugin Development Team: http://nagiosplug.sourceforge.net COPYRIGHT AND LICENSE
Copyright (C) 2006 by Nagios Plugin Development Team This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2011-12-23 Nagios::Plugin::Functions(3pm)