MySQL-plugin : how to use it ??

[James Pratt]

>> -----Original Message-----
>> From: jonas kellens [mailto:jonas.kellens at telenet.be]
>> Sent: Saturday, October 31, 2009 11:01 AM
>> To: Nagios-Users
>> Subject: [Nagios-users] MySQL-plugin : how to use it ??
>> 
>> I have found the following Nagios plugin to monitor MySQL :
>> 
>> bash-3.2# wget http://oss.isg.inf.ethz.ch/nagiosplug/download/MySQL-1.3.tgz
>> 
>> bash-3.2# ls
>> AUTHORS   ChangeLog check_mysql.pl check_mysql_slow.pl COPYING  VERSION
>> build.sh  check_mysql_bytes.pl check_mysql_queries.pl check_mysql_threads.pl
>> TODO
>> 
>> bash-3.2# sh build.sh
>> build.sh: line 22: rpmbuildenv: command not found
>> error: failed to stat /usr/src/MySQL-1.3/MySQL.spec: No such file or directory
>> error: failed to stat /usr/src/MySQL-1.3/MySQL.spec: No such file or directory
>> 
>> Now, how can I use these check-commands ??
>> 
>> Greetings,
>> Jonas.

It appears as though build.sh is trying to build you an RPM file from the source, which is a RedHat package type - you will need the rpm , and other rpm-build utilities in order to get this to compile by using that build script.

>From the looks of it above, you may be able to just copy the *.pl files over to /usr/local/nagios/libexec (or wherever your plugin folder lives), and try to use them in your commands.cfg - unless of course there is something specific placed into them from the build.sh script.


Regards,
Jamie
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
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