APC UPS Monitoring Setup.

[David A.]

Thank you, James.

Turns out I had two problems.

I edited my command definition in the commands.cfg file to match yours (I
actually had that at one point, but changed it when I could not the plugin
to work!)

I then used the switch.cfg sample file to set up the host, group and service
definitions.

And that is when I discovered my second problem.  After editing the
nagios.cfg file to include a pointer to my ups monitoring config file I ran
the verification command (/usr/local/nagios/bin/nagios -v
/usr/local/nagios/etc/nagios.cfg) and got the same darned WARNING (null
value on line 48) message I have been getting all weekend!  I don't know
what made me do it this time, but I decided to check the nagios.cfg file for
errors.  I had an error in my pointer line -- used a "-" isntead of an "=".
$%&@#$*!

Sigh.  All is well now.

Thanks again.  And I ran out this morning and picked up Wolfgang Barth's
book on Nagios to assist me with the rest of my configurations.



On Sun, Apr 12, 2009 at 10:26 PM, <jmoseley at corp.xanadoo.com> wrote:

> Remember to CC the nagios users' list...  From looking at the script, it
> doesn't look like there are any options for setting critical/warning
> thresholds for temperature, load, etc.  It appears they are all predefined.
>
> In that case, the command configuration would look something like:
>
> define command {
>  command_name check_apcups
>  command_line $USER1$/check_snmp_apcups -H $HOSTADDRESS$ -C $ARG1$
> }
>
> The service check configuration would look like:
>
> define service{         use
> generic-service         host_name                      apc-smart-ups
> service_description     APC_STATUS         check_command
> check_apcups!public
>         }
>
> Obviously, you would replace 'public' above with whatever SNMP community
> string you have setup...
>
> The host group and host defintions you supplied earlier should be fine.
> Remember, this script is fairly elementary in that it appears it
> predetermines all the critical/warning levels for things like temp, battery
> capacity, input/output voltage, etc.  So, there's nothing else you need to
> do.  It will either return an 'OK' value or generate a critical or warning
> alert with the simple configuration above.  Obviously, you could edit the
> script to change any of the thresholds by hardcoding them into the script,
> or you could modify it to accept warning/critical threshold limits as
> variables.
>
>
>
> James Moseley
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090413/64e2302f/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null