We don't do rsvp!
Adam.
Sent with AquaMail for Android http://www.aqua-mail.com
On 10 September 2014 16:07:15 Zhenhui Liang ZhenhuiLiang@eharmony.com wrote:
The bug I was referring specifically is that a specific vender¹s specific code version has: snmpwalk on RSVP mib when RSVP is not configured causing memory leak.
So I am wondering, since my device does not have rsvp configured, where is that snmpwalk coming from? My guess is discover.php? For existing devices already on observium, what exactly is discover.php doing? Trying to discover new installed module, new routing instances etc? Is there a way to prevent it from discovering rsvp mibs? Thanks!
‹Zhenhui
On 9/10/14, 2:03 AM, "Tom Laermans" tom.laermans@powersource.cx wrote:
On 09/09/2014 23:55, Adam Armstrong wrote:
At the moment we don't have the capability of disabling individual MIBs, so you have to enable an entire module.
True, well, apart from the part where we can disable entire MIBs for a specific device of course ;-)
But this is work in progress and only works for some of the mibs in some of the cases. Most notably all modules where we the the include-dir-mib system: you can disable those as mentioned earlier in the thread via the device settings. There is a lot of code that just polls/discovers without checking if it's disabled though, so we're not quite there yet.
I agree it's most likely more useful to disable a module than an entire MIB... (apart from things like LM-SENSORS-MIB, those you should just disable ;))
Tom
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium