ZenPacks : Collector Tool : Comments

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 15:29:57 GMT

Hey,

I am trying to get this setup, when i run zencollectortool in new collector it does not go past

Modifying configuration options in /opt/zenoss/etc/zentrap.conf:

monitor zenoss-master.root
hubhost zenoss-collector.root

Its been sitting here for more than 30 mins, am i missing out any process here?

Thanks

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 15:34:54 GMT

I've never seen that behaviour before and I've tested the script across 5 different Zenoss servers and 2 different versions. All it's doing when it's editing those files is a sed command to replace one string with another. It shouldn't cause any freezing. Why are you using zenoss-master.root and zenoss-collector.root as the hostnames?

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 15:48:55 GMT

Ryan

Zenoss-master.root is my zenoss master hosts, and zenoss-collector.root is collector hosts.

zenoss-master.root - primary zenoss (as master)

zenoss-collector.root - secondary zenoss (as collector)

I just named them this way to test the collectortool.

I still cant get passed that step..

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 15:49:50 GMT

A qq -

Do i need have mysql running in collector hosts?

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 16:06:44 GMT

I am boggled that you can't get past that step, I've looked at the code and there's nothing there that could cause it to freeze up. No, you don't need to be running MySQL on the collector (the script actually explains that if it were to get past that step). Perhaps it's getting stuck because $ZENHOME/etc/zenrender.conf doesn't exist? Check if it exists, if not create it with the following command: "touch $ZENHOME/etc/zenrender" as the zenoss user, then try again.

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 16:12:48 GMT

You're getting caught up on this code:

if [ $zenperfwmicheck == 1 ]
                        then
                                echo zenperfwmi >> $ZENHOME/etc/daemons.txt
                                files=( "$ZENHOME/etc/zenping.conf" "$ZENHOME/etc/zensyslog.conf" \
                                "$ZENHOME/etc/zenstatus.conf" "$ZENHOME/etc/zentrap.conf" \
                                "$ZENHOME/etc/zenrender.conf" "$ZENHOME/etc/zenperfsnmp.conf" "$ZENHOME/etc/zencommand.conf" \
                                "$ZENHOME/etc/zenprocess.conf" "$ZENHOME/etc/zenwin.conf" "$ZENHOME/etc/zeneventlog.conf" \
                                "$ZENHOME/etc/zenperfwmi.conf" )
                        else
                                files=( "$ZENHOME/etc/zenping.conf" "$ZENHOME/etc/zensyslog.conf" \
                                        "$ZENHOME/etc/zenstatus.conf" "$ZENHOME/etc/zentrap.conf" \
                                        "$ZENHOME/etc/zenrender.conf" "$ZENHOME/etc/zenperfsnmp.conf" "$ZENHOME/etc/zencommand.conf" \
                                        "$ZENHOME/etc/zenprocess.conf" "$ZENHOME/etc/zenwin.conf" "$ZENHOME/etc/zeneventlog.conf" )
                        fi

                        echo -e "\nThe following files will be updated:\n"
                        printf "%s\n" "${files[@]}"
                        echo "$ZENHOME/etc/zope.conf"
                        for f in "${files[@]}"
                        do
                                monitorcheck=$(grep monitor $f 2>/dev/null | wc -l)
                                hubhostcheck=$(grep hubhost $f 2>/dev/null | wc -l)

                                echo -e "\nModifying configuration options in $f:\n"
                                echo "monitor $collector"
                                echo "hubhost $master"

                                if [ $monitorcheck == 1 ]
                                then
                                        sed -i 's/^.*monitor.*$/monitor '$collector'/g' $f
                                else
                                        if [ $monitorcheck > 1 ]
                                        then
                                                sed -i '/^.*monitor.*$/d' $f
                                        fi
                                        echo "monitor $collector" >> $f
                                fi

                                if [ $hubhostcheck == 1 ]
                                then
                                        sed -i 's/^.*hubhost.*$/hubhost '$master'/g' $f
                                else
                                        if [ $monitorcheck > 1 ]
                                        then
                                                sed -i '/^.*hubhost.*$/d' $f
                                        fi
                                        echo "hubhost $master" >> $f
                                fi
                        done

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 16:24:06 GMT

zenrender.conf does exists.

-rwxrwxr-x 1 zenoss zenoss   22 Apr 1 11:56 /opt/zenoss/etc/zenactions.conf
-rwxrwxr-x 1 zenoss zenoss 155 Aug 5 2009 /opt/zenoss/etc/zenbackup.conf
-rwxrwxr-x 1 zenoss zenoss 307 Apr 1 11:56 /opt/zenoss/etc/zencommand.conf
-rwxrwxr-x 1 zenoss zenoss   22 Aug 5 2009 /opt/zenoss/etc/zendisc.conf
-rwxrwxr-x 1 zenoss zenoss 342 Apr 1 12:16 /opt/zenoss/etc/zeneventlog.conf
-rwxrwxr-x 1 zenoss zenoss 370 Apr 1 12:14 /opt/zenoss/etc/zenhub.conf
-rwxrwxr-x 1 zenoss zenoss 2388 Aug 5 2009 /opt/zenoss/etc/zenjmx.conf
-rwxrwxr-x 1 zenoss zenoss 286 Nov 16 10:18 /opt/zenoss/etc/zenjobs.conf
-rwxrwxr-x 1 zenoss zenoss   30 Aug 5 2009 /opt/zenoss/etc/zenmib.conf
-rwxrwxr-x 1 zenoss zenoss   22 Aug 5 2009 /opt/zenoss/etc/zenmigrate.conf
-rwxrwxr-x 1 zenoss zenoss   90 Apr 1 12:12 /opt/zenoss/etc/zenmodeler.conf
-rwxrwxr-x 1 zenoss zenoss   22 Aug 5 2009 /opt/zenoss/etc/zenpack.conf
-rwxrwxr-x 1 zenoss zenoss 333 Apr 1 12:16 /opt/zenoss/etc/zenperfsnmp.conf
-rwxrwxr-x 1 zenoss zenoss 345 Apr 1 11:51 /opt/zenoss/etc/zenping.conf
-rwxrwxr-x 1 zenoss zenoss 295 Apr 1 11:56 /opt/zenoss/etc/zenprocess.conf
-rwxrwxr-x 1 zenoss zenoss 101 Apr 1 12:11 /opt/zenoss/etc/zenrender.conf
-rwxrwxr-x 1 zenoss zenoss 348 Apr 1 11:51 /opt/zenoss/etc/zenstatus.conf
-rwxrwxr-x 1 zenoss zenoss 401 Apr 1 11:51 /opt/zenoss/etc/zensyslog.conf
-rwxrwxr-x 1 zenoss zenoss 337 Apr 1 11:51 /opt/zenoss/etc/zentrap.conf
-rwxrwxr-x 1 zenoss zenoss 134 Apr 1 12:16 /opt/zenoss/etc/zenwin.conf
-rwxrwxr-x 1 zenoss zenoss   48 Aug 5 2009 /opt/zenoss/etc/zenwinmodeler.conf
-rwxrwxr-x 1 zenoss zenoss   22 Aug 5 2009 /opt/zenoss/etc/zenxevent.conf

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 16:26:16 GMT

So this is the absolute last thing that you see when running the script:

Modifying configuration options in /opt/zenoss/etc/zentrap.conf:

monitor zenoss-master.root
hubhost zenoss-collector.root

???

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 16:33:09 GMT

when i run zencollectortool i see 2 daemons running is this normal?

zenoss 11950 11920 0 11:50 pts/2 00:00:00 /bin/bash /opt/zenoss/bin/zencollectortool
zenoss 12269 11950 0 11:51 pts/2 00:00:00 /bin/bash /opt/zenoss/bin/zencollectortool

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 16:33:50 GMT

correct! it does not go beyond modifying zentrap.conf

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 16:37:36 GMT

It's not a daemon, it's just a script. What you're seeing is the scripts that have been run and are hung for whatever reason. you should do killall -9 zencollectortool. I've poured through the code and there's absolutely no reason for it to be freezing. Is this on a clean server with a clean Zenoss install? How did you go about installing Zenoss? It looks like you're possibly using the appliance?

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 16:51:23 GMT

Yes, it is clean zenoss install.

I am going to wipe out and re-install zenoss and try again. I will update you how that goes.

Thanks

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 17:46:05 GMT

NO success stucked at the same step, even reverting has the same behavior.

is there a manual process for this?

Thanks

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 17:47:43 GMT

The manual process is here: http://community.zenoss.org/docs/DOC-2496

However, I would really like to know what's causing your issue. Guess I'll wait and see if anyone else runs in to problems. What version of Linux are you running Zenoss on, and how did you install Zenoss (stack, rpm, etc...)?

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 18:36:32 GMT

final question on manual setup.

When i try the render url (http://zenoss-master.root:8090/zenoss-collector.root) i get bunch of twisted connection error.

web.Server Traceback (most recent call last):

exceptions.IndexError: list index out of range

/opt/zenoss/lib/python/twisted/web/server.py, line 150 in process

148 try:

149 resrc = self.site.getResourceFor(self)

150 self.render(resrc)

151 except:

Self

I believe the collector is working, I moved one device to remote collector (zenoss-collector.root) and when i see zenprocess.log I see its getting processes.

Can you suggests what am i missing here?

Thanks

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 18:57:57 GMT

You have to restart the master server after setting the render url.

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 19:37:08 GMT

multiple master zenoss restart did not help at all, still getting same error.

Nothing seems to work for me today, looks like its one of those days where things get pretty complicated.

I will let you know which worked for me.

Thanks

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 19:52:51 GMT

What version of Linux are you running Zenoss on, and how did you install Zenoss (stack, rpm, etc...)? I need to know so that I can do testing and fix anything that's wrong (if there is actually a problem with the script).

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 20:03:02 GMT

CentOS 5

zenoss installed via rpm

FYI, I am seeing these errors in event.log,

2010-04-01T15:51:17 ERROR zen.RRDView <ProtocolError for zenoss-master.root:8090/zenoss-collector.root: 500 Internal Server Error>
Traceback (most recent call last):
File "/zenoss/zenoss/Products/ZenModel/RRDView.py", line 167, in getRRDValues
    vals = perfServer.performanceCustomSummary(gopts)
File "/zenoss/zenoss/Products/ZenModel/PerformanceConf.py", line 395, in performanceCustomSummary
    return server.summary(gopts)
File "/opt/zenoss/lib/python2.4/xmlrpclib.py", line 1153, in __call__
    return self.__send(self.__name, args)
File "/opt/zenoss/lib/python2.4/xmlrpclib.py", line 1440, in __request
    verbose=self.__verbose
File "/opt/zenoss/lib/python2.4/xmlrpclib.py", line 1194, in request
    headers
ProtocolError: <ProtocolError for zenoss-master.root:8090/zenoss-collector.root: 500 Internal Server Error>
------
2010-04-01T15:51:17 ERROR zen.RRDView Unable to cache value for sysUpTime

I see rrd's are being updated with data on new collector host, but when i go to perf tab in master hosts I cant see the graph as well, and renderer url is still not working.

here is the rrd fetch info from sysUpTime_sysUpTime.rrd of the device thats being moved to new collector

1270150400: 1.3831442743e+08
1270150800: 1.3835872456e+08
1270151200: 1.3839622452e+08
1270151600: 1.3843442651e+08
1270152000: nan
1270152400: nan

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 20:54:16 GMT

Ummm, protocol error eh?

Did you by chance put zenoss-master.root:8090/zenoss-collector.root instead of http://zenoss-master.root:8090/zenoss-collector.root ?

RE: Collector Tool

community@zenoss.org — Thu, 01 Apr 2010 20:55:13 GMT

Just to add, you can always try it with IP addresses instead of hostnames.

RE: Collector Tool

community@zenoss.org — Fri, 02 Apr 2010 13:46:37 GMT

Nope, I have http://zenoss-master.root:8090/zenoss-collector.root as zenrender URL.

I wiped out zenoss on both master and collector, and started from scratch, still zencollectortool did not pass beyond trap.conf.

I did the manual process and master/collector is working as expected but the zenrender url still gives me same error.

web.Server Traceback (most recent call last):

exceptions.IndexError: list index out of range

/opt/zenoss/lib/python/twisted/web/server.py, line 150 in process

148 try:

149 resrc = self.site.getResourceFor(self)

150 self.render(resrc)

151 except:

Self

site	twisted.web.server.Site instance @ 0x16630ab8 <twisted.web.server.Site instance at 0x16630ab8>

Locals

resrc	Products.ZenHub.services.ZenRender.Render instance @ 0x16630248 <Products.ZenHub.services.ZenRender.Render instance at 0x16630248>
self

I will try again may be next week with fresh install and see where that leads me. So far I have added 500 devices 250 each.. and its working very smoothly, i would like to get zenrender url to work.

Thanks.

RE: Collector Tool

community@zenoss.org — Tue, 06 Apr 2010 12:23:13 GMT

I'm seeing the same issue when running on a collector - the script freezes at this point:

Modifying configuration options in /opt/zenoss/etc/zentrap.conf:

monitor zenoss-collector-ip

hubhost zenoss-master-ip

RE: Collector Tool

community@zenoss.org — Tue, 06 Apr 2010 14:14:00 GMT

It's difficult for me to troubleshoot it since I can't reproduce the issue on any of my Zenoss installs. I've tried it on clean 2.5.2 installs, I've tried it on 2.4.5 installs. I've tried it on installs that were upgraded from 2.4.5 to 2.5.2. It worked flawlessly in all cases. I've looked at the code and can't see any reason for the freezing. Do either of you have any bash scripting experience? If so, perhaps you could mark a section of the code with echo lines to try and pinpoint exactly what part of the code it is getting hung up on. It's very strange that it's just freezing. I've never seen that with a bash script before, generally they either work or error out.

RE: Collector Tool

community@zenoss.org — Mon, 12 Apr 2010 18:06:56 GMT

Ryan,

I'm using RHEL 5.5, and Zenoss Core 2.5.2. I'm seeing the same issue that others are seeing with the script just hanging. the problem is in your script on line 228. There is a trailing space after the "\" at the end of the line. For some reason this is causing the script to hang. I removed the space and the script worked fine for me. You might want to update the Zenpack for users who are experiencing the issue. It could be a RHEL specific bug with bash or something else goofy Other than that, thanks for the script!

RE: Collector Tool

community@zenoss.org — Mon, 12 Apr 2010 18:20:14 GMT

Wow, nice find. I'm amazed that that's what was causing it to hang. I'll have an updated version of the script with the space removed posted asap.

RE: Collector Tool

community@zenoss.org — Mon, 12 Apr 2010 18:49:40 GMT

I just posted version 1.1 with the bugfix. Thanks to jimmyoliver for troubleshooting the issue and bringing it to my attention.

RE: Collector Tool

community@zenoss.org — Thu, 29 Apr 2010 23:04:49 GMT

I just noticed that I forgot to remove the space from the part where it does the reversion too, I'll have another update to fix that soon.

RE: Collector Tool

community@zenoss.org — Fri, 30 Apr 2010 08:53:30 GMT

I've just stepped through the script and found one other instance of a space at the end of a line as well as the one in the reversion area and jimmyoliver's on line 228. (Sorry, I didn't note which line the one I found was on). After clearing the space that jimmyoliver found the script still froze at the same point, but after clearing the space in the reversion section and the one I found (somewhere around the configure master or collector sections) everything ran correctly.

jimmyoliver is right though - there is clearly a bug in CenntOS 5.5.

Perhaps now this is working I'll be able to add ZenPacks to my collector without needing to perform major configuration changes to the system - I will be able to do this won't I?

RE: Collector Tool

community@zenoss.org — Fri, 30 Apr 2010 14:43:21 GMT

Nah, it's not a bug related to CentOS. The reason it ran fine for me is because I have the WMI Data Source ZenPack installed. The section of code that the script uses when that ZenPack is installed doesn't have the problem. I already fixed the code for the collector setup so that's working fine, the reversion portion is what I need to fix, but I doubt many people will be using that. I'll be releasing version 1.2 which will be completely bug free.

RE: Collector Tool

community@zenoss.org — Fri, 07 May 2010 09:08:32 GMT

I'm currently also working on a project with Zenoss.

But i have 2 questions:

1. do you need a VPN connection to connect the 2 zenoss-machines with each other or how is this best done? My master zenoss finds the remote zenoss with his hostname which is a dyndns.org-hostname, i can add a device in the networkrange at that network, but even after setting the zWinuser and password, my master zenoss gives me an error while modeling the device: are your snmp settings correct?

They are correct and i can do an snmpwalk at the local zenoss too the device.

2. after running the zencollectortool, zenoss was unable to start zenperfwmi. It gave an error: no such file or directory: /usr/local/zenoss/bin/zenperfwmi. I went to the file and it was in red with a dark highlighting.

could you help me please?

RE: Collector Tool

community@zenoss.org — Fri, 07 May 2010 15:16:26 GMT

If /usr/local/zenoss/bin/zenperfwmi doesn't exist then the WMI Data Source pack is not installed correctly. It's in red because it's meant to be a link to the actual zenperfwmi file in the ZenPack's directory, but the link is broken because the file no longer exists. Reinstall it. As far as how you connect the servers, that's entirely up to you. They just need to be able to communicate with each other on various ports. Make sure you're not firewalling ports that they need. If it's complaining about SNMP settings zWinUser and zWinPassword have nothing to do with it. zWinUser and zWinPassword are used for WMI monitoring.

RE: Collector Tool

community@zenoss.org — Sun, 09 May 2010 17:43:38 GMT

alright, thank you. Tomorrow i'll will connect them with a VPN-connection. Then i let this collectortool run and the remote zenoss will perform the modeling of the devices in that network and report everything back to the master-zenoss, right?

RE: Collector Tool

community@zenoss.org — Tue, 11 May 2010 09:50:13 GMT

ok, so i made a VPN-tunnel. My remote had an IP of 172.16.x.x in the end and the master-zenoss has also. I ran the zencollectortool and added the remote-zenoss to the monitors in my master + changed the renderserverURL.

So then i add a device, which is in an other range: 192.168.x.x and set the right collector for it. He finds the device, but times when zen.SnmpClient starts: Device timed out: SNMP info for 192.168.x.x at 192.168.x.x:161 timeout: 2.5 tries: 2 version: v1 community: public

Warning: zen.snmpclient: device 192.168.x.x timed out: are your SNMP settings correct?

I have the SNMP-service, SNMPTRAP-service and snmp-informant installed on that computer.

Even when i run zenmodelere on the remote-zenoss with: zenmodeleren run --now -F -d 192.168.x.x, it hangs saying:
INFO.zen.ZenModeler: connecting to localhost:8789

ERROR.zen.ZenModeler: Timeout connecting to ZenHub: is it running?

could somebody help me please?

RE: Collector Tool

community@zenoss.org — Tue, 11 May 2010 13:32:52 GMT

Ok, this is one of those "let's go back to basics" moments. I see that you're using the "public" snmp string. Are you 100% sure that that is the string that is set on that device? Are you 100% sure that the snmp settings are correct on that device in general (can you model/monitor it from the localhost collector?)

RE: Collector Tool

community@zenoss.org — Fri, 14 May 2010 15:47:25 GMT

I have updated the script to fix one final bug that was present.

RE: Collector Tool

community@zenoss.org — Sat, 15 May 2010 11:05:07 GMT

Hey Ryan

I've got it working. The problem was that zenmodeler.conf was not adjusted like the other conf-files. So now i can give the command on the remote-zenoss to model a device in that network and the results are transferred to the central zenoss.

But giving the command in the central zenoss to model a device with the collector from that network is not working. Is that normal or?

I'm using a VPN-connection between the 2 zenoss-machines, so now the remote-zenoss workings like a daemon for that network.

RE: Collector Tool

community@zenoss.org — Mon, 17 May 2010 11:06:49 GMT

Additional question: what if i want to install new ZenPacks? Suppose i want to install the HP Proliant Monitor after the zencollectortool as been run. How do i install the zenpack then? Stopping the zenoss not possible and when i install the pack on the remote zenoss with the command: zenpack --install=<zenpack>, i get: Warning: ZEO.zrpc (3888- CW: error connecting to ('localhost', 8100): ECONNREFUSED

FIXED: thanks to this thread: http://community.zenoss.org/message/38336#38336

RE: Collector Tool

community@zenoss.org — Mon, 17 May 2010 14:56:44 GMT

Yeh, all you need to do is copy the actual ZenPack directory over to the ZenPacks directory on the remote collector. I'm pretty sure that only being able to run the zenmodel command from the commandline on the remote collector is normal since when you do it from the UI it signals that collector to run zenmodel.

RE: Collector Tool

community@zenoss.org — Fri, 28 May 2010 13:29:17 GMT

Little problem. I add an OS process for a computer in the remote network. But when I close the process, my central Zenoss does not show the changed status of the OS process even after 15minutes waiting. unless i remodel the remote device again.

How can this be?

The remote device is in a networkrange: 192.168.x.x with the local zenoss, with an IP in the 192.168.-range, is connected with the central zenoss through a VPN with 172.16.x.x.

Is it because the SNMP-messages can't reach the 172.16-IP?

RE: Collector Tool

community@zenoss.org — Fri, 28 May 2010 15:22:48 GMT

Make sure that you push changes to the collector by selecting Manage -> Push Changes from the dropdown menu on the OS tab. The collector only automatically pulls new configuration info every hour, so you need to push the changes to it. Also, zenprocess can be a bit flaky. When I make any changes to processes being monitored I find that restarting zenprocess is the best way to ensure that it is functioning properly. Restart it on the collector that the device is assigned to obviously.

RE: Collector Tool

community@zenoss.org — Mon, 31 May 2010 08:11:45 GMT

hmm, doesn't seem to help... I really need this to work, because this is a vital element for us.

zenprocess.conf is adjusted with the monitor and hubhost-parameter.

EDIT: in the snmp-service in a windows-computer, do i have to set the settings at the tab "Traps" Community name and trap destinations: ?

in the "Security"-tab i have: send authentication trap enabled and a community name: public read-only and selected: accept SNMP packets from any host

RE: Collector Tool

community@zenoss.org — Tue, 01 Jun 2010 17:55:59 GMT

Hi Ryan, it's normal that under collector / mynewcollector/ performance all zenmodeler graph are empty?

(missing rrd file)?

/opt/zenoss/perf/Daemons
[zenoss@zenoss01 Daemons]$ ls
mynewcollector localhost

localhost graph:

zencommand_commands.rrd zenperfsnmp_success.rrd
zencommand_configTime.rrd zenping_configTime.rrd
zencommand_cyclePoints.rrd zenping_cycleTime.rrd
zencommand_dataPoints.rrd zenping_devices.rrd
zencommand_eventQueueLength.rrd zenping_eventQueueLength.rrd
zencommand_schedule.rrd zenprocess_configTime.rrd
zeneventlog_configTime.rrd zenprocess_cyclePoints.rrd
zeneventlog_cyclePoints.rrd zenprocess_dataPoints.rrd
zeneventlog_dataPoints.rrd zenprocess_devices.rrd
zeneventlog_devices.rrd zenprocess_eventQueueLength.rrd
zeneventlog_eventQueueLength.rrd zenstatus_configTime.rrd
zeneventlog_events.rrd zenstatus_cycleTime.rrd
zenhub_services.rrd zenstatus_eventQueueLength.rrd
zenhub_totalCallTime.rrd zenstatus_failed.rrd
zenhub_totalEvents.rrd zenstatus_success.rrd
zenhub_totalTime.rrd zensyslog_eventQueueLength.rrd
zenhub_workListLength.rrd zensyslog_events.rrd
zenmodeler_cycleTime.rrd zensyslog_totalTime.rrd
zenmodeler_devices.rrd zentrap_eventQueueLength.rrd
zenmodeler_eventQueueLength.rrd zentrap_events.rrd
zenmodeler_timedOut.rrd zentrap_totalTime.rrd
zenperfsnmp_configTime.rrd zenwin_configTime.rrd
zenperfsnmp_cyclePoints.rrd zenwin_cyclePoints.rrd
zenperfsnmp_cycleTime.rrd zenwin_dataPoints.rrd
zenperfsnmp_dataPoints.rrd zenwin_devices.rrd
zenperfsnmp_eventQueueLength.rrd zenwin_eventQueueLength.rrd
zenperfsnmp_failed.rrd

myremotecollector log

zenmodeler_cycleTime.rrd zenmodeler_devices.rrd zenmodeler_timedOut.rrd

in i ssh on remote colletor and make an ls on same dir

zencommand_commands.rrd zenping_eventQueueLength.rrd
zencommand_configTime.rrd zenprocess_configTime.rrd
zencommand_cyclePoints.rrd zenprocess_cyclePoints.rrd
zencommand_dataPoints.rrd zenprocess_dataPoints.rrd
zencommand_eventQueueLength.rrd zenprocess_devices.rrd
zencommand_schedule.rrd zenprocess_eventQueueLength.rrd
zeneventlog_configTime.rrd zenstatus_configTime.rrd
zeneventlog_cyclePoints.rrd zenstatus_cycleTime.rrd
zeneventlog_dataPoints.rrd zenstatus_eventQueueLength.rrd
zeneventlog_devices.rrd zenstatus_failed.rrd
zeneventlog_eventQueueLength.rrd zenstatus_success.rrd
zeneventlog_events.rrd zensyslog_eventQueueLength.rrd
zenperfsnmp_configTime.rrd zensyslog_events.rrd
zenperfsnmp_cyclePoints.rrd zensyslog_totalTime.rrd
zenperfsnmp_cycleTime.rrd zentrap_eventQueueLength.rrd
zenperfsnmp_dataPoints.rrd zentrap_events.rrd
zenperfsnmp_eventQueueLength.rrd zentrap_totalTime.rrd
zenperfsnmp_failed.rrd zenwin_configTime.rrd
zenperfsnmp_success.rrd zenwin_cyclePoints.rrd
zenping_configTime.rrd zenwin_dataPoints.rrd
zenping_cycleTime.rrd zenwin_devices.rrd
zenping_devices.rrd zenwin_eventQueueLength.rrd

so no zenmodeler rrd...

RE: Collector Tool

community@zenoss.org — Wed, 02 Jun 2010 13:24:33 GMT

A couple of things can cause no RRDs to be displayed.

1. If you moved devices that were originally added to the localhosts collector but did not copy the RRD files for that device over to the remote collector.

2. If you set monitor on the remote collector to 127.0.0.1 or localhost. It needs to be the IP or a hostname that corresponds to the IP of an actual network interface.

RE: Collector Tool

community@zenoss.org — Thu, 03 Jun 2010 08:57:09 GMT

I'm really getting tired of Zenoss not doing what it has to do. Why doesn't the zenwin-daemon collect the win services on the local computers in a remote network? The zenwin-daemon is running on that remote collector and has the right monitor and hubhost-parameter in the conf-file... Also i've noticed that the zenprocess is buggy. On the master Zenoss and on the remote Zenoss...

When i run the command: zenwin run -d <ip-address> it gives the following results:
connecting to <master-zenoss-IP-address:8789
connected to zenHub

Configuration for <ip-address> unavailable
daemon Collectordaemon shutting down

and yes, the wmi provider is installed on the local machine

RE: Collector Tool

community@zenoss.org — Thu, 03 Jun 2010 14:27:26 GMT

I'm not sure as I haven't used zenwin with this setup. Just to be clear, the collector model isn't officially supported in core. This is a method of configuring remote collectors which the community has hashed together. I'm pretty sure there are still steps that need to be hashed out.

zenprocess is a bit buggy in the sense that I've found that I need to restart it after making changes to process monitoring settings to guarantee that the settings take (which I can live with). Otherwise it works fine.

RE: Collector Tool

community@zenoss.org — Fri, 04 Jun 2010 07:21:19 GMT

I don't know... Maybe it's because of my set-up or Zenoss is completely messed up...

Say i want to monitor Firefox. I add the process in the Process-tab and use firefox.exe as regex. Then i go to the machine i want to monitor firefox on. I add the process and then select it and enable monitoring on it. I push the changes, do i have to remodel the device then? Even if i do, somehow Zenoss does not change the status...

RE: Collector Tool

community@zenoss.org — Fri, 04 Jun 2010 13:47:32 GMT

The way I do it is to go to the Processes section in the left hand menu. I add the process with a name and regex that match the exe name (such as BESAlert.exe). In the case of windows processes I make sure that the option "Ignore Parameters" is set to True for each process. I then navigate to Settings -> Daemons and click restart next to zenprocess (which only takes a few seconds and guarantees that zenprocess picks up the new config). Then I push changes to the collector and remodel the device. As long as the processes on the device aren't locked it should add the new process as monitored (works all the time for me).

RE: Collector Tool

community@zenoss.org — Fri, 04 Jun 2010 17:19:01 GMT

to block this note grow i create a post on collector issue

http://community.zenoss.org/thread/13656

RE: Collector Tool

community@zenoss.org — Fri, 04 Jun 2010 17:24:25 GMT

Thanks, it was getting quite long.

RE: Collector Tool

community@zenoss.org — Mon, 07 Jun 2010 07:21:00 GMT

ok, maybe this is a stupid question, but must the process be running on the host when you add the process to the host in zenoss? I'm slightly guessing yes...

RE: Collector Tool

community@zenoss.org — Mon, 07 Jun 2010 14:35:44 GMT

It has to be running on the host when you remodel the device in Zenoss. Otherwise it won't detect it and automatically add it to the processes list.

RE: Collector Tool

community@zenoss.org — Tue, 08 Jun 2010 10:48:25 GMT

alright, thanks!

RE: Collector Tool

community@zenoss.org — Fri, 18 Jun 2010 19:18:46 GMT

Has anyone else ran into where the multigraph reports no longer show graphs. I copied all the RRD files to the main server to see if that would help. its not saying no RRD file, it doesnt show the graph at all just the two side zoom buttons.

RE: Collector Tool

community@zenoss.org — Tue, 24 Aug 2010 20:52:51 GMT

Hello,

I have fixed a little bug on script "zencollectortool" inside "ZenPacks.Nova.Collector.Tool-1.2-py2.4.egg\ZenPacks\Nova\Collector\Tool\bin\"

Change in line 278 of file "zencollectortool"

su root -c "sed -i 's/### \$MYSQL_SCRIPT start/\$MYSQL_SCRIPT start/g' $ZENHOME/../ctlscript.sh && sed -i 's/### \$MYSQL_SCRIPT stop/\$MYSQL_SCRIPT stop/g' $ZENHOME/../ctlscript.sh && /usr/local/zenoss/mysql/scripts/ctl.sh start"

for

RE: Collector Tool

community@zenoss.org — Wed, 25 Aug 2010 13:55:58 GMT

Also in

su root -c "sed -i 's/\$MYSQL_SCRIPT start/### \$MYSQL_SCRIPT start/g' $ZENHOME/../ctlscript.sh && sed -i 's/\$MYSQL_SCRIPT stop/### \$MYSQL_SCRIPT stop/g' $ZENHOME/../ctlscript.sh && $ZENHOME/../mysql/scripts/ctl.sh stop"

RE: Collector Tool

community@zenoss.org — Wed, 25 Aug 2010 15:25:33 GMT

Thanks, I'll release an updated version when I have time (probably some time next week).

RE: Collector Tool

community@zenoss.org — Wed, 25 Aug 2010 19:27:13 GMT

Which are the ports I need to open in firewall?

RE: Collector Tool

community@zenoss.org — Wed, 25 Aug 2010 19:57:58 GMT

I don't know off hand, there are quite a few ports. Please post your question in the forums, this comments section is for comments relating specifically to this ZenPack. Thank you.

RE: Collector Tool

community@zenoss.org — Wed, 01 Sep 2010 15:14:17 GMT

Ryan,

This is an excellent tool and has saved me a lot of time in my deployment. One issue I am having is that the graphs collected from the remotes are not zoomable from the master.

Any thoughts?

Thanks in advance,

RE: Collector Tool

community@zenoss.org — Wed, 01 Sep 2010 15:27:08 GMT

I have something for you to try... I know how the script says to use http://localhost:8091/remotehost (the port may not be right, I'm doing this off the top of my head). Try to do http://remotehost:8091 instead. Also, out of curiosity, are you using 2.5 or 3.0?

Cheers.

RE: Collector Tool

community@zenoss.org — Wed, 01 Sep 2010 15:28:04 GMT

Yeh sorry, port 8090.

RE: Collector Tool

community@zenoss.org — Wed, 01 Sep 2010 15:38:48 GMT

Ryan,

Thanks for the quick idea. I tried your change and that only broke the graphs with the collector render url of http://192.168.200.252:8090, when I changed it to http://192.168.200.252:8091 they worked again but I am still not able to zoom. I am running zenoss 2.5.2 x64 on both the Master and the Slave.

Thanks again,

RE: Collector Tool

community@zenoss.org — Wed, 01 Sep 2010 15:41:46 GMT

I've heard of this zooming issue many times. Doesn't seem like anyone has come up with a solid solution to it. Wish I could be more helpful. You might want to try posting in the forums and see what you get in there.