Well, if I use the default snmpd.conf, I can connect to the host using snmpwalk locally and from the nagios host, but I can't see anything related to the perc array. It is this configuration that causes the perl substr error when I run check_sasraid_megaraid.
Renaming percsnmpd.conf -> snmpd.conf, I can't connect to the host at all either using snmpwalk or the script. Both conf files have a line "pass .1.3.6.1.4.1.3582 /usr/sbin/percmain" as the last line of the file, but I don't understand enough about snmp (reading the docs is giving me a headache! :) to be able to connect the dots. Would you share relevant snmpd.conf info for me, James? Much thanks for your patience and advice. Bo Bo Gusman wrote: > Progress, of sorts. > > I installed nagios on another CentOS box to ensure that you and I are > working from the same essential config. Had exactly the same perl errors > as before. Doing some debugging of the script, it occurred to me that > the first error > > substr outside of string at ./check_sasraid_megaraid.pl line 461. > > was a great big clue perhaps the script wasn't getting anything back from the > percsnmp daemon on the monitored box. > > Since I was running snmpd using the default snmpd.conf, I figured that since > I'm only going to use the percsnmpd, why not symlink percsnmpd.conf to > snmpd.conf and try again. This got me much further, though still with errors: > > snmp error: No response from remote host 'bullwinkle' > Megaraid UNKNON - could not retrieve snmp table blah blah > > OK, so I'm guessing that something is broken in my snmp config. Guess it's > time to try to figure that out. RTFM, as they say! > > Bo > > > > jmose...@corp.xanadoo.com wrote: > >> Doesn't matter if you're not using the plugin within Nagios yet. What >> matters is if you have all the perl utilities installed. >> >> If you haven't already, install the following: >> >> yum install nagios-plugins >> >> Then rerun the script. I have a CentOS 5.2 box with Perl, Nagios, and >> Nagios-plugins installed via yum and I don't have the problems you do >> running the script. >> >> >> James Moseley >> >> >> >> Bo Gusman <ml...@bogusville.us> wrote: >> >> 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. >> >> >> >> >> >> > > > ------------------------------------------------------------------------------ > 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@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 > ------------------------------------------------------------------------------ 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@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