SNMP Problems

[Jamie Baddeley]

Hi Ron,

As discussed, this problem is solved.

jamie

> I get the following error message from Nagios that has me puzzled.
> 
> [12-Jan-2004 18:47:04 ] Retrieved data for disk_4 (): 61
> [12-Jan-2004 18:47:04*] Received SNMP response with error code 
noSuchName.
> OID: 1.3.6.1.2.1.2.2.1.10.16777219
> 
> I do not understand what it is telling me. I can retrieve the data
> manually using snmpget and get the results with no error message. But
> every time Nagios retrieves I get the error message even though as 
you can
> see from above it actually retrieves the data (61) Can anyone please 
throw
> some light on this error?
> 
> Thanks
> --
>  
> Ron Wilson
> City of Sails
> Auckland
> 
> Let thy speech be short, comprehending much in a few words.
> Aprocrypha
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: Perforce Software.
> Perforce is the Fast Software Configuration Management System offering
> advanced branching capabilities and atomic changes on 50+ platforms.
> Free Eval! http://www.perforce.com/perforce/loadprog.html
> _______________________________________________
> 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
> 
> 




-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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