Oct 11, 2012 10:40 PM
In Zenoss Core 4.2 , Is collector can only installed by Zenpack DistributedCollectors?
-
Like (0)
Advanced -> Collectors, I only get the possibility to add either a Monitor or a Remote Monitor, is this the same???
Monitors and Collectors are the same thing. You will find both terms used in the documentation. In the code, they are monitors. The modern word in the documentation is Collectors.
I would suggest that you do use the Distributed Collectors ZenPack if you want multiple collectotrs (though I haven't run it on 4.2 yet - anyone else????). In theory, you can follow documentation here docs/DOC-2496 but it is MUCH easier to deploy and manage remote collectors with Egor's magic ZenPack.
Cheers,
Jane
I'll just point out that that doc that Jane linked to is pretty outdated. It should still work in theory but a lot has changed in terms of the back end architechture since that was written. The Distributed Collectors pack is your best bet as it simplifies the process. Distributed collectors are not officially supported in core which is why that ZenPack was written.
Thanks : jcurry and Ryan Matte.
I just went through this. The steps I took where:
deploy collector instance (vm or otherwise)
run autodeploy script
chkconfig rabbitmq-server off
chkconfig snmpd off
chkconfig memcached off
chkconfig mysql off
service rabbitmq-server stop
service snmpd stop
service memcached stop
service mysql stop
setup hub zenoss user ssh keys on collector vm as per http://community.spiceworks.com/education/projects/Passwordless_SSH_Using_Shared_Keys
Make sure you install the distributed zenpacks collector: docs/DOC-5861
Restart zenoss on hub
After zenoss is done restarting, login goto advanced -> collectors -> add remote monitor (and all your remote monitors resolveable hostname or ip)
Afterwards you will need to edit the daemon configs in /opt/zenoss/etc
And I mean all the daemons... all the daemons should point to your hub's ip/resolve hostname in the following line:
#
# Configuration file for zenrender
#
# To enable a particular option, uncomment the desired entry.
#
# Parameter Setting
# --------- -------
#
# Host of zenhub daemon. Default is localhost.,
# default: localhost
hubhost myzenosshuborhubip
I did this for the zenrender.conf
zenperfsnmp e.t.c. (all of them)
After you are done doing this on the collector you should do a "zenoss restart" as the zenoss user. Once you do this you will be able to use your collector without any issues.
Thank you for sharing this with us.
I will assume that the modifications you suggest for the daemons configurations are to be performed on each and every collector but not on the hub. Just correct me if I'm wrong here.
Hi,
Yes I only made the daemon configuration changes on the collector.
I've followed your steps but I'm running into a problem with the collector connecting to the zenhub on the hub machine. Here are the errors when it tries to do a remote zendisc:
2013-02-28 14:39:52 INFO zen.ZenDisc Connecting to myhost.mydomain.net:8789
2013-02-28 14:39:52 WARNING zen.pbclientfactory Cancelling attempts to connect
2013-02-28 14:39:52 CRITICAL zen.pbclientfactory zenhub username/password combination is incorrect!
I see the zendisc process on the collector. I used tcpdump and do see the connection attempt to port 8789 on my hub machine. In the tcpdump conversation I see the collector sending "root" and "admin" where I think it's trying to send the username and password. So I'm guessing I have to change that someplace, but I'm not sure where. Any ideas?
I had this same problem. Check the hubpasswd ($ZENHOME/etc/) on your master and and make sure it matches the hub password on your collector in the global.conf ($ZENHOME/etc). The hub password in the global.conf was the last line. I would restart zenoss on your collector after this.
I also I had a problem with this install because of hosts.allow and hosts.deny. No zenoss service could talk to rrdcached. Remove/rename or add a line to these files to allow rrdcaches to accessed locally
Also make sure you do not have a stray zenoss services running. I stopped zenoss completely and still had some stray zenoss services running (zenhubworker, zope) so I had to kill them manually.
Boom! That fixed it. Thanks much!
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||