Sep 6, 2011 2:26 PM
Bug in 3.2 loading MIBs?
-
Like (0)
This is the only place my login can post ... sorry.
I am unable to load MIBs from the desktop on a fresh 3.2 core installation. ( Ubuntu 10.04 )
My private MIBs didn't work, so I tried a common one: SNMPv2-MIB It failed in the same way:
Load "MIB from desktop" choose file
Process starts...
No GUI errors.
Re-load page to see MIB
Page throws error: "uncatalogued exception"
dismiss error pop-up; page hangs on "loading"
zenoss restart... no change page still hangs
check jobs log:
2011-09-06 11:08:06,351 WARNING zen.ZenMib: Unable to parse information from /usr/local/zenoss/common/share/mibs/irtf/.index -- skipping
2011-09-06 11:08:06,796 WARNING zen.ZenMib: Unable to parse information from /usr/local/zenoss/common/share/mibs/ietf/.index -- skipping
2011-09-06 11:08:07,112 WARNING zen.ZenMib: Unable to parse information from /usr/local/zenoss/common/share/mibs/irtf/IRTF-NMRG-SMING -- skipping
2011-09-06 11:08:08,990 WARNING zen.ZenMib: Unable to parse information from /usr/local/zenoss/common/share/mibs/iana/.index -- skipping
2011-09-06 11:08:13,282 WARNING zen.ZenMib: Unable to parse information from /usr/local/zenoss/common/share/mibs/tubs/.index -- skipping
2011-09-06 11:08:13,553 WARNING zen.ZenMib: Unable to parse information from /usr/local/zenoss/common/share/mibs/irtf/IRTF-NMRG-SMING-EXTENSIONS -- skipping
2011-09-06 11:08:18,340 WARNING zen.ZenMib: Unable to parse information from /usr/local/zenoss/common/share/mibs/irtf/IRTF-NMRG-SMING-TYPES -- skipping
2011-09-06 11:08:18,672 WARNING zen.ZenMib: Unable to parse information from /usr/local/zenoss/common/share/mibs/site/.index -- skipping
2011-09-06 11:08:20,728 INFO zen.ZenMib: Found 1 MIBs to import.
2011-09-06 11:08:21,871 INFO zen.ZenMib: Parsed 57 nodes and 3 notifications from SNMPv2-MIB
2011-09-06 11:08:21,872 INFO zen.ZenMib: Loaded MIB SNMPv2-MIB into the DMD
2011-09-06 11:08:21,872 INFO zen.ZenMib: Loaded 1 MIB file(s)
Job completed at 2011-09-06 11:08:22. Result: success.
The only way to clear it I found was by zenrestore from backup. I don't see any ".index" in ~/mibs
Is this a bug?
John
I'm experiencing the exact same situation (UncataloguedObjectException) with a fresh 3.2 core installation on Ubuntu 10.04.
I've also followed some recomendations and tried to load them from console with zenmib, after adding SMIPATH variable and creating a couple of sym links and nothing, i get the exact same result.
John Fisher escribió:
The only way to clear it I found was by zenrestore from backup. I don't see any ".index" in ~/mibs
In my case ".index" files are present, maybe you don't see them because they are hidden?
I'm just getting started with Zenoss, so i hope someone can guide us where to look.
Sorry for the broken English.
Well, I've found a workaround to this problem. It's not a solution, but seems to work pretty well. It may help you, so I'll explain what I did.
For reasons that elude me (for the moment at least), if you change the name of the MIB (after adding it), the problem disappears and everything works perfectly. This must be repeated for every new MIB added. This is an example step by step of the "procedure":
Let's say you want to add 2 MIBs.
1- First, you add them, taking care about dependencies, etc. You can do it directly from the GUI or by using the zenmib command. Once added, if you go to Advanced->MIBs you will get the UncataloguedObject Exception.
2- Next, you must rename the MIBs you just added (put a "1" at the end of the name, for instance). After that, you can change the names back to the original ones, the important thing is to change them at least once.
This can be made going to: http://YOUR-SERVER:8080/zport/dmd/Mibs/manage#mibtree:/zport/dmd/Mibs and clicking "mibs". You will see a list of all the MIBs you have added. The rest is self-explanatory.
If you are willing to add a large number of MIBs, this could be a pretty tedious process. If that is the case, I'm almost sure this also could be done with a script in console, but that's another story.
3- Go to Advanced->Mibs again and everything should work.
Any thoughts or suggestions that could help me understand what is going on will be greatly appreciated.
PS: John, maybe I'm wrong, but I think the lines "WARNING zen.ZenMib: Unable to parse..." are "normal" since the index files cannot be parsed because, well, they are not mib files.
Thanks Francisco, I don't know how you figured that out, but good work. I bet it has something to do with the ZOPE db, and there must be a bug indeed. I am leaving this open in case somebody from Zenoss will notice it. I don't seem to have access to the bug system, or perhaps I just haven't seen the right link yet.
Your English is excellent.
John Fisher:
You could try rebuilding the global catalog. Ended up working here message/61963#61963
Please backup your ZODB before doing this. (Do a zeopack -h localhost -p8100 and copy the Data.fs.old somewhere safe)
As user zenoss, `python $ZENHOME/Products/ZenUtils/zencatalog.py --createcatalog --forceindex`
Best,
--Shane W. Scott(Hackman238)
ZCA - community/zca/blog
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||