On Fri, 16 Mar 2012 09:33:58 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
After upgrading to 3.11.0 this has magically corrected itself, but for one box.
In 'sensor' I find two rows with oid=.1.3.6.1.4.1.9.9.13.1.5.1.3.[12]. So I guess if I just remove these everything will be OK?
Ok, that was strange. Since you don't have an SNMP community set for the UPS, its pre-existing list of sensors should never be edited by NAV (since the SNMP collector doesn't run for that UPS any more).
But yes, deleting the sensor entries related to the UPS' netboxid should do the trick. I'll whip up a patch to _not_ generate cricket-config for sensors for devices without a community.
I guess the SNMP community has once been set. And I would like to set it again, but when I edit the device I get
TypeMismatchError at /seeddb/netbox/edit/1853/
Octet-stream parse error at Pdus
Request Method: POST Request URL: https://nav.uit.no/seeddb/netbox/edit/1853/ Django Version: 1.3.1 Exception Type: TypeMismatchError Exception Value:
Octet-stream parse error at Pdus
Exception Location: /usr/local/lib/python2.7/site-packages/pysnmp/asn1/encodin g/ber/base.py in berDecode, line 370 Python Executable: /usr/local/bin/python Python Version: 2.7.2
If I use a wrong community I get this error after "Continue" on the first page of /seeddb/netbox/edit/1853/. If I use the correct community I do not get the error until I press "Save" on the second page.
Another device with a wonky SNMP implementation? Do you have a full traceback from the error? If so, please file a bug report: https://bugs.launchpad.net/nav/+filebug
As a fix for now I will set the community directly into the database.
Ok. No problems with the device in ipdevpoll.log then?