Opened 13 years ago

Closed 11 years ago

Last modified 9 years ago

#75 closed defect (fixed)

MRTG doesn't handle additional mibs when not using SMNPv3

Reported by: human Owned by: somebody
Version: 2.x Keywords:
Cc: Martín, Ferrari, <martin.ferrari@…>

Description

Hello, I'm forwarding the Debian bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404168 :

""" Version: 2.14.7-2

In a fresh install of mrtg, I noticed that I cannot use external MIBs. After a couple of hours trying to understand I found that /usr/bin/mrtg was loading SNMP_util, as snmpv3 was not required, but /usr/share/perl5/MRTG_lib.pm was loading Net_SNMP_util, as it always tries that library first. As a result, when the config file was read by MRTG_lib, the mibs were pushed into @Net_SNMP_util::MIB_Files, but then, when calling toOID from /usr/bin/mrtg, it tries to read mibs from @SNMP_util::MIB_Files, so that doesn't work.

Just putting "enablesnmpv3: yes" fixed the issue.

I don't understand how this works in other computers I have... """

Change History (2)

Note: See TracTickets for help on using tickets.
 

NOTE: The content of this website is accessible with any browser. The graphical design though relies completely on CSS2 styles. If you see this text, this means that your browser does not support CSS2. Consider upgrading to a standard conformant browser like Mozilla Firefox or Opera but also Apple's Safari or KDE's Konqueror for example.