[prev in list] [next in list] [prev in thread] [next in thread] 

List:       nagios-users
Subject:    Re: [Nagios-users] MySQL-plugin : how to use it ??
From:       Giorgio Zarrelli <zarrelli () linux ! it>
Date:       2009-10-31 15:44:36
Message-ID: 1257003876.3987.2.camel () SALOTTO
[Download RAW message or body]

Hi,

look, the easy way is to put the file utils.pm in the libexec
directory. 
The correct way would be to put utils.pm in the path required by perl.

But do the first and it should work.



Giorgio

Il giorno sab, 31/10/2009 alle 16.37 +0100, jonas kellens ha scritto:
> This is the output when placing the perl-files
> in /usr/local/nagios/libexec/ :
> 
> bash-3.2# /usr/local/nagios/libexec/check_mysql_threads --help
> bash: /usr/local/nagios/libexec/check_mysql_threads: No such file or
> directory
> 
> bash-3.2# /usr/local/nagios/libexec/check_mysql_threads.pl 
> Can't locate utils.pm in @INC (@INC contains:
> nagios/plugins /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi \
> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl \
> /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi \
> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl \
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at \
> /usr/local/nagios/libexec/check_mysql_threads.pl line 26. BEGIN failed--compilation \
> aborted at /usr/local/nagios/libexec/check_mysql_threads.pl line 26.
> 
> bash-3.2# perl /usr/local/nagios/libexec/check_mysql_threads.pl 
> Can't locate utils.pm in @INC (@INC contains:
> nagios/plugins /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi \
> /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl \
> /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi \
> /usr/lib/perl5/vendor_perl/5.8.8 /usr/lib/perl5/vendor_perl \
> /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi /usr/lib/perl5/5.8.8 .) at \
> /usr/local/nagios/libexec/check_mysql_threads.pl line 26. BEGIN failed--compilation \
> aborted at /usr/local/nagios/libexec/check_mysql_threads.pl line 26.
> 
> Jonas.
> 
> On Sat, 2009-10-31 at 11:14 -0400, James Pratt wrote: 
> > 
> > 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@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



------------------------------------------------------------------------------
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@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


[prev in list] [next in list] [prev in thread] [next in thread]