On Mon, 19 Mar 2012 11:01:28 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
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.
That would be sensible.
The patch will be in 3.11.1.
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
Will do.
Thanks!
As a fix for now I will set the community directly into the database.
Ok. No problems with the device in ipdevpoll.log then?
Well, we get a lot of [WARNING twsnmp.protocol] Bad response from ('129.242.35.52', 161): '0&\x02\x01\x01\x04\x06<SNMPCOMMUNITY>\xa2\x1e\x02\x03#S\xb1\x02\x01\x05\x02\x0 1\x000\x0c0\n\x06\x06+\x06\x01\x02\x01\x01\x05\x00' but we also get these from other devices which do not crash the webinterface.
For this error I would prescribe: Try to get rid of twistedsnmp and use pynetsnmp instead, if you can. I do trust NetSNMP a whole lot more than twistedsnmp.