geotek wrote:
> I have the same problem, zMySqlRootPassword does not show up, neither in 
> zProterties nor in Custom. My device is correctly bound to MySql and there 
> are some empty MySql graphs in the Perf tabs just as I would expect it.
> 

If you don't see zMySqlRootPassword on the custom schema page then your install 
of the MySqlMonitor zenpack is broken somehow.


geotek wrote:
> 
> I had to install the MySql Zenpack with easy_install because the Web GUI 
> installation shows the infamous AttributeError: 'CheckDnsDataSource' object 
> has no attribute '__of__' 
> 


The "object has no attribute '__of__'" error message means that zenoss can't 
find a ZenPack, in this case the DnsMonitor zenpack.

There are two basic, high level steps that happen when a zenpack is installed.  
First the python egg is installed into $ZENHOME/ZenPacks (usually) so that 
python is aware of the new code.  Next the ZenPack is instantiated and loaded 
within Zenoss itself.

easy_install is a tool that can be used to accomplish the first of those two 
steps.  This is useful in situations where the second step is complete but 
somehow the installation of the egg (first step) has a problem.  easy_install 
is not a general purpose alternative to the zenpack script however, which does 
both the first and second steps.

It looks like your DnsMonitor zenpack is not installed correctly.  Try the 
easy_install trick with DnsMonitor egg to see if that helps.  You want to 
repair that situation before installing any additional ZenPacks.  Again, the 
easy_install command to try to fix a broken install is

Code:

zenoss$ easy_install --site-dirs=$ZENHOME/ZenPacks -d $ZENHOME/ZenPacks <the 
zenpack .egg file>




-jason




-------------------- m2f --------------------

Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=20470#20470

-------------------- m2f --------------------



_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to