[Nagiosplug-devel] [ nagiosplug-Bugs-1032009 ] check_ups incompatible with nut 2.0

[SourceForge.net]

Bugs item #1032009, was opened at 2004-09-21 09:12
Message generated for change (Comment added) made by mattkent
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1032009&group_id=29880

Category: None
Group: None
>Status: Closed
Resolution: Out of Date
Priority: 5
Submitted By: Alain RICHARD (arichard)
Assigned to: Matthew Kent (mattkent)
Summary: check_ups incompatible with nut 2.0

Initial Comment:
Hi,

nut is now at 2.0 level and have changed completly the 
communication protocol used to monitoring the ups state and 
values (nut 2.0 is included in various recent distributions like 
fedora). 

This breaks completly the check_ups plugin.

I have reworked it and you'll find it joined to this report.

As the old plugin works with nut-0.x and nut-1.x, I propose to add 
this as a new check_upsv2 plugin.

I am currently using it and it is stable.

Regards,


----------------------------------------------------------------------

>Comment By: Matthew Kent (mattkent)
Date: 2004-12-06 18:45

Message:
Logged In: YES 
user_id=983566

Updated plugin has had initial testing.

----------------------------------------------------------------------

Comment By: Matthew Kent (mattkent)
Date: 2004-12-01 20:43

Message:
Logged In: YES 
user_id=983566

Superceeded by #1038413 a large patch which brings support
to NUT 2.0. Would appreciate any testing of check_ups from a
recent nightly snapshot/cvs build to make sure it still
meets your needs. 

----------------------------------------------------------------------

Comment By: Pat Hennessy (pathennessy)
Date: 2004-10-18 17:43

Message:
Logged In: YES 
user_id=1140303

Well, thats real useful.  I kinda wish I saw all this
before, but I must have missed these bugs while looking. 
Hopefully, this will all be working into the next release of
the nagios plugins.

Using upsc hasn't been a big deal to us because we install
NUT on all the servers.  Since we are using it to monitor
and handle clean shutdowns.  I wasn't aware in the
compatibility issue and will keep that in mind to switch
versions on everything at once.  Actually, I will probably
install a patched version of the check_ups program instead.
 I'd rather use that then a script.

I also played with the NUT perl module, but that only works
with <=1.4 versions of NUT.  It was not real pretty, maybe
something better came along.  I was kinda tempted to fix it
to work with the newer protocol, but parsing the output of
upsc was quicker and easier.


----------------------------------------------------------------------

Comment By: arnaud quette (uzuul)
Date: 2004-10-18 07:47

Message:
Logged In: YES 
user_id=135177

I've made a patch that include Richard's enhancements plus 
some of mine. Check 
http://sourceforge.net/tracker/index.php?
func=detail&aid=1038413&group_id=29880&atid=397599

Note that we _can't_ rely on upsc as it implies having NUT 
installed. We (NUT developers) have made an easy and Ascii 
protocol so that implementation is fairly straightforward, as in 
check_ups. Moreover, only upsc from nut 1.4 supports both 
the old and the new protocol, so if you have NUT 2.0 installed 
locally, and want to talk to a <= 1.4 NUT server, it won't 
work!

If having both old and new protocol compat is needed, please 
tell us so.

Arnaud
---
2nd NUT coordinator/developer
Debian Developer

----------------------------------------------------------------------

Comment By: Pat Hennessy (pathennessy)
Date: 2004-10-15 19:44

Message:
Logged In: YES 
user_id=1140303

I also ran into this and found this bug after the fact.  I
wrote a perl script to use the upsc command instead.  The
upsc command works with both versions.  Since the upsc
command comes with the nut client, it should always work
with the server.  Using this perl script, I am able to
update my nut servers one at time without the need to fiddle
with my Nagios config or plugins.

I was going to submit the script to the contrib section of
the CVS tree, but I haven't quite figured out how to do that
yet.  If someone wants it, I will be happy to email the
script to them until I submit it (if its even accepted).


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1032009&group_id=29880