On Mon, 07 Aug 2006 13:16:39 -0400, Eric Newton <[EMAIL PROTECTED]> wrote:
> Wow.  Something is definitely wrong here.  Can you try a single device?
> 
>     $ zenperfsnmp run -v 10 -d name-of-zenoss-device
> 
> Somehow the config is not getting loaded properly.  Can you add this
> line at or around line 287:
> 
>     oid = '.'+oid.lstrip('.')                         # <-- existing line
>     self.log.debug("Oid is '%r'" % oid)   # <-- new line

I figured it out by adding this line.  My boss had copied and pasted an OID but 
had whitespace in front of it (namely a tab character).

DEBUG:zen.zenperfsnmp:Oid is ''.  \t1.3.6.1.2.1.1.3.0''

Might want to do some checking for that before inserting into the database.

Thanks!

--Dennis

> 
> And then send the results?
> 
> -Eric
> 
> Dennis B.Hopp wrote:
>> On Mon, 07 Aug 2006 12:23:44 -0400, Eric Newton <[EMAIL PROTECTED]>
> wrote:
>>
>>> Try running zenperfsnmp with debug:
>>>
>>>     zenperfsnmp run -v 10 --cycle
>>>
>>
>> Here is some of the output from this.
>>
>> Unhandled error in Deferred:
>> Traceback (most recent call last):
>>   File "/opt/zenoss/Products/ZenUtils/Chain.py", line 45, in success
>>     self.next()
>>   File "/opt/zenoss/Products/ZenUtils/Chain.py", line 40, in next
>>     self.defer.callback(self.results)
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 229, in
> callback
>>     self._startRunCallbacks(result)
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 294, in
> _startRunCallbacks
>>     self._runCallbacks()
>> --- <exception caught here> ---
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 307, in
> _runCallbacks
>>     self.result = callback(self.result, *args, **kw)
>>   File "/opt/zenoss/Products/ZenRRD/zenperfsnmp.py", line 405, in
> storeValues
>>     self.storeRRD(deviceName, oid, value)
>>   File "/opt/zenoss/Products/ZenRRD/zenperfsnmp.py", line 431, in
> storeRRD
>>     oidData = self.proxies[device].oidMap[oid]
>> exceptions.KeyError: '.1.3.6.1.2.1.1.3.0'
>> Unhandled error in Deferred:
>> Traceback (most recent call last):
>>   File "/opt/zenoss/Products/ZenUtils/Chain.py", line 45, in success
>>     self.next()
>>   File "/opt/zenoss/Products/ZenUtils/Chain.py", line 40, in next
>>     self.defer.callback(self.results)
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 229, in
> callback
>>     self._startRunCallbacks(result)
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 294, in
> _startRunCallbacks
>>     self._runCallbacks()
>> --- <exception caught here> ---
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 307, in
> _runCallbacks
>>     self.result = callback(self.result, *args, **kw)
>>   File "/opt/zenoss/Products/ZenRRD/zenperfsnmp.py", line 405, in
> storeValues
>>     self.storeRRD(deviceName, oid, value)
>>   File "/opt/zenoss/Products/ZenRRD/zenperfsnmp.py", line 431, in
> storeRRD
>>     oidData = self.proxies[device].oidMap[oid]
>> exceptions.KeyError: '.1.3.6.1.2.1.1.3.0'
>>
>> Unhandled error in Deferred:
>> Traceback (most recent call last):
>>   File "/opt/zenoss/Products/ZenUtils/Chain.py", line 45, in success
>>     self.next()
>>   File "/opt/zenoss/Products/ZenUtils/Chain.py", line 40, in next
>>     self.defer.callback(self.results)
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 229, in
> callback
>>     self._startRunCallbacks(result)
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 294, in
> _startRunCallbacks
>>     self._runCallbacks()
>> --- <exception caught here> ---
>>   File "/opt/zenoss/lib/python/twisted/internet/defer.py", line 307, in
> _runCallbacks
>>     self.result = callback(self.result, *args, **kw)
>>   File "/opt/zenoss/Products/ZenRRD/zenperfsnmp.py", line 414, in
> storeValues
>>     self.startReadDevice(self.queryWorkList.pop())
>>   File "/opt/zenoss/Products/ZenRRD/zenperfsnmp.py", line 356, in
> startReadDevice
>>     d = chain.run()
>>   File "/opt/zenoss/Products/ZenUtils/Chain.py", line 31, in run
>>     self.next()
>>   File "/opt/zenoss/Products/ZenUtils/Chain.py", line 38, in next
>>     self.callable(next).addCallbacks(self.success, self.failure)
>>   File "/opt/zenoss/Products/ZenRRD/zenperfsnmp.py", line 354, in
> getLater
>>     return proxy.get(oids, proxy.timeout, proxy.tries)
>>   File "/opt/zenoss/lib/python/twistedsnmp/v3/agentproxy.py", line 82,
> in get
>>     self.send(request.encode())
>>   File "/opt/zenoss/lib/python/pysnmp/asn1/encoding/ber/base.py", line
> 254, in berEncode
>>     result = result + self[key].encode()
>>   File "/opt/zenoss/lib/python/pysnmp/asn1/encoding/ber/base.py", line
> 254, in berEncode
>>     result = result + self[key].encode()
>>   File "/opt/zenoss/lib/python/pysnmp/asn1/encoding/ber/base.py", line
> 254, in berEncode
>>     result = result + self[key].encode()
>>   File "/opt/zenoss/lib/python/pysnmp/asn1/encoding/ber/base.py", line
> 370, in berEncode
>>     result = result + value.berEncode()
>>   File "/opt/zenoss/lib/python/pysnmp/asn1/encoding/ber/base.py", line
> 254, in berEncode
>>     result = result + self[key].encode()
>>   File "/opt/zenoss/lib/python/pysnmp/asn1/encoding/ber/base.py", line
> 171, in berEncode
>>     value = self._berEncode(value)
>>   File "/opt/zenoss/lib/python/pysnmp/asn1/encoding/ber/univ.py", line
> 143, in _berEncode
>>     raise error.BadArgumentError('Short Object ID for %s' % \
>> pysnmp.asn1.encoding.ber.error.BadArgumentError: Short Object ID for
> ObjectName
>>
>>
>>> For even more debug, at the beginning of zenperfsnmp.py, line 370, add
> a
>>> line of debug:
>>>
>>>         'decode responses from devices and store the elements in RRD
>>> files'
>>>         # even more debugging
>>>         self.log.debug('storeValues %s %s', updates, deviceName)
>>>         proxy = self.proxies.get(deviceName, None)
>>>
>>> You can also run zenperfsnmp on a single device:
>>>
>>>     zenperfsnmp run -v 10 -d troublesome-device
>>>
>>> Finally, if you really want to find out what is going on, strace the
>>> process for network events:
>>>
>>>     strace -e trace=network zenperfsnmp run -v 10 -d troublesome-device
>>>
>>> I would be happy to pour through any of this if you want to send it on.
>>>
>>> -Eric
>>>
>>> Dennis B.Hopp wrote:
>>>
>>>> Is there any way I can determine what is causing this?  I'm still
>>>>
>>> getting these messages and I have completely removed the AIX boxes from
>>> monitoring.
>>>
>>>> --Dennis
>>>>
>>>> On Fri, 04 Aug 2006 15:15:32 -0400, Eric Newton <[EMAIL PROTECTED]>
>>>>
>>> wrote:
>>>
>>>>> It could if the oid list is long and some of the responses timeout
>>>>> because the device does not respond.
>>>>>
>>>>> -Eric
>>>>>
>>>>> Dennis B.Hopp wrote:
>>>>>
>>>>>
>>>>>> On Fri, 04 Aug 2006 14:58:14 -0400, Eric Newton <[EMAIL PROTECTED]>
>>>>>>
>>>>>>
>>>>> wrote:
>>>>>
>>>>>
>>>>>>> Hi Dennis,
>>>>>>>
>>>>>>> This message means "not all of the devices have responded for two
>>>>>>> cycles: I'm going to start over with all the devices".   We
> regularly
>>>>>>> monitor 500 devices in a minute, so something is probably wrong. 
> One
>>>>>>> possibility is that your devices are down and they have not yet
> been
>>>>>>> removed from the list of devices to be monitored by zenping.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>> None of my devices are down, but I am trying to add some AIX boxes
> and
>>>>>>
>>> I
>>>
>>>>> can't seem to get the OIDs right and so it's complaining about bad
> OIDs
>>>>>
>>> in
>>>
>>>>> the Events, could this cause that?
>>>>>
>>>>>
>>>>>> --Dennis
>>>>>>
>>>>>>
> 
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users

_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to