experience with check_sasraid_megaraid for Dell PERC 4?

[Bo Gusman]

Host OS is CentOS 5.x (originally 5.2 with ongoing updates applied via 
yum.)  Perl is default install v 5.8.8. On the Nagios box (actually a 
VM) I'm using Groundwork Community Edition 5.3 VM as provided by 
groundwork. I've not actually connected the plugin to anything Nagios 
yet, I'm just running it from the command line.

I did have to install Net::SNMP for perl from CPAN.

Hmmm, what a puzzle.

    Bo

jmoseley at corp.xanadoo.com wrote:
> My guess is you have an old version of perl or missing something else...
>
> How did you install perl and Nagios/Nagios plugins?  I just tested this
> plugin on a CentOS 5.3 box which had perl and nagios-plugins installed via
> yum repository.  Worked just fine.
>
> I'd install nagios-plugins from yum and see if that clears things up.  If
> it doesn't you might want to check which version of perl you are running
> and upgrade it.
>
>
> James Moseley
>
>
>
>
> Bo Gusman <mlist at bogusville.us>  wrote:
>
>
> That said
>
>              ./check_sasraid_megaraid.pl -H bullwinkle -C public -T
> megaraid -s 2c
>
> all hell breaks loose:
>
>
>     substr outside of string at ./check_sasraid_megaraid.pl line 461.
>     Use of uninitialized value in split at ./check_sasraid_megaraid.pl
> line 462.
> <snip>
>
>
>
>   


------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
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