With regards to the issue of the the removal not working, that can be manually
fixed (assuming that you're in a hurry) by editing the __init__.py file by hand
and adding an extra argument to the remove function. In other words, the
updated version of 'remove' should look like:
Code:
def remove( self, app, leaveObjects=False ):
ZenPackBase.remove( self, app, leaveObjects )
NB: Python is space sensitive, so be careful not to add or remove spaces
before the 'def' or the 'ZenPackBase...' stuff.
I've fixed the ZenPack's code thanks to your comments, and I'll send the
update into Zenoss in the next couple of days. There exists the possibility
that after installing the update that you might be able to perform the
uninstall. If that's not successful, the manual update of the __init__.py
file will be necessary. (Oops!)
For the share path workaround (symlinking), I'm guessing that this issue is
something that should be a ticket in Zenoss Core. I've submitted a ticket
(3578) that provides another workaround that suggests adding the SMIPATH as a
zProperty, so that with an appropriate path this shouldn't be necessary.
There's probably still room for another ticket for the exact issue that you're
mentioning.
For the FF 2.0.0.6 issue, I'm not quite sure about the root cause. My
Ubuntu box is using FF 2.0.0.4, so it shouldn't be an issue with an older
version of FF. The behaviour that you're seeing (at a first guess) either
indicates that there was an issue with the MIB being converted into an XML file
(you can check that with the showMibasXML command) or a Javascript issue (which
can and has caused that issue -- in FF, open the Tools -> Error Console, browse
to the Mibs page, clear the errors and then open the MIB browser and then post
the results).
To use the showMibasXML command, go to the Mibs tree, select the MIB you
want to see in the MIB browser, and plunk showMibasXML at the end of it. The
complete URL will look something like:
http://myzenossserver:8080/zport/dmd/Mibs/mibs/myMibname/showMibasXML
You should see a screen that tells you that the browser can't find any
styling information, and so it displays the document tree. If you see this,
then there's a Javascript issue.
If there is a parsing error of some sort, you'll get a terribly
uninformative message stating something like "head <link> not formed" or some
such thing. This indicates an issue with attempting to create an XML file
from the MIB. Get the page source and post it.
kells
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=23838#23838
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
