Ken Snider wrote:
Todd Davis wrote:
You aren't trying to run Zenoss on the same machine with Zenoss-Plugins
installed on the same box are you? I was having a very similar problem
which was solved by uninstalling Zenoss-Plugins from the Zenoss box and
making sure to remove the residual
/usr/lib/python2.3/site-packages/zenoss
directory structure.
Actually, that is precisely what I am trying to do. I had assumed that
the plugins were used by the Zenoss server to perform the queries of
remote systems. Is this not the case? Are these plugins instead
intended solely for ssh-based queries of remote boxes?
Yes. Zenoss-Core contains support for command-style plugins that can
optionally be executed over an SSH connection. If you write a script
that returns a name=value style string, Zenoss can extract those
name-value pairs and store them as performance metrics. An example of
valid command-style output follows (it illustrates CPU performance
collection):
CPU OK;|ssCpuRawInterrupt=157056 laLoadInt1=0.10
ssRawContexts=484000836 laLoadInt5=0.16 ssCpuRawNice=274
ssCpuRawKernel=9486893 ssCpuRawSystem=9486893 ssCpuRawWait=41705457
laLoadInt15=0.15 ssRawInterrupts=7363971790 ssCpuRawIdle=1168817393
ssCpuRawUser=179793097
The Zenoss-Plugins distribution is a set of python modules that can be
used with the command-style performance collector. You would install
the Zenoss-Plugins onto remote boxes that you wish to monitor via SSH.
Note that in the future we'll be (hopefully) moving to an environment
where you don't need to install ANY software on the remote box in order
to monitor it. All you'll need is an SSH account, and Zenoss-Core will
do the rest. Magic... ;-)
(Which I suppose raises another question, whether I should be using
ssh-based data collection, or snmp based, in the case of Servers?)
SSH-based data collection is good in over-the-Internet environments
where you might not want to expose an SNMP agent to the world (or mess
with firewall configs to lock down access to the SNMP agent). We use
the Zenoss-Plugins to monitor our production servers.
SNMP-based data collection is good in intranet or local network
environments where a perimeter firewall prevents malicious public users
from connecting to your SNMP agent. We're talking the 192.168.0.0/16
and 10.0.0.0/8 subnets here...
Removing the plugins corrected the issue, and I've imported the zenoss
server into itself.
Good to hear. Let us know if you get stuck anywhere else - I'm
interested in hearing if your 64 bit installation works as well as I'm
hoping it should. :)
-c
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
