Nagios binaries for AIX 7.1

Special Forums UNIX and Linux Applications Infrastructure Monitoring Nagios binaries for AIX 7.1

10-14-2015

Moderator

6,876, 694

Join Date: Sep 2005

Last Activity: 10 February 2021, 3:50 AM EST

Location: Switzerland - GE

Posts: 6,876

Thanks Given: 594

Thanked 694 Times in 627 Posts

thread closed
please follow here:
Nagios for AIX 7.1

vbe

View Public Profile for vbe

Find all posts by vbe

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. AIX

NAGIOS Service not able to open port on AIX 7.1

I have an AIX 7.1 LPAR where Nagios agent was installed for monitoring. The issue is that when I start the nagios service (ncpa_listener), it starts but does not open the 5693 port it requires for communication. On all other LPARs the service opens the port and is listening. I tried reinstalling...

2. AIX

Nagios for AIX 7.1

Hello All, I am new to Nagios. I have a requirement to monitor AIX 7.1 using Nagios xi, could any one guide me steps to go in right direction. I know Nagios doesn't have precompiled agent and plugin for aix 7.1. Appreciate your help

3. AIX

Is nagios monitoring tool supported on AIX 7.1 ?

Hi, is any one using nagios monitoring solution on AIX ? if yes, is it supported on AIX 7.1 TL 03 as well ? I tried to search online and unix.com , could not find it. Thank you

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

5. AIX

Nagios on AIX

I have just been handed a server running aix 61, and an installation of nagios is running on this server. It is monitoring multiple servers in our environment, i assume it is only monitoring aix servers, the admin that did this install has left the company and there isnt any documentation on this...

6. AIX

Installing nmap binaries on AIX

Hi , I am trying to install nmap binaries on AIX 5.3 system. I want it to be installed in the usr/bin directory but it is getting installed in usr/local/bin directory by default, without prompting for installation directory. Is there any way i can install nmap in usr/bin directory ? ...

7. UNIX for Dummies Questions & Answers

Stripping down binaries

Hello, I am the CEO of Grand Tech Corporation. We are launching Linux NT and forgive me, but I do not know how to strip binaries down in Mandriva Linux. Can someone tell me a way to?:b:

8. Infrastructure Monitoring

AIX & Nagios like application.

Hello to all. I am working as a Linux System Administrator since 5 Years & Now,my company is going to purchase 3 numbers of IBM-P Series Server with AIX support. We will install Oracle Database Application on AIX version 5 OS Platform. Now,my questions is: Is it possible to install NAGIOS...

9. Solaris

How to compare binaries

I have the same two source files. They MUST be compiled with -g debugger option. The binaries are different. But in fact the binaries work the same. How to compare them to know the are compiled using the same source code. In Linux it is enough to: strip --strip-all <file> and diff shows no...

10. UNIX for Dummies Questions & Answers

Windows Binaries

This is probably a really stupid question: Why doesnt windows binaries run in *nix? Is it the filesystem? or what? //Maestin

LEARN ABOUT DEBIAN

nagios::plugin::functions

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)

Infrastructure Monitoring