check_megaraid fails in Nagios 2.0 on Debian 3.1

[Gary Danko]

I got the plugin here:
http://www.ibiblio.org/john/megaraid/

Nagios was installed via apt-get. I guess I could recompile it from
source though I'd like to not do that since I have a number of Nagios
servers in use.

I did try adding the line "$my runtimedir;" before the first use of
the variable but the error persisted. I will try some other things.
Any other suggestons are welcome. :-)

On 5/22/06, Marc Powell <marc at ena.com> wrote:
>
>
> > -----Original Message-----
> > From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> > admin at lists.sourceforge.net] On Behalf Of Gary Danko
> > Sent: Monday, May 22, 2006 12:28 PM
> > To: Nagios-users at lists.sourceforge.net
> > Subject: [Nagios-users] check_megaraid fails in Nagios 2.0 on Debian
> 3.1
> >
> > We have two Nagios 1.3 servers that sit on Debian 3.1 machines. The
> > check_megaraid version we use is 0.8.2. I am trying to migrate to
> > Nagios 2.0, but the check_megaraid plugin fails in Nagios 2.0.
> >
> > root at discostu:/etc/nagios2# /usr/local/nagios/plugins/check_megaraid
> > -H mail-incoming -C xxxxxx
> > megaraid OK
>
> Always perform your tests as the nagios user. The nagios user won't have
> the same access rights as the root user so tests that work as root may
> not work for the nagios user. It wouldn't have mattered in this
> particular case but it's good practice.
>
> >
> > But in the Nagios web console on the same server I receive this error:
> >
> > **ePN 'check_megaraid' Global symbol "$runtimedir" requires explicit
> > package name at (eval 6) line 51.
> >
> > Has anyone here successfully run the check_megaraid plugin on Nagios
> 2.0?
>
> I don't use it but have some suggestions. Since this is a non-standard
> plugin you should provide pointers to download the specific version you
> are using when asking for help. There are a couple of check_megaraid
> plugins that I've found but none use the variable $runtimedir.
>
> It would appear that this plugin is not written to be compatible with
> the Nagios embedded Perl interpreter. I would hazard a guess that your
> 1.3 installations were compiled without the ePN but your nagios-2
> installation was. This should have been a problem for 1.3 as well since
> the plugin requirements are the same. You can either --
>
> 1) recompile your nagios-2 installations without the ePN.
> 2) modify the plugin to be compatible with the ePN
>         - This may be as simple as adding 'my $runtimedir;' somewhere
> before the first use of that variable.
>         - other guidelines to make perl plugins compatible with the ePN
> are available here --
> http://nagiosplug.sourceforge.net/developer-guidelines.html#PERLPLUGIN
>
> --
> Marc
>
>
> -------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmdlnk&kid0709&bid&3057&dat1642
> _______________________________________________
> 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
>


-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
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