Feb 7, 2012 9:38 PM
how can configure distributed collectors in 4.1.70
-
Like (0)
Very glad to be among the first to 4.2 Beta test of users. We have been used to use Zenoss Distributed Collectors user management thousands of servers.
Therefore, I am interested in the 4.2 Beta test of distributed. But found and found a lot of function and old version of the different.
1. The modification of the acquisition process etc, to the acquisition of the structure will process data collection to the master server up.
Monitor localhost
Hubhost master
2. Modification of the motion process node points, will be unnecessary process terminates off. The process of start will include:
Zenperfsnmp
Zencommand
Zenporcess
Zenping
......
3. In the Main interface, add Collector, and by using the traditional method (http://DChost:8080/zport/RenderServer).
4. I want to ZODB data processing by the Memcached is, therefore, try changing zope. Conf Memcached address will point to Master of 11211
I thought this configuration can let the distributed system shipped preach up, but the results found that I was wrong.
First of all, in the Web interface, and can't find add to the Distributed Collectors equipment performance image.
Second, Distributed Collectors Server found only in the performance of the Master files (perf/Devices /)
Finally, feeling, in the Distributed Collectors Web displayed in information and Master interface shown in different content.
I think it is in ZODB and data collection on a problem, but I don't know how to change, because, I for new structures are still not very well.
Almost the same: I have Egor's distributed collectors running on Zenoss 3.2.0 (CentOS 5.8 stack-installer). I'm planning to migrate my system to newer Zenoss 4.x (CentOS 6.3 rpms). Is this possible to run distributed collectors the same way on the new 4.x version?
check latest ZenPack version from my git repository: https://github.com/epuzanov/ZenPacks.community.DistributedCollectors
WARNING! this version is for testers only, do not install it on production system.
Egor, early results look pretty good.
It appears zenactiond is not in the list of DEFAULT_MASTER_DAEMONS, and as such its listed in daemons.txt. Should this daemon be running on the collector, or the master only? As I understand it, its th replacement to zenactions, so I think it needs to be added to the list.
I also noticed that zenrrdcached was not configurd to be running on the collector, even though its not listed in the DEFAULT_MASTER_DAEMONS. I don't know alot about this daemon, but from the *very* little I know, I think it should running on the collector
That aside, I was able to add the collector cleanly, and so far things look OK. I'll know a little more once its had a few cycles to collect some data and such.
This zenrrdcached issue looks like it might be caused by the fact that deamon is not listed in dmd.About.getZenossDaemonStates(), however it is shown when you run a zenoss status from the CLI.
Seems like a bug in Core to me that dmd.About.getZenossDaemonStates() doesnt show the status of zenrrdcached?
Not sure why, but zenrrdcached is intentionally excluded from the about of getZenossDaemonStates() via the exclusion in _getDaemonList()
http://dev.zenoss.org/trac/browser/tags/zenoss-4.2.0/Products/ZenModel/ZenossInfo.py#L471
Not to sure thats excluded... but it looks intentional..
Hello dpetzel,
thanks for testing and your comments. Please, check my github repo for the updated ZenPack version.
I have not had much time to track down why, but I'm seeing zenrrdcached showing up multiple times in my daemons.txt file.. Not sure if there needs to be a check that its not already there before writing it?
So something is certainly up...
I think you want to move the following outside of the for loop. It looks like the current version spits this out once for every other daemon in the status list.
if VERSION < '4.0': continue
daemons.write('zenrrdcached\n')
Take a look at the before and after (updating remote monitor)
[zenoss@collector ~]$ cat /opt/zenoss/etc/daemons.txt
zenping
zensyslog
zenstatus
zentrap
zenmodeler
zenperfsnmp
zencommand
zenprocess
zenjmx
zenwinperf
zenwin
zeneventlog
[zenoss@collector ~]$ cat /opt/zenoss/etc/daemons.txt
zenping
zenrrdcached
zensyslog
zenrrdcached
zenstatus
zenrrdcached
zentrap
zenrrdcached
zenmodeler
zenrrdcached
zenperfsnmp
zenrrdcached
zencommand
zenrrdcached
zenprocess
zenrrdcached
zenjmx
zenrrdcached
zenwinperf
zenrrdcached
zenwin
zenrrdcached
zeneventlog
zenrrdcached
thanks dpetzel, fixed on github
Hi
I'm trying to get this ZenPack to work on Core 4.2...
I have downloaded the newest version from Github, and it seems to install fine..
I'm quite new to zenoss, where do I go from here to add a new collector...
If I go to the Advanced -> Collectors, I only get the possibility to add either a Monitor or a Remote Monitor, is this the same???
If I try to add either of the two I get prompted for an ID, and nothing else... Where do I get this ID from...
Thanks
Follow Us On Twitter »
|
Latest from the Zenoss Blog » | Community | Products | Services Resources | Customers Partners | About Us | ||
Copyright © 2005-2011 Zenoss, Inc.
|
||||||||