Hi,

This is now fixed in SVN.

To update and replace your modifications, delete your mibs directory and run "svn up". It'll re-download the MIBs and make sure they're correct.

You should really update more often :)

adam.

On 2014-08-19 01:38, Nathan Phelan wrote:

Hi Guys,

Short version: Fortinet memory stops showing in Observium after updating due to Fortinet MIBS not being where Observium expects them. Hack Solution: mv /opt/observium/mibs/FORTINET-* /opt/observium/mibs/fortinet/ ./discovery.php -h all

Long version: We have been running a very old version for a long time ( 0.14.1.4945 ) and it's been ticking along nicely but I've finally found some time to do a test update to the latest svn and ran into an issue with Fortigate memory.

I ran a discovery with debug; attached as "memory debug.txt".

If I run one of those commands manually I get the following:

root@clone:/opt/observium# /usr/bin/snmpget -v2c -c 'test -snmp' -OvQ -m FORTINET-FORTIGATE-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp:/opt/observium/mibs/fortinet 'udp':'testdev.test.local':'161' fgSysMemUsage.0 MIB search path: /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp:/opt/observium/mibs/fortinet Cannot find module (FORTINET-FORTIGATE-MIB): At line 0 in (none) fgSysMemUsage.0: Unknown Object Identifier (Sub-id not found: (top) -> fgSysMemUsage)

The FORTINET-FORTIGATE-MIB files don't appear to have changed but Observium appears to be looking for them under "/opt/observium/mibs/fortinet/" when they are actually just under "/opt/observium/mibs/"

After doing this: root@clone:/opt/observium# cd mibs root@clone:/opt/observium/mibs# mkdir fortinet root@clone:/opt/observium/mibs# mv FORTINET-* ./fortinet/

and then running discovery again memory stats came back.

Has anyone else had this issue? If so maybe the MIBS need to be relocated in SVN?

Cheers, Nathan

---

observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium